disabling mouse support in `vim` in a `gnome-terminal` environmentDefault GNOME cursors package?Why does F10 in gnome-terminal open the right-click menu?Enable mouse support in the console for applications that feature it in GUI terminalsvmware debian sid gnome mouse not working keyboard is fineSetting Terminal tab names in OS X and using vimVim in Gnome-terminal says “Output is not to a terminal”Disabling mouse in Vim disables indentationHow to fix anoying vim/terminal behaviour (vim produces empty lines in terminal)?Any terminal shell with mouse support?st-terminal / vim - Ultisnips: How to enable Ctrl+Enter as Enter in insert mode of vim?

What is the difference between "behavior" and "behaviour"?

How to be diplomatic in refusing to write code that breaches the privacy of our users

Large drywall patch supports

Why not increase contact surface when reentering the atmosphere?

How easy is it to start Magic from scratch?

India just shot down a satellite from the ground. At what altitude range is the resulting debris field?

Pre-amplifier input protection

CREATE opcode: what does it really do?

How to write papers efficiently when English isn't my first language?

Escape a backup date in a file name

Is exact Kanji stroke length important?

What is the best translation for "slot" in the context of multiplayer video games?

How to safely derail a train during transit?

Unreliable Magic - Is it worth it?

Pole-zeros of a real-valued causal FIR system

Increase performance creating Mandelbrot set in python

Do sorcerers' Subtle Spells require a skill check to be unseen?

Was Spock the First Vulcan in Starfleet?

You cannot touch me, but I can touch you, who am I?

How can a function with a hole (removable discontinuity) equal a function with no hole?

How to pronounce the slash sign

Different result between scanning in Epson's "color negative film" mode and scanning in positive -> invert curve in post?

Why didn't Theresa May consult with Parliament before negotiating a deal with the EU?

What is the intuitive meaning of having a linear relationship between the logs of two variables?



disabling mouse support in `vim` in a `gnome-terminal` environment


Default GNOME cursors package?Why does F10 in gnome-terminal open the right-click menu?Enable mouse support in the console for applications that feature it in GUI terminalsvmware debian sid gnome mouse not working keyboard is fineSetting Terminal tab names in OS X and using vimVim in Gnome-terminal says “Output is not to a terminal”Disabling mouse in Vim disables indentationHow to fix anoying vim/terminal behaviour (vim produces empty lines in terminal)?Any terminal shell with mouse support?st-terminal / vim - Ultisnips: How to enable Ctrl+Enter as Enter in insert mode of vim?













42















Edit: The problem of an enabled mouse in vim appears to be specific to gnome-terminal (version 3.4.1.1-1; I am using gnome 3 fallback mode). If I run xterm, mouse support in vim is disabled by default, and I have the option to enable it (:set mouse=a, which I never do) and disable it (:set mouse=). In contrast, when I run vim in gnome-terminal, mouse support is enabled by default and it is not possible to disable it (:set mouse= has no effect). Is there a solution short of changing terminal emulator?




I want to completely disable mouse support in vim. I am running vim version 2:7.3.547-3 through gnome-terminal version 3.4.1.1-1. The following commands, whether executed directly in vim or added to my .vimrc file, fail to disable mouse support:



set mouse =
set mouse =""


Based on reading the vim manual and posts online, one or both of these commands should work. In particular, the vim manual states the following



'mouse' string (default "", "a" for GUI, MS-DOS and Win32)
The mouse can be enabled for different modes:
n Normal mode
v Visual mode
i Insert mode
c Command-line mode
h all previous modes when editing a help file
a all previous modes
r for |hit-enter| and |more-prompt| prompt
Normally you would enable the mouse in all four modes with: >
:set mouse=a
When the mouse is not enabled, the GUI will still use the mouse for
modeless selection. This doesn't move the text cursor.


I am using a laptop and each time my hand brushes the trackpad, my cursor position in vim moves abruptly.










share|improve this question




























    42















    Edit: The problem of an enabled mouse in vim appears to be specific to gnome-terminal (version 3.4.1.1-1; I am using gnome 3 fallback mode). If I run xterm, mouse support in vim is disabled by default, and I have the option to enable it (:set mouse=a, which I never do) and disable it (:set mouse=). In contrast, when I run vim in gnome-terminal, mouse support is enabled by default and it is not possible to disable it (:set mouse= has no effect). Is there a solution short of changing terminal emulator?




    I want to completely disable mouse support in vim. I am running vim version 2:7.3.547-3 through gnome-terminal version 3.4.1.1-1. The following commands, whether executed directly in vim or added to my .vimrc file, fail to disable mouse support:



    set mouse =
    set mouse =""


    Based on reading the vim manual and posts online, one or both of these commands should work. In particular, the vim manual states the following



    'mouse' string (default "", "a" for GUI, MS-DOS and Win32)
    The mouse can be enabled for different modes:
    n Normal mode
    v Visual mode
    i Insert mode
    c Command-line mode
    h all previous modes when editing a help file
    a all previous modes
    r for |hit-enter| and |more-prompt| prompt
    Normally you would enable the mouse in all four modes with: >
    :set mouse=a
    When the mouse is not enabled, the GUI will still use the mouse for
    modeless selection. This doesn't move the text cursor.


    I am using a laptop and each time my hand brushes the trackpad, my cursor position in vim moves abruptly.










    share|improve this question


























      42












      42








      42


      11






      Edit: The problem of an enabled mouse in vim appears to be specific to gnome-terminal (version 3.4.1.1-1; I am using gnome 3 fallback mode). If I run xterm, mouse support in vim is disabled by default, and I have the option to enable it (:set mouse=a, which I never do) and disable it (:set mouse=). In contrast, when I run vim in gnome-terminal, mouse support is enabled by default and it is not possible to disable it (:set mouse= has no effect). Is there a solution short of changing terminal emulator?




      I want to completely disable mouse support in vim. I am running vim version 2:7.3.547-3 through gnome-terminal version 3.4.1.1-1. The following commands, whether executed directly in vim or added to my .vimrc file, fail to disable mouse support:



      set mouse =
      set mouse =""


      Based on reading the vim manual and posts online, one or both of these commands should work. In particular, the vim manual states the following



      'mouse' string (default "", "a" for GUI, MS-DOS and Win32)
      The mouse can be enabled for different modes:
      n Normal mode
      v Visual mode
      i Insert mode
      c Command-line mode
      h all previous modes when editing a help file
      a all previous modes
      r for |hit-enter| and |more-prompt| prompt
      Normally you would enable the mouse in all four modes with: >
      :set mouse=a
      When the mouse is not enabled, the GUI will still use the mouse for
      modeless selection. This doesn't move the text cursor.


      I am using a laptop and each time my hand brushes the trackpad, my cursor position in vim moves abruptly.










      share|improve this question
















      Edit: The problem of an enabled mouse in vim appears to be specific to gnome-terminal (version 3.4.1.1-1; I am using gnome 3 fallback mode). If I run xterm, mouse support in vim is disabled by default, and I have the option to enable it (:set mouse=a, which I never do) and disable it (:set mouse=). In contrast, when I run vim in gnome-terminal, mouse support is enabled by default and it is not possible to disable it (:set mouse= has no effect). Is there a solution short of changing terminal emulator?




      I want to completely disable mouse support in vim. I am running vim version 2:7.3.547-3 through gnome-terminal version 3.4.1.1-1. The following commands, whether executed directly in vim or added to my .vimrc file, fail to disable mouse support:



      set mouse =
      set mouse =""


      Based on reading the vim manual and posts online, one or both of these commands should work. In particular, the vim manual states the following



      'mouse' string (default "", "a" for GUI, MS-DOS and Win32)
      The mouse can be enabled for different modes:
      n Normal mode
      v Visual mode
      i Insert mode
      c Command-line mode
      h all previous modes when editing a help file
      a all previous modes
      r for |hit-enter| and |more-prompt| prompt
      Normally you would enable the mouse in all four modes with: >
      :set mouse=a
      When the mouse is not enabled, the GUI will still use the mouse for
      modeless selection. This doesn't move the text cursor.


      I am using a laptop and each time my hand brushes the trackpad, my cursor position in vim moves abruptly.







      gnome vim mouse gnome-terminal






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Aug 2 '12 at 22:47







      user001

















      asked Aug 2 '12 at 1:04









      user001user001

      1,55232038




      1,55232038




















          7 Answers
          7






          active

          oldest

          votes


















          27














          I've found what cause this bad behavior with many linux flavors :



          /usr/share/vim/vim80/defaults.vim # may be "vim81" depending on your vim version


          it's 'sourced' if there's no ~/.vimrc but even if you have a /etc/vimrc or such /etc file, so if you don't have one just create a blank one as suggested by @lgpasquale:



          [[ -s ~/.vim/vimrc ]] && echo "aborted, file exists" || :> ~/.vim/vimrc


          If you liked the other features (like syntax highlighting) that you got from defaults.vim, you can use this command rather the the previous one:



          [[ -s ~/.vim/vimrc ]] && echo "aborted, file exists" || echo -e "source /usr/share/vim/vim80/defaults.vimnset mouse=" > ~/.vim/vimrc





          share|improve this answer




















          • 2





            Thank you! Commenting out the line "mouse -a" in that file solved the issue for me (on Archlinux)

            – luckyrumo
            Nov 3 '16 at 20:57







          • 1





            You don't need to edit that file (which is part of vim-runtime on archlinux). As it's stated in that file, it is only loaded if no vimrc is found. That means that placing a .vimrc file in your home should solve the problem (it did for me). It doesn't need to contain anything, it can even be an empty file.

            – lgpasquale
            Dec 13 '16 at 22:28












          • This is the real solution for Fedora 25.

            – KamikazeCZ
            Dec 14 '16 at 12:24











          • I confirm this worked for me in Debian 8 in late 2017.

            – Criggie
            Jan 6 '17 at 8:30






          • 1





            @rlf In my opinion editing a file under /usr/share/ which is managed by your package manager is a bad idea. If you want to keep some of the options in defaults.vim, I would copy them to ~/.vimrc.

            – lgpasquale
            Jun 23 '17 at 15:08


















          22














          mouse support is disabled by default, so something is turning it on. Likely the reason your set mouse= is failing is because it's running before whatever is turning it on. I'd look through the rest of your vimrc, and possibly the system wide vimrc (/etc/vim/vimrc is a standard location).



          As a last resort, you can do this really ugly hack which will cause the command to run as one of the last things done before giving you control of the editor.



          autocmd BufEnter * set mouse=





          share|improve this answer


















          • 2





            My /etc/vim/vimrc file is pretty bare (runtime! debian.vim and a conditional if filereadable("/etc/vim/vimrc.local") ; source /etc/vim/vimrc.local; endif). The /etc/vim/vimrc.local file does not exist on my system. My ~/.vimrc file only has a few lines that I have added manually. An strace of vim reveals that it checks the following locations for config files: /usr/share/vim/vimrc, /etc/vim/vimrc.local (ENOENT), and /home/user/.vimrc. (Why do I receive the ENOENT error; doesn't the if statement prevent attempts to open this non-existent file?).

            – user001
            Aug 2 '12 at 1:38












          • Also, if I type :set mouse= directly in vim, shouldn't this override any settings from config files? Why would direct execution of this statement within vim not disable mouse control?

            – user001
            Aug 2 '12 at 1:40







          • 1





            @user001 You see the ENOENT as vim has to check if the file exists. This is typically done by calling stat which returns ENOENT if the file does not exist.

            – Ulrich Dangel
            Aug 2 '12 at 5:29







          • 2





            @user001 ah, the fact that it doesnt work when typed into the current session is critical info. Based on this, I'm not sure it's vim that's the problem. Maybe gnome-terminal is doing something horrible. Can you try a different terminal emulator?

            – Patrick
            Aug 2 '12 at 12:30











          • Hi, good suggestion. I tried in xterm and had no problem with mouse activation. I could reproduce the problem by typing :set mouse=a in vim running in xterm (and reverse it by typing :set mouse=). Any idea how to troubleshoot the gnome-terminal glitch? Should I start a new thread? Thanks.

            – user001
            Aug 2 '12 at 12:54



















          6














          I ran into this on my OS X "Terminal" app on a Fedora Server 25 host. I've permanently solved it with this in my .vimrc with:



          set mouse=
          set ttymouse=


          Now I can scroll up to my previous bash history in my terminal's scrollback with my mouse.






          share|improve this answer























          • It is strongly recommended to create a vimrc.local in the same catalogue, because vimrc.local wont be updated if vim get updates

            – Orphans
            Aug 22 '17 at 9:57











          • It worked for me on Raspbian 9.4. Other answers did not solve undesired mouse behaviour when I log in via PUTTY.

            – Dmitry
            Sep 22 '18 at 21:53











          • For anyone else cutting and pasting, note set ttymouse= had strange behaviour for me, e.g. caused behaviour of arrow keys, escape key to change.

            – mozboz
            Jan 8 at 14:48



















          4














          I had pretty much the same complaints as you about the newer Vim's sensitivity to the mouse. Using set mouse="" did not do it for me, either.



          I have set mouse=c (no quotes) close to the bottom of my .vimrc file. That seemed to keep Vim from using the mouse, except when using "PuTTY" to ssh in from my (ugh!) Windows machine at work. I have to use shift-middle-button to paste in PuTTY.



          2018-03-30 Edit: I have now started using: :mouse= (no quotes or anything) on some remote (CentOS 6.7) instances of vim to get rid of undesired mouse effects.






          share|improve this answer

























          • Hi, thanks for the suggestion. I added this to my .vimrc file and tried executing it interactively (:set mouse=c), but neither had an effect in my case.

            – user001
            Aug 2 '12 at 2:14


















          3














          Add this to your .vimrc:



          if has("gui_running")
          "echo "yes, we have a GUI"
          set mouse=a
          else
          "echo "Boring old console"
          set mouse=
          endif





          share|improve this answer




















          • 1





            This is of no relevance to the question asked.

            – GKFX
            Sep 24 '16 at 19:54











          • @GKFX Are you sure? It looks relevant to me. Note that has("gui_running") is 0 in a terminal environment. This answer, unlike the others, takes extra effort to only disable the mouse in a terminal environment, which the question asks, while leaving it enabled in gvim.

            – hvd
            Jul 29 '17 at 6:23











          • @hvd I worded my comment a bit harshly; I apologize. However, this answer just puts an if block around what the OP had already tried, so it's unlikely to be helpful.

            – GKFX
            Jul 29 '17 at 13:15






          • 1





            @GKFX Fair point, and applies to other answers as well.

            – hvd
            Jul 29 '17 at 13:23


















          0














          Somewhat related to the question, if you are using neovim(nvim) you should put set mouse= in your ~/.config/nvim/init.vim configuration file.



          If the directory doesn't exist create it with mkdir -p ~/.config/nvim/






          share|improve this answer






























            0














            On debian stretch some central settings are loaded after loading /etc/vim/vimrc and /etc/vim/vimrc.local. See /etc/vim/vimrc:



            ...
            " Vim will load $VIMRUNTIME/defaults.vim if the user does not have a vimrc.
            " This happens after /etc/vim/vimrc(.local) are loaded, so it will override
            " any settings in these files.
            " If you don't want that to happen, uncomment the below line to prevent
            " defaults.vim from being loaded.
            "let g:skip_defaults_vim = 1
            ...


            This files defaults to /usr/share/vim/vim80/defaults.vim. Now changing a central file under /usr/share/... is



            • evil

            • non-permanent, it gets reverted after an update

            Setting skip_defaults_vim by uncommentig the above line removes all other options set by that file. To just remove the unwanted options put the following into /etc/vimrc.local:



            " /etc/vim/vimrc.local
            " honor skip_defaults_vim from the master /etc/vim/vimrc file
            if ! exists('skip_defaults_vim')
            " Source the defaults file manually from here
            source $VIMRUNTIME/defaults.vim
            endif

            " avoid loading the defaults twice
            let g:skip_defaults_vim = 1

            " revert any unwanted changes the defaults file introduced
            set mouse=

            " set any other options you want centrally on your system
            "set paste " uncomment if you want paste insert enabled
            "...


            This loads the defaults.vim manually and turns off the automatic loading, thus giving you a chance to revert any unwanted settings, without having to create a .vimrc for every user account.






            share|improve this answer
























              Your Answer








              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "106"
              ;
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function()
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled)
              StackExchange.using("snippets", function()
              createEditor();
              );

              else
              createEditor();

              );

              function createEditor()
              StackExchange.prepareEditor(
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: false,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: null,
              bindNavPrevention: true,
              postfix: "",
              imageUploader:
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              ,
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              );



              );













              draft saved

              draft discarded


















              StackExchange.ready(
              function ()
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f44513%2fdisabling-mouse-support-in-vim-in-a-gnome-terminal-environment%23new-answer', 'question_page');

              );

              Post as a guest















              Required, but never shown

























              7 Answers
              7






              active

              oldest

              votes








              7 Answers
              7






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              27














              I've found what cause this bad behavior with many linux flavors :



              /usr/share/vim/vim80/defaults.vim # may be "vim81" depending on your vim version


              it's 'sourced' if there's no ~/.vimrc but even if you have a /etc/vimrc or such /etc file, so if you don't have one just create a blank one as suggested by @lgpasquale:



              [[ -s ~/.vim/vimrc ]] && echo "aborted, file exists" || :> ~/.vim/vimrc


              If you liked the other features (like syntax highlighting) that you got from defaults.vim, you can use this command rather the the previous one:



              [[ -s ~/.vim/vimrc ]] && echo "aborted, file exists" || echo -e "source /usr/share/vim/vim80/defaults.vimnset mouse=" > ~/.vim/vimrc





              share|improve this answer




















              • 2





                Thank you! Commenting out the line "mouse -a" in that file solved the issue for me (on Archlinux)

                – luckyrumo
                Nov 3 '16 at 20:57







              • 1





                You don't need to edit that file (which is part of vim-runtime on archlinux). As it's stated in that file, it is only loaded if no vimrc is found. That means that placing a .vimrc file in your home should solve the problem (it did for me). It doesn't need to contain anything, it can even be an empty file.

                – lgpasquale
                Dec 13 '16 at 22:28












              • This is the real solution for Fedora 25.

                – KamikazeCZ
                Dec 14 '16 at 12:24











              • I confirm this worked for me in Debian 8 in late 2017.

                – Criggie
                Jan 6 '17 at 8:30






              • 1





                @rlf In my opinion editing a file under /usr/share/ which is managed by your package manager is a bad idea. If you want to keep some of the options in defaults.vim, I would copy them to ~/.vimrc.

                – lgpasquale
                Jun 23 '17 at 15:08















              27














              I've found what cause this bad behavior with many linux flavors :



              /usr/share/vim/vim80/defaults.vim # may be "vim81" depending on your vim version


              it's 'sourced' if there's no ~/.vimrc but even if you have a /etc/vimrc or such /etc file, so if you don't have one just create a blank one as suggested by @lgpasquale:



              [[ -s ~/.vim/vimrc ]] && echo "aborted, file exists" || :> ~/.vim/vimrc


              If you liked the other features (like syntax highlighting) that you got from defaults.vim, you can use this command rather the the previous one:



              [[ -s ~/.vim/vimrc ]] && echo "aborted, file exists" || echo -e "source /usr/share/vim/vim80/defaults.vimnset mouse=" > ~/.vim/vimrc





              share|improve this answer




















              • 2





                Thank you! Commenting out the line "mouse -a" in that file solved the issue for me (on Archlinux)

                – luckyrumo
                Nov 3 '16 at 20:57







              • 1





                You don't need to edit that file (which is part of vim-runtime on archlinux). As it's stated in that file, it is only loaded if no vimrc is found. That means that placing a .vimrc file in your home should solve the problem (it did for me). It doesn't need to contain anything, it can even be an empty file.

                – lgpasquale
                Dec 13 '16 at 22:28












              • This is the real solution for Fedora 25.

                – KamikazeCZ
                Dec 14 '16 at 12:24











              • I confirm this worked for me in Debian 8 in late 2017.

                – Criggie
                Jan 6 '17 at 8:30






              • 1





                @rlf In my opinion editing a file under /usr/share/ which is managed by your package manager is a bad idea. If you want to keep some of the options in defaults.vim, I would copy them to ~/.vimrc.

                – lgpasquale
                Jun 23 '17 at 15:08













              27












              27








              27







              I've found what cause this bad behavior with many linux flavors :



              /usr/share/vim/vim80/defaults.vim # may be "vim81" depending on your vim version


              it's 'sourced' if there's no ~/.vimrc but even if you have a /etc/vimrc or such /etc file, so if you don't have one just create a blank one as suggested by @lgpasquale:



              [[ -s ~/.vim/vimrc ]] && echo "aborted, file exists" || :> ~/.vim/vimrc


              If you liked the other features (like syntax highlighting) that you got from defaults.vim, you can use this command rather the the previous one:



              [[ -s ~/.vim/vimrc ]] && echo "aborted, file exists" || echo -e "source /usr/share/vim/vim80/defaults.vimnset mouse=" > ~/.vim/vimrc





              share|improve this answer















              I've found what cause this bad behavior with many linux flavors :



              /usr/share/vim/vim80/defaults.vim # may be "vim81" depending on your vim version


              it's 'sourced' if there's no ~/.vimrc but even if you have a /etc/vimrc or such /etc file, so if you don't have one just create a blank one as suggested by @lgpasquale:



              [[ -s ~/.vim/vimrc ]] && echo "aborted, file exists" || :> ~/.vim/vimrc


              If you liked the other features (like syntax highlighting) that you got from defaults.vim, you can use this command rather the the previous one:



              [[ -s ~/.vim/vimrc ]] && echo "aborted, file exists" || echo -e "source /usr/share/vim/vim80/defaults.vimnset mouse=" > ~/.vim/vimrc






              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Jan 8 at 19:44









              Minix

              2,30952040




              2,30952040










              answered Sep 21 '16 at 21:36









              Gilles QuenotGilles Quenot

              16.3k14053




              16.3k14053







              • 2





                Thank you! Commenting out the line "mouse -a" in that file solved the issue for me (on Archlinux)

                – luckyrumo
                Nov 3 '16 at 20:57







              • 1





                You don't need to edit that file (which is part of vim-runtime on archlinux). As it's stated in that file, it is only loaded if no vimrc is found. That means that placing a .vimrc file in your home should solve the problem (it did for me). It doesn't need to contain anything, it can even be an empty file.

                – lgpasquale
                Dec 13 '16 at 22:28












              • This is the real solution for Fedora 25.

                – KamikazeCZ
                Dec 14 '16 at 12:24











              • I confirm this worked for me in Debian 8 in late 2017.

                – Criggie
                Jan 6 '17 at 8:30






              • 1





                @rlf In my opinion editing a file under /usr/share/ which is managed by your package manager is a bad idea. If you want to keep some of the options in defaults.vim, I would copy them to ~/.vimrc.

                – lgpasquale
                Jun 23 '17 at 15:08












              • 2





                Thank you! Commenting out the line "mouse -a" in that file solved the issue for me (on Archlinux)

                – luckyrumo
                Nov 3 '16 at 20:57







              • 1





                You don't need to edit that file (which is part of vim-runtime on archlinux). As it's stated in that file, it is only loaded if no vimrc is found. That means that placing a .vimrc file in your home should solve the problem (it did for me). It doesn't need to contain anything, it can even be an empty file.

                – lgpasquale
                Dec 13 '16 at 22:28












              • This is the real solution for Fedora 25.

                – KamikazeCZ
                Dec 14 '16 at 12:24











              • I confirm this worked for me in Debian 8 in late 2017.

                – Criggie
                Jan 6 '17 at 8:30






              • 1





                @rlf In my opinion editing a file under /usr/share/ which is managed by your package manager is a bad idea. If you want to keep some of the options in defaults.vim, I would copy them to ~/.vimrc.

                – lgpasquale
                Jun 23 '17 at 15:08







              2




              2





              Thank you! Commenting out the line "mouse -a" in that file solved the issue for me (on Archlinux)

              – luckyrumo
              Nov 3 '16 at 20:57






              Thank you! Commenting out the line "mouse -a" in that file solved the issue for me (on Archlinux)

              – luckyrumo
              Nov 3 '16 at 20:57





              1




              1





              You don't need to edit that file (which is part of vim-runtime on archlinux). As it's stated in that file, it is only loaded if no vimrc is found. That means that placing a .vimrc file in your home should solve the problem (it did for me). It doesn't need to contain anything, it can even be an empty file.

              – lgpasquale
              Dec 13 '16 at 22:28






              You don't need to edit that file (which is part of vim-runtime on archlinux). As it's stated in that file, it is only loaded if no vimrc is found. That means that placing a .vimrc file in your home should solve the problem (it did for me). It doesn't need to contain anything, it can even be an empty file.

              – lgpasquale
              Dec 13 '16 at 22:28














              This is the real solution for Fedora 25.

              – KamikazeCZ
              Dec 14 '16 at 12:24





              This is the real solution for Fedora 25.

              – KamikazeCZ
              Dec 14 '16 at 12:24













              I confirm this worked for me in Debian 8 in late 2017.

              – Criggie
              Jan 6 '17 at 8:30





              I confirm this worked for me in Debian 8 in late 2017.

              – Criggie
              Jan 6 '17 at 8:30




              1




              1





              @rlf In my opinion editing a file under /usr/share/ which is managed by your package manager is a bad idea. If you want to keep some of the options in defaults.vim, I would copy them to ~/.vimrc.

              – lgpasquale
              Jun 23 '17 at 15:08





              @rlf In my opinion editing a file under /usr/share/ which is managed by your package manager is a bad idea. If you want to keep some of the options in defaults.vim, I would copy them to ~/.vimrc.

              – lgpasquale
              Jun 23 '17 at 15:08













              22














              mouse support is disabled by default, so something is turning it on. Likely the reason your set mouse= is failing is because it's running before whatever is turning it on. I'd look through the rest of your vimrc, and possibly the system wide vimrc (/etc/vim/vimrc is a standard location).



              As a last resort, you can do this really ugly hack which will cause the command to run as one of the last things done before giving you control of the editor.



              autocmd BufEnter * set mouse=





              share|improve this answer


















              • 2





                My /etc/vim/vimrc file is pretty bare (runtime! debian.vim and a conditional if filereadable("/etc/vim/vimrc.local") ; source /etc/vim/vimrc.local; endif). The /etc/vim/vimrc.local file does not exist on my system. My ~/.vimrc file only has a few lines that I have added manually. An strace of vim reveals that it checks the following locations for config files: /usr/share/vim/vimrc, /etc/vim/vimrc.local (ENOENT), and /home/user/.vimrc. (Why do I receive the ENOENT error; doesn't the if statement prevent attempts to open this non-existent file?).

                – user001
                Aug 2 '12 at 1:38












              • Also, if I type :set mouse= directly in vim, shouldn't this override any settings from config files? Why would direct execution of this statement within vim not disable mouse control?

                – user001
                Aug 2 '12 at 1:40







              • 1





                @user001 You see the ENOENT as vim has to check if the file exists. This is typically done by calling stat which returns ENOENT if the file does not exist.

                – Ulrich Dangel
                Aug 2 '12 at 5:29







              • 2





                @user001 ah, the fact that it doesnt work when typed into the current session is critical info. Based on this, I'm not sure it's vim that's the problem. Maybe gnome-terminal is doing something horrible. Can you try a different terminal emulator?

                – Patrick
                Aug 2 '12 at 12:30











              • Hi, good suggestion. I tried in xterm and had no problem with mouse activation. I could reproduce the problem by typing :set mouse=a in vim running in xterm (and reverse it by typing :set mouse=). Any idea how to troubleshoot the gnome-terminal glitch? Should I start a new thread? Thanks.

                – user001
                Aug 2 '12 at 12:54
















              22














              mouse support is disabled by default, so something is turning it on. Likely the reason your set mouse= is failing is because it's running before whatever is turning it on. I'd look through the rest of your vimrc, and possibly the system wide vimrc (/etc/vim/vimrc is a standard location).



              As a last resort, you can do this really ugly hack which will cause the command to run as one of the last things done before giving you control of the editor.



              autocmd BufEnter * set mouse=





              share|improve this answer


















              • 2





                My /etc/vim/vimrc file is pretty bare (runtime! debian.vim and a conditional if filereadable("/etc/vim/vimrc.local") ; source /etc/vim/vimrc.local; endif). The /etc/vim/vimrc.local file does not exist on my system. My ~/.vimrc file only has a few lines that I have added manually. An strace of vim reveals that it checks the following locations for config files: /usr/share/vim/vimrc, /etc/vim/vimrc.local (ENOENT), and /home/user/.vimrc. (Why do I receive the ENOENT error; doesn't the if statement prevent attempts to open this non-existent file?).

                – user001
                Aug 2 '12 at 1:38












              • Also, if I type :set mouse= directly in vim, shouldn't this override any settings from config files? Why would direct execution of this statement within vim not disable mouse control?

                – user001
                Aug 2 '12 at 1:40







              • 1





                @user001 You see the ENOENT as vim has to check if the file exists. This is typically done by calling stat which returns ENOENT if the file does not exist.

                – Ulrich Dangel
                Aug 2 '12 at 5:29







              • 2





                @user001 ah, the fact that it doesnt work when typed into the current session is critical info. Based on this, I'm not sure it's vim that's the problem. Maybe gnome-terminal is doing something horrible. Can you try a different terminal emulator?

                – Patrick
                Aug 2 '12 at 12:30











              • Hi, good suggestion. I tried in xterm and had no problem with mouse activation. I could reproduce the problem by typing :set mouse=a in vim running in xterm (and reverse it by typing :set mouse=). Any idea how to troubleshoot the gnome-terminal glitch? Should I start a new thread? Thanks.

                – user001
                Aug 2 '12 at 12:54














              22












              22








              22







              mouse support is disabled by default, so something is turning it on. Likely the reason your set mouse= is failing is because it's running before whatever is turning it on. I'd look through the rest of your vimrc, and possibly the system wide vimrc (/etc/vim/vimrc is a standard location).



              As a last resort, you can do this really ugly hack which will cause the command to run as one of the last things done before giving you control of the editor.



              autocmd BufEnter * set mouse=





              share|improve this answer













              mouse support is disabled by default, so something is turning it on. Likely the reason your set mouse= is failing is because it's running before whatever is turning it on. I'd look through the rest of your vimrc, and possibly the system wide vimrc (/etc/vim/vimrc is a standard location).



              As a last resort, you can do this really ugly hack which will cause the command to run as one of the last things done before giving you control of the editor.



              autocmd BufEnter * set mouse=






              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Aug 2 '12 at 1:19









              PatrickPatrick

              51.3k11132183




              51.3k11132183







              • 2





                My /etc/vim/vimrc file is pretty bare (runtime! debian.vim and a conditional if filereadable("/etc/vim/vimrc.local") ; source /etc/vim/vimrc.local; endif). The /etc/vim/vimrc.local file does not exist on my system. My ~/.vimrc file only has a few lines that I have added manually. An strace of vim reveals that it checks the following locations for config files: /usr/share/vim/vimrc, /etc/vim/vimrc.local (ENOENT), and /home/user/.vimrc. (Why do I receive the ENOENT error; doesn't the if statement prevent attempts to open this non-existent file?).

                – user001
                Aug 2 '12 at 1:38












              • Also, if I type :set mouse= directly in vim, shouldn't this override any settings from config files? Why would direct execution of this statement within vim not disable mouse control?

                – user001
                Aug 2 '12 at 1:40







              • 1





                @user001 You see the ENOENT as vim has to check if the file exists. This is typically done by calling stat which returns ENOENT if the file does not exist.

                – Ulrich Dangel
                Aug 2 '12 at 5:29







              • 2





                @user001 ah, the fact that it doesnt work when typed into the current session is critical info. Based on this, I'm not sure it's vim that's the problem. Maybe gnome-terminal is doing something horrible. Can you try a different terminal emulator?

                – Patrick
                Aug 2 '12 at 12:30











              • Hi, good suggestion. I tried in xterm and had no problem with mouse activation. I could reproduce the problem by typing :set mouse=a in vim running in xterm (and reverse it by typing :set mouse=). Any idea how to troubleshoot the gnome-terminal glitch? Should I start a new thread? Thanks.

                – user001
                Aug 2 '12 at 12:54













              • 2





                My /etc/vim/vimrc file is pretty bare (runtime! debian.vim and a conditional if filereadable("/etc/vim/vimrc.local") ; source /etc/vim/vimrc.local; endif). The /etc/vim/vimrc.local file does not exist on my system. My ~/.vimrc file only has a few lines that I have added manually. An strace of vim reveals that it checks the following locations for config files: /usr/share/vim/vimrc, /etc/vim/vimrc.local (ENOENT), and /home/user/.vimrc. (Why do I receive the ENOENT error; doesn't the if statement prevent attempts to open this non-existent file?).

                – user001
                Aug 2 '12 at 1:38












              • Also, if I type :set mouse= directly in vim, shouldn't this override any settings from config files? Why would direct execution of this statement within vim not disable mouse control?

                – user001
                Aug 2 '12 at 1:40







              • 1





                @user001 You see the ENOENT as vim has to check if the file exists. This is typically done by calling stat which returns ENOENT if the file does not exist.

                – Ulrich Dangel
                Aug 2 '12 at 5:29







              • 2





                @user001 ah, the fact that it doesnt work when typed into the current session is critical info. Based on this, I'm not sure it's vim that's the problem. Maybe gnome-terminal is doing something horrible. Can you try a different terminal emulator?

                – Patrick
                Aug 2 '12 at 12:30











              • Hi, good suggestion. I tried in xterm and had no problem with mouse activation. I could reproduce the problem by typing :set mouse=a in vim running in xterm (and reverse it by typing :set mouse=). Any idea how to troubleshoot the gnome-terminal glitch? Should I start a new thread? Thanks.

                – user001
                Aug 2 '12 at 12:54








              2




              2





              My /etc/vim/vimrc file is pretty bare (runtime! debian.vim and a conditional if filereadable("/etc/vim/vimrc.local") ; source /etc/vim/vimrc.local; endif). The /etc/vim/vimrc.local file does not exist on my system. My ~/.vimrc file only has a few lines that I have added manually. An strace of vim reveals that it checks the following locations for config files: /usr/share/vim/vimrc, /etc/vim/vimrc.local (ENOENT), and /home/user/.vimrc. (Why do I receive the ENOENT error; doesn't the if statement prevent attempts to open this non-existent file?).

              – user001
              Aug 2 '12 at 1:38






              My /etc/vim/vimrc file is pretty bare (runtime! debian.vim and a conditional if filereadable("/etc/vim/vimrc.local") ; source /etc/vim/vimrc.local; endif). The /etc/vim/vimrc.local file does not exist on my system. My ~/.vimrc file only has a few lines that I have added manually. An strace of vim reveals that it checks the following locations for config files: /usr/share/vim/vimrc, /etc/vim/vimrc.local (ENOENT), and /home/user/.vimrc. (Why do I receive the ENOENT error; doesn't the if statement prevent attempts to open this non-existent file?).

              – user001
              Aug 2 '12 at 1:38














              Also, if I type :set mouse= directly in vim, shouldn't this override any settings from config files? Why would direct execution of this statement within vim not disable mouse control?

              – user001
              Aug 2 '12 at 1:40






              Also, if I type :set mouse= directly in vim, shouldn't this override any settings from config files? Why would direct execution of this statement within vim not disable mouse control?

              – user001
              Aug 2 '12 at 1:40





              1




              1





              @user001 You see the ENOENT as vim has to check if the file exists. This is typically done by calling stat which returns ENOENT if the file does not exist.

              – Ulrich Dangel
              Aug 2 '12 at 5:29






              @user001 You see the ENOENT as vim has to check if the file exists. This is typically done by calling stat which returns ENOENT if the file does not exist.

              – Ulrich Dangel
              Aug 2 '12 at 5:29





              2




              2





              @user001 ah, the fact that it doesnt work when typed into the current session is critical info. Based on this, I'm not sure it's vim that's the problem. Maybe gnome-terminal is doing something horrible. Can you try a different terminal emulator?

              – Patrick
              Aug 2 '12 at 12:30





              @user001 ah, the fact that it doesnt work when typed into the current session is critical info. Based on this, I'm not sure it's vim that's the problem. Maybe gnome-terminal is doing something horrible. Can you try a different terminal emulator?

              – Patrick
              Aug 2 '12 at 12:30













              Hi, good suggestion. I tried in xterm and had no problem with mouse activation. I could reproduce the problem by typing :set mouse=a in vim running in xterm (and reverse it by typing :set mouse=). Any idea how to troubleshoot the gnome-terminal glitch? Should I start a new thread? Thanks.

              – user001
              Aug 2 '12 at 12:54






              Hi, good suggestion. I tried in xterm and had no problem with mouse activation. I could reproduce the problem by typing :set mouse=a in vim running in xterm (and reverse it by typing :set mouse=). Any idea how to troubleshoot the gnome-terminal glitch? Should I start a new thread? Thanks.

              – user001
              Aug 2 '12 at 12:54












              6














              I ran into this on my OS X "Terminal" app on a Fedora Server 25 host. I've permanently solved it with this in my .vimrc with:



              set mouse=
              set ttymouse=


              Now I can scroll up to my previous bash history in my terminal's scrollback with my mouse.






              share|improve this answer























              • It is strongly recommended to create a vimrc.local in the same catalogue, because vimrc.local wont be updated if vim get updates

                – Orphans
                Aug 22 '17 at 9:57











              • It worked for me on Raspbian 9.4. Other answers did not solve undesired mouse behaviour when I log in via PUTTY.

                – Dmitry
                Sep 22 '18 at 21:53











              • For anyone else cutting and pasting, note set ttymouse= had strange behaviour for me, e.g. caused behaviour of arrow keys, escape key to change.

                – mozboz
                Jan 8 at 14:48
















              6














              I ran into this on my OS X "Terminal" app on a Fedora Server 25 host. I've permanently solved it with this in my .vimrc with:



              set mouse=
              set ttymouse=


              Now I can scroll up to my previous bash history in my terminal's scrollback with my mouse.






              share|improve this answer























              • It is strongly recommended to create a vimrc.local in the same catalogue, because vimrc.local wont be updated if vim get updates

                – Orphans
                Aug 22 '17 at 9:57











              • It worked for me on Raspbian 9.4. Other answers did not solve undesired mouse behaviour when I log in via PUTTY.

                – Dmitry
                Sep 22 '18 at 21:53











              • For anyone else cutting and pasting, note set ttymouse= had strange behaviour for me, e.g. caused behaviour of arrow keys, escape key to change.

                – mozboz
                Jan 8 at 14:48














              6












              6








              6







              I ran into this on my OS X "Terminal" app on a Fedora Server 25 host. I've permanently solved it with this in my .vimrc with:



              set mouse=
              set ttymouse=


              Now I can scroll up to my previous bash history in my terminal's scrollback with my mouse.






              share|improve this answer













              I ran into this on my OS X "Terminal" app on a Fedora Server 25 host. I've permanently solved it with this in my .vimrc with:



              set mouse=
              set ttymouse=


              Now I can scroll up to my previous bash history in my terminal's scrollback with my mouse.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Dec 19 '16 at 0:39









              Robpol86Robpol86

              16112




              16112












              • It is strongly recommended to create a vimrc.local in the same catalogue, because vimrc.local wont be updated if vim get updates

                – Orphans
                Aug 22 '17 at 9:57











              • It worked for me on Raspbian 9.4. Other answers did not solve undesired mouse behaviour when I log in via PUTTY.

                – Dmitry
                Sep 22 '18 at 21:53











              • For anyone else cutting and pasting, note set ttymouse= had strange behaviour for me, e.g. caused behaviour of arrow keys, escape key to change.

                – mozboz
                Jan 8 at 14:48


















              • It is strongly recommended to create a vimrc.local in the same catalogue, because vimrc.local wont be updated if vim get updates

                – Orphans
                Aug 22 '17 at 9:57











              • It worked for me on Raspbian 9.4. Other answers did not solve undesired mouse behaviour when I log in via PUTTY.

                – Dmitry
                Sep 22 '18 at 21:53











              • For anyone else cutting and pasting, note set ttymouse= had strange behaviour for me, e.g. caused behaviour of arrow keys, escape key to change.

                – mozboz
                Jan 8 at 14:48

















              It is strongly recommended to create a vimrc.local in the same catalogue, because vimrc.local wont be updated if vim get updates

              – Orphans
              Aug 22 '17 at 9:57





              It is strongly recommended to create a vimrc.local in the same catalogue, because vimrc.local wont be updated if vim get updates

              – Orphans
              Aug 22 '17 at 9:57













              It worked for me on Raspbian 9.4. Other answers did not solve undesired mouse behaviour when I log in via PUTTY.

              – Dmitry
              Sep 22 '18 at 21:53





              It worked for me on Raspbian 9.4. Other answers did not solve undesired mouse behaviour when I log in via PUTTY.

              – Dmitry
              Sep 22 '18 at 21:53













              For anyone else cutting and pasting, note set ttymouse= had strange behaviour for me, e.g. caused behaviour of arrow keys, escape key to change.

              – mozboz
              Jan 8 at 14:48






              For anyone else cutting and pasting, note set ttymouse= had strange behaviour for me, e.g. caused behaviour of arrow keys, escape key to change.

              – mozboz
              Jan 8 at 14:48












              4














              I had pretty much the same complaints as you about the newer Vim's sensitivity to the mouse. Using set mouse="" did not do it for me, either.



              I have set mouse=c (no quotes) close to the bottom of my .vimrc file. That seemed to keep Vim from using the mouse, except when using "PuTTY" to ssh in from my (ugh!) Windows machine at work. I have to use shift-middle-button to paste in PuTTY.



              2018-03-30 Edit: I have now started using: :mouse= (no quotes or anything) on some remote (CentOS 6.7) instances of vim to get rid of undesired mouse effects.






              share|improve this answer

























              • Hi, thanks for the suggestion. I added this to my .vimrc file and tried executing it interactively (:set mouse=c), but neither had an effect in my case.

                – user001
                Aug 2 '12 at 2:14















              4














              I had pretty much the same complaints as you about the newer Vim's sensitivity to the mouse. Using set mouse="" did not do it for me, either.



              I have set mouse=c (no quotes) close to the bottom of my .vimrc file. That seemed to keep Vim from using the mouse, except when using "PuTTY" to ssh in from my (ugh!) Windows machine at work. I have to use shift-middle-button to paste in PuTTY.



              2018-03-30 Edit: I have now started using: :mouse= (no quotes or anything) on some remote (CentOS 6.7) instances of vim to get rid of undesired mouse effects.






              share|improve this answer

























              • Hi, thanks for the suggestion. I added this to my .vimrc file and tried executing it interactively (:set mouse=c), but neither had an effect in my case.

                – user001
                Aug 2 '12 at 2:14













              4












              4








              4







              I had pretty much the same complaints as you about the newer Vim's sensitivity to the mouse. Using set mouse="" did not do it for me, either.



              I have set mouse=c (no quotes) close to the bottom of my .vimrc file. That seemed to keep Vim from using the mouse, except when using "PuTTY" to ssh in from my (ugh!) Windows machine at work. I have to use shift-middle-button to paste in PuTTY.



              2018-03-30 Edit: I have now started using: :mouse= (no quotes or anything) on some remote (CentOS 6.7) instances of vim to get rid of undesired mouse effects.






              share|improve this answer















              I had pretty much the same complaints as you about the newer Vim's sensitivity to the mouse. Using set mouse="" did not do it for me, either.



              I have set mouse=c (no quotes) close to the bottom of my .vimrc file. That seemed to keep Vim from using the mouse, except when using "PuTTY" to ssh in from my (ugh!) Windows machine at work. I have to use shift-middle-button to paste in PuTTY.



              2018-03-30 Edit: I have now started using: :mouse= (no quotes or anything) on some remote (CentOS 6.7) instances of vim to get rid of undesired mouse effects.







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Mar 30 '18 at 15:12

























              answered Aug 2 '12 at 2:09









              Bruce EdigerBruce Ediger

              35.5k669120




              35.5k669120












              • Hi, thanks for the suggestion. I added this to my .vimrc file and tried executing it interactively (:set mouse=c), but neither had an effect in my case.

                – user001
                Aug 2 '12 at 2:14

















              • Hi, thanks for the suggestion. I added this to my .vimrc file and tried executing it interactively (:set mouse=c), but neither had an effect in my case.

                – user001
                Aug 2 '12 at 2:14
















              Hi, thanks for the suggestion. I added this to my .vimrc file and tried executing it interactively (:set mouse=c), but neither had an effect in my case.

              – user001
              Aug 2 '12 at 2:14





              Hi, thanks for the suggestion. I added this to my .vimrc file and tried executing it interactively (:set mouse=c), but neither had an effect in my case.

              – user001
              Aug 2 '12 at 2:14











              3














              Add this to your .vimrc:



              if has("gui_running")
              "echo "yes, we have a GUI"
              set mouse=a
              else
              "echo "Boring old console"
              set mouse=
              endif





              share|improve this answer




















              • 1





                This is of no relevance to the question asked.

                – GKFX
                Sep 24 '16 at 19:54











              • @GKFX Are you sure? It looks relevant to me. Note that has("gui_running") is 0 in a terminal environment. This answer, unlike the others, takes extra effort to only disable the mouse in a terminal environment, which the question asks, while leaving it enabled in gvim.

                – hvd
                Jul 29 '17 at 6:23











              • @hvd I worded my comment a bit harshly; I apologize. However, this answer just puts an if block around what the OP had already tried, so it's unlikely to be helpful.

                – GKFX
                Jul 29 '17 at 13:15






              • 1





                @GKFX Fair point, and applies to other answers as well.

                – hvd
                Jul 29 '17 at 13:23















              3














              Add this to your .vimrc:



              if has("gui_running")
              "echo "yes, we have a GUI"
              set mouse=a
              else
              "echo "Boring old console"
              set mouse=
              endif





              share|improve this answer




















              • 1





                This is of no relevance to the question asked.

                – GKFX
                Sep 24 '16 at 19:54











              • @GKFX Are you sure? It looks relevant to me. Note that has("gui_running") is 0 in a terminal environment. This answer, unlike the others, takes extra effort to only disable the mouse in a terminal environment, which the question asks, while leaving it enabled in gvim.

                – hvd
                Jul 29 '17 at 6:23











              • @hvd I worded my comment a bit harshly; I apologize. However, this answer just puts an if block around what the OP had already tried, so it's unlikely to be helpful.

                – GKFX
                Jul 29 '17 at 13:15






              • 1





                @GKFX Fair point, and applies to other answers as well.

                – hvd
                Jul 29 '17 at 13:23













              3












              3








              3







              Add this to your .vimrc:



              if has("gui_running")
              "echo "yes, we have a GUI"
              set mouse=a
              else
              "echo "Boring old console"
              set mouse=
              endif





              share|improve this answer















              Add this to your .vimrc:



              if has("gui_running")
              "echo "yes, we have a GUI"
              set mouse=a
              else
              "echo "Boring old console"
              set mouse=
              endif






              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Apr 8 '13 at 2:46









              Michael Mrozek

              62k29193213




              62k29193213










              answered Apr 8 '13 at 1:26









              ipirloipirlo

              311




              311







              • 1





                This is of no relevance to the question asked.

                – GKFX
                Sep 24 '16 at 19:54











              • @GKFX Are you sure? It looks relevant to me. Note that has("gui_running") is 0 in a terminal environment. This answer, unlike the others, takes extra effort to only disable the mouse in a terminal environment, which the question asks, while leaving it enabled in gvim.

                – hvd
                Jul 29 '17 at 6:23











              • @hvd I worded my comment a bit harshly; I apologize. However, this answer just puts an if block around what the OP had already tried, so it's unlikely to be helpful.

                – GKFX
                Jul 29 '17 at 13:15






              • 1





                @GKFX Fair point, and applies to other answers as well.

                – hvd
                Jul 29 '17 at 13:23












              • 1





                This is of no relevance to the question asked.

                – GKFX
                Sep 24 '16 at 19:54











              • @GKFX Are you sure? It looks relevant to me. Note that has("gui_running") is 0 in a terminal environment. This answer, unlike the others, takes extra effort to only disable the mouse in a terminal environment, which the question asks, while leaving it enabled in gvim.

                – hvd
                Jul 29 '17 at 6:23











              • @hvd I worded my comment a bit harshly; I apologize. However, this answer just puts an if block around what the OP had already tried, so it's unlikely to be helpful.

                – GKFX
                Jul 29 '17 at 13:15






              • 1





                @GKFX Fair point, and applies to other answers as well.

                – hvd
                Jul 29 '17 at 13:23







              1




              1





              This is of no relevance to the question asked.

              – GKFX
              Sep 24 '16 at 19:54





              This is of no relevance to the question asked.

              – GKFX
              Sep 24 '16 at 19:54













              @GKFX Are you sure? It looks relevant to me. Note that has("gui_running") is 0 in a terminal environment. This answer, unlike the others, takes extra effort to only disable the mouse in a terminal environment, which the question asks, while leaving it enabled in gvim.

              – hvd
              Jul 29 '17 at 6:23





              @GKFX Are you sure? It looks relevant to me. Note that has("gui_running") is 0 in a terminal environment. This answer, unlike the others, takes extra effort to only disable the mouse in a terminal environment, which the question asks, while leaving it enabled in gvim.

              – hvd
              Jul 29 '17 at 6:23













              @hvd I worded my comment a bit harshly; I apologize. However, this answer just puts an if block around what the OP had already tried, so it's unlikely to be helpful.

              – GKFX
              Jul 29 '17 at 13:15





              @hvd I worded my comment a bit harshly; I apologize. However, this answer just puts an if block around what the OP had already tried, so it's unlikely to be helpful.

              – GKFX
              Jul 29 '17 at 13:15




              1




              1





              @GKFX Fair point, and applies to other answers as well.

              – hvd
              Jul 29 '17 at 13:23





              @GKFX Fair point, and applies to other answers as well.

              – hvd
              Jul 29 '17 at 13:23











              0














              Somewhat related to the question, if you are using neovim(nvim) you should put set mouse= in your ~/.config/nvim/init.vim configuration file.



              If the directory doesn't exist create it with mkdir -p ~/.config/nvim/






              share|improve this answer



























                0














                Somewhat related to the question, if you are using neovim(nvim) you should put set mouse= in your ~/.config/nvim/init.vim configuration file.



                If the directory doesn't exist create it with mkdir -p ~/.config/nvim/






                share|improve this answer

























                  0












                  0








                  0







                  Somewhat related to the question, if you are using neovim(nvim) you should put set mouse= in your ~/.config/nvim/init.vim configuration file.



                  If the directory doesn't exist create it with mkdir -p ~/.config/nvim/






                  share|improve this answer













                  Somewhat related to the question, if you are using neovim(nvim) you should put set mouse= in your ~/.config/nvim/init.vim configuration file.



                  If the directory doesn't exist create it with mkdir -p ~/.config/nvim/







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Mar 26 '18 at 14:29









                  Marcelo LacerdaMarcelo Lacerda

                  1011




                  1011





















                      0














                      On debian stretch some central settings are loaded after loading /etc/vim/vimrc and /etc/vim/vimrc.local. See /etc/vim/vimrc:



                      ...
                      " Vim will load $VIMRUNTIME/defaults.vim if the user does not have a vimrc.
                      " This happens after /etc/vim/vimrc(.local) are loaded, so it will override
                      " any settings in these files.
                      " If you don't want that to happen, uncomment the below line to prevent
                      " defaults.vim from being loaded.
                      "let g:skip_defaults_vim = 1
                      ...


                      This files defaults to /usr/share/vim/vim80/defaults.vim. Now changing a central file under /usr/share/... is



                      • evil

                      • non-permanent, it gets reverted after an update

                      Setting skip_defaults_vim by uncommentig the above line removes all other options set by that file. To just remove the unwanted options put the following into /etc/vimrc.local:



                      " /etc/vim/vimrc.local
                      " honor skip_defaults_vim from the master /etc/vim/vimrc file
                      if ! exists('skip_defaults_vim')
                      " Source the defaults file manually from here
                      source $VIMRUNTIME/defaults.vim
                      endif

                      " avoid loading the defaults twice
                      let g:skip_defaults_vim = 1

                      " revert any unwanted changes the defaults file introduced
                      set mouse=

                      " set any other options you want centrally on your system
                      "set paste " uncomment if you want paste insert enabled
                      "...


                      This loads the defaults.vim manually and turns off the automatic loading, thus giving you a chance to revert any unwanted settings, without having to create a .vimrc for every user account.






                      share|improve this answer





























                        0














                        On debian stretch some central settings are loaded after loading /etc/vim/vimrc and /etc/vim/vimrc.local. See /etc/vim/vimrc:



                        ...
                        " Vim will load $VIMRUNTIME/defaults.vim if the user does not have a vimrc.
                        " This happens after /etc/vim/vimrc(.local) are loaded, so it will override
                        " any settings in these files.
                        " If you don't want that to happen, uncomment the below line to prevent
                        " defaults.vim from being loaded.
                        "let g:skip_defaults_vim = 1
                        ...


                        This files defaults to /usr/share/vim/vim80/defaults.vim. Now changing a central file under /usr/share/... is



                        • evil

                        • non-permanent, it gets reverted after an update

                        Setting skip_defaults_vim by uncommentig the above line removes all other options set by that file. To just remove the unwanted options put the following into /etc/vimrc.local:



                        " /etc/vim/vimrc.local
                        " honor skip_defaults_vim from the master /etc/vim/vimrc file
                        if ! exists('skip_defaults_vim')
                        " Source the defaults file manually from here
                        source $VIMRUNTIME/defaults.vim
                        endif

                        " avoid loading the defaults twice
                        let g:skip_defaults_vim = 1

                        " revert any unwanted changes the defaults file introduced
                        set mouse=

                        " set any other options you want centrally on your system
                        "set paste " uncomment if you want paste insert enabled
                        "...


                        This loads the defaults.vim manually and turns off the automatic loading, thus giving you a chance to revert any unwanted settings, without having to create a .vimrc for every user account.






                        share|improve this answer



























                          0












                          0








                          0







                          On debian stretch some central settings are loaded after loading /etc/vim/vimrc and /etc/vim/vimrc.local. See /etc/vim/vimrc:



                          ...
                          " Vim will load $VIMRUNTIME/defaults.vim if the user does not have a vimrc.
                          " This happens after /etc/vim/vimrc(.local) are loaded, so it will override
                          " any settings in these files.
                          " If you don't want that to happen, uncomment the below line to prevent
                          " defaults.vim from being loaded.
                          "let g:skip_defaults_vim = 1
                          ...


                          This files defaults to /usr/share/vim/vim80/defaults.vim. Now changing a central file under /usr/share/... is



                          • evil

                          • non-permanent, it gets reverted after an update

                          Setting skip_defaults_vim by uncommentig the above line removes all other options set by that file. To just remove the unwanted options put the following into /etc/vimrc.local:



                          " /etc/vim/vimrc.local
                          " honor skip_defaults_vim from the master /etc/vim/vimrc file
                          if ! exists('skip_defaults_vim')
                          " Source the defaults file manually from here
                          source $VIMRUNTIME/defaults.vim
                          endif

                          " avoid loading the defaults twice
                          let g:skip_defaults_vim = 1

                          " revert any unwanted changes the defaults file introduced
                          set mouse=

                          " set any other options you want centrally on your system
                          "set paste " uncomment if you want paste insert enabled
                          "...


                          This loads the defaults.vim manually and turns off the automatic loading, thus giving you a chance to revert any unwanted settings, without having to create a .vimrc for every user account.






                          share|improve this answer















                          On debian stretch some central settings are loaded after loading /etc/vim/vimrc and /etc/vim/vimrc.local. See /etc/vim/vimrc:



                          ...
                          " Vim will load $VIMRUNTIME/defaults.vim if the user does not have a vimrc.
                          " This happens after /etc/vim/vimrc(.local) are loaded, so it will override
                          " any settings in these files.
                          " If you don't want that to happen, uncomment the below line to prevent
                          " defaults.vim from being loaded.
                          "let g:skip_defaults_vim = 1
                          ...


                          This files defaults to /usr/share/vim/vim80/defaults.vim. Now changing a central file under /usr/share/... is



                          • evil

                          • non-permanent, it gets reverted after an update

                          Setting skip_defaults_vim by uncommentig the above line removes all other options set by that file. To just remove the unwanted options put the following into /etc/vimrc.local:



                          " /etc/vim/vimrc.local
                          " honor skip_defaults_vim from the master /etc/vim/vimrc file
                          if ! exists('skip_defaults_vim')
                          " Source the defaults file manually from here
                          source $VIMRUNTIME/defaults.vim
                          endif

                          " avoid loading the defaults twice
                          let g:skip_defaults_vim = 1

                          " revert any unwanted changes the defaults file introduced
                          set mouse=

                          " set any other options you want centrally on your system
                          "set paste " uncomment if you want paste insert enabled
                          "...


                          This loads the defaults.vim manually and turns off the automatic loading, thus giving you a chance to revert any unwanted settings, without having to create a .vimrc for every user account.







                          share|improve this answer














                          share|improve this answer



                          share|improve this answer








                          edited yesterday

























                          answered Mar 16 at 19:50









                          Holger BöhnkeHolger Böhnke

                          1012




                          1012



























                              draft saved

                              draft discarded
















































                              Thanks for contributing an answer to Unix & Linux Stack Exchange!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid


                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.

                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f44513%2fdisabling-mouse-support-in-vim-in-a-gnome-terminal-environment%23new-answer', 'question_page');

                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              Àrd-bhaile Cathair chruinne/Baile mòr cruinne | Artagailean ceangailte | Clàr-taice na seòladaireachd

                              Cannot Extend partition with GParted The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election ResultsCan't increase partition size with GParted?GParted doesn't recognize the unallocated space after my current partitionWhat is the best way to add unallocated space located before to Ubuntu 12.04 partition with GParted live?I can't figure out how to extend my Arch home partition into free spaceGparted Linux Mint 18.1 issueTrying to extend but swap partition is showing as Unknown in Gparted, shows proper from fdiskRearrange partitions in gparted to extend a partitionUnable to extend partition even though unallocated space is next to it using GPartedAllocate free space to root partitiongparted: how to merge unallocated space with a partition

                              대한민국 목차 국명 지리 역사 정치 국방 경제 사회 문화 국제 순위 관련 항목 각주 외부 링크 둘러보기 메뉴북위 37° 34′ 08″ 동경 126° 58′ 36″ / 북위 37.568889° 동경 126.976667°  / 37.568889; 126.976667ehThe Korean Repository문단을 편집문단을 편집추가해Clarkson PLC 사Report for Selected Countries and Subjects-Korea“Human Development Index and its components: P.198”“http://www.law.go.kr/%EB%B2%95%EB%A0%B9/%EB%8C%80%ED%95%9C%EB%AF%BC%EA%B5%AD%EA%B5%AD%EA%B8%B0%EB%B2%95”"한국은 국제법상 한반도 유일 합법정부 아니다" - 오마이뉴스 모바일Report for Selected Countries and Subjects: South Korea격동의 역사와 함께한 조선일보 90년 : 조선일보 인수해 혁신시킨 신석우, 임시정부 때는 '대한민국' 국호(國號) 정해《우리가 몰랐던 우리 역사: 나라 이름의 비밀을 찾아가는 역사 여행》“남북 공식호칭 ‘남한’‘북한’으로 쓴다”“Corea 대 Korea, 누가 이긴 거야?”국내기후자료 - 한국[김대중 前 대통령 서거] 과감한 구조개혁 'DJ노믹스'로 최단기간 환란극복 :: 네이버 뉴스“이라크 "韓-쿠르드 유전개발 MOU 승인 안해"(종합)”“해외 우리국민 추방사례 43%가 일본”차기전차 K2'흑표'의 세계 최고 전력 분석, 쿠키뉴스 엄기영, 2007-03-02두산인프라, 헬기잡는 장갑차 'K21'...내년부터 공급, 고뉴스 이대준, 2008-10-30과거 내용 찾기mk 뉴스 - 구매력 기준으로 보면 한국 1인당 소득 3만弗과거 내용 찾기"The N-11: More Than an Acronym"Archived조선일보 최우석, 2008-11-01Global 500 2008: Countries - South Korea“몇년째 '시한폭탄'... 가계부채, 올해는 터질까”가구당 부채 5000만원 처음 넘어서“‘빚’으로 내몰리는 사회.. 위기의 가계대출”“[경제365] 공공부문 부채 급증…800조 육박”“"소득 양극화 다소 완화...불평등은 여전"”“공정사회·공생발전 한참 멀었네”iSuppli,08年2QのDRAMシェア・ランキングを発表(08/8/11)South Korea dominates shipbuilding industry | Stock Market News & Stocks to Watch from StraightStocks한국 자동차 생산, 3년 연속 세계 5위자동차수출 '현대-삼성 웃고 기아-대우-쌍용은 울고' 과거 내용 찾기동반성장위 창립 1주년 맞아Archived"중기적합 3개업종 합의 무시한 채 선정"李대통령, 사업 무분별 확장 소상공인 생계 위협 질타삼성-LG, 서민업종인 빵·분식사업 잇따라 철수상생은 뒷전…SSM ‘몸집 불리기’ 혈안Archived“경부고속도에 '아시안하이웨이' 표지판”'철의 실크로드' 앞서 '말(言)의 실크로드'부터, 프레시안 정창현, 2008-10-01“'서울 지하철은 안전한가?'”“서울시 “올해 안에 모든 지하철역 스크린도어 설치””“부산지하철 1,2호선 승강장 안전펜스 설치 완료”“전교조, 정부 노조 통계서 처음 빠져”“[Weekly BIZ] 도요타 '제로 이사회'가 리콜 사태 불러들였다”“S Korea slams high tuition costs”““정치가 여론 양극화 부채질… 합리주의 절실””“〈"`촛불집회'는 민주주의의 질적 변화 상징"〉”““촛불집회가 민주주의 왜곡 초래””“국민 65%, "한국 노사관계 대립적"”“한국 국가경쟁력 27위‥노사관계 '꼴찌'”“제대로 형성되지 않은 대한민국 이념지형”“[신년기획-갈등의 시대] 갈등지수 OECD 4위…사회적 손실 GDP 27% 무려 300조”“2012 총선-대선의 키워드는 '국민과 소통'”“한국 삶의 질 27위, 2000년과 2008년 연속 하위권 머물러”“[해피 코리아] 행복점수 68점…해외 평가선 '낙제점'”“한국 어린이·청소년 행복지수 3년 연속 OECD ‘꼴찌’”“한국 이혼율 OECD중 8위”“[통계청] 한국 이혼율 OECD 4위”“오피니언 [이렇게 생각한다] `부부의 날` 에 돌아본 이혼율 1위 한국”“Suicide Rates by Country, Global Health Observatory Data Repository.”“1. 또 다른 차별”“오피니언 [편집자에게] '왕따'와 '패거리 정치' 심리는 닮은꼴”“[미래한국리포트] 무한경쟁에 빠진 대한민국”“대학생 98% "외모가 경쟁력이라는 말 동의"”“특급호텔 웨딩·200만원대 유모차… "남보다 더…" 호화病, 고질병 됐다”“[스트레스 공화국] ① 경쟁사회, 스트레스 쌓인다”““매일 30여명 자살 한국, 의사보다 무속인에…””“"자살 부르는 '우울증', 환자 중 85% 치료 안 받아"”“정신병원을 가다”“대한민국도 ‘묻지마 범죄’,안전지대 아니다”“유엔 "학생 '성적 지향'에 따른 차별 금지하라"”“유엔아동권리위원회 보고서 및 번역본 원문”“고졸 성공스토리 담은 '제빵왕 김탁구' 드라마 나온다”“‘빛 좋은 개살구’ 고졸 취업…실습 대신 착취”원본 문서“정신건강, 사회적 편견부터 고쳐드립니다”‘소통’과 ‘행복’에 목 마른 사회가 잠들어 있던 ‘심리학’ 깨웠다“[포토] 사유리-곽금주 교수의 유쾌한 심리상담”“"올해 한국인 평균 영화관람횟수 세계 1위"(종합)”“[게임연중기획] 게임은 문화다-여가활동 1순위 게임”“영화속 ‘영어 지상주의’ …“왠지 씁쓸한데””“2월 `신문 부수 인증기관` 지정..방송법 후속작업”“무료신문 성장동력 ‘차별성’과 ‘갈등해소’”대한민국 국회 법률지식정보시스템"Pew Research Center's Religion & Public Life Project: South Korea"“amp;vwcd=MT_ZTITLE&path=인구·가구%20>%20인구총조사%20>%20인구부문%20>%20 총조사인구(2005)%20>%20전수부문&oper_YN=Y&item=&keyword=종교별%20인구& amp;lang_mode=kor&list_id= 2005년 통계청 인구 총조사”원본 문서“한국인이 좋아하는 취미와 운동 (2004-2009)”“한국인이 좋아하는 취미와 운동 (2004-2014)”Archived“한국, `부분적 언론자유국' 강등〈프리덤하우스〉”“국경없는기자회 "한국, 인터넷감시 대상국"”“한국, 조선산업 1위 유지(S. Korea Stays Top Shipbuilding Nation) RZD-Partner Portal”원본 문서“한국, 4년 만에 ‘선박건조 1위’”“옛 마산시,인터넷속도 세계 1위”“"한국 초고속 인터넷망 세계1위"”“인터넷·휴대폰 요금, 외국보다 훨씬 비싸”“한국 관세행정 6년 연속 세계 '1위'”“한국 교통사고 사망자 수 OECD 회원국 중 2위”“결핵 후진국' 한국, 환자가 급증한 이유는”“수술은 신중해야… 자칫하면 생명 위협”대한민국분류대한민국의 지도대한민국 정부대표 다국어포털대한민국 전자정부대한민국 국회한국방송공사about korea and information korea브리태니커 백과사전(한국편)론리플래닛의 정보(한국편)CIA의 세계 정보(한국편)마리암 부디아 (Mariam Budia),『한국: 하늘이 내린 한 폭의 그림』, 서울: 트랜스라틴 19호 (2012년 3월)대한민국ehehehehehehehehehehehehehehWorldCat132441370n791268020000 0001 2308 81034078029-6026373548cb11863345f(데이터)00573706ge128495