My .vimrc file disabled the copy/paste action using mouse right click!
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
Am using an open source .vimrc file from GitHub, but it is screwing up my default mouse right click, copy-paste actions. Whenever I do a right click, it enters into the visual mode and I am having a hard time, doing a copy-paste when I'm inter-working with my Windows machine.
Let me know what .vimrc config lines to delete.
Am running a Red Hat Enterprise Linux Server release 5.4 (Tikanga)
linux vim rc
edited Nov 30 at 20:21
Michael Prokopec
78716
asked Apr 24 '15 at 10:11
Inian
3,815824
migrated from programmers.stackexchange.com Apr 24 '15 at 10:54
This question came from our site for professionals, academics, and students working within the systems development life cycle.
add a comment |
up vote
2
down vote
favorite
Am using an open source .vimrc file from GitHub, but it is screwing up my default mouse right click, copy-paste actions. Whenever I do a right click, it enters into the visual mode and I am having a hard time, doing a copy-paste when I'm inter-working with my Windows machine.
Let me know what .vimrc config lines to delete.
Am running a Red Hat Enterprise Linux Server release 5.4 (Tikanga)
linux vim rc
edited Nov 30 at 20:21
Michael Prokopec
78716
asked Apr 24 '15 at 10:11
Inian
3,815824
migrated from programmers.stackexchange.com Apr 24 '15 at 10:54
This question came from our site for professionals, academics, and students working within the systems development life cycle.
In the file you propose, lines 105 -- 108 mention the mouse. Have you tried removing these ?
– Vincent Nivoliers
Apr 24 '15 at 10:58
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Am using an open source .vimrc file from GitHub, but it is screwing up my default mouse right click, copy-paste actions. Whenever I do a right click, it enters into the visual mode and I am having a hard time, doing a copy-paste when I'm inter-working with my Windows machine.
Let me know what .vimrc config lines to delete.
Am running a Red Hat Enterprise Linux Server release 5.4 (Tikanga)
linux vim rc
edited Nov 30 at 20:21
Michael Prokopec
78716
asked Apr 24 '15 at 10:11
Inian
3,815824
Am using an open source .vimrc file from GitHub, but it is screwing up my default mouse right click, copy-paste actions. Whenever I do a right click, it enters into the visual mode and I am having a hard time, doing a copy-paste when I'm inter-working with my Windows machine.
Let me know what .vimrc config lines to delete.
Am running a Red Hat Enterprise Linux Server release 5.4 (Tikanga)
linux vim rc
linux vim rc
edited Nov 30 at 20:21
Michael Prokopec
78716
asked Apr 24 '15 at 10:11
Inian
3,815824
edited Nov 30 at 20:21
Michael Prokopec
78716
asked Apr 24 '15 at 10:11
Inian
3,815824
edited Nov 30 at 20:21
Michael Prokopec
78716
edited Nov 30 at 20:21
Michael Prokopec
78716
edited Nov 30 at 20:21
Michael Prokopec
78716
78716
asked Apr 24 '15 at 10:11
Inian
3,815824
asked Apr 24 '15 at 10:11
Inian
3,815824
asked Apr 24 '15 at 10:11
Inian
3,815824
3,815824
migrated from programmers.stackexchange.com Apr 24 '15 at 10:54
This question came from our site for professionals, academics, and students working within the systems development life cycle.
migrated from programmers.stackexchange.com Apr 24 '15 at 10:54
This question came from our site for professionals, academics, and students working within the systems development life cycle.
In the file you propose, lines 105 -- 108 mention the mouse. Have you tried removing these ?
– Vincent Nivoliers
Apr 24 '15 at 10:58
add a comment |
In the file you propose, lines 105 -- 108 mention the mouse. Have you tried removing these ?
– Vincent Nivoliers
Apr 24 '15 at 10:58
In the file you propose, lines 105 -- 108 mention the mouse. Have you tried removing these ?
– Vincent Nivoliers
Apr 24 '15 at 10:58
In the file you propose, lines 105 -- 108 mention the mouse. Have you tried removing these ?
– Vincent Nivoliers
Apr 24 '15 at 10:58
add a comment |
1 Answer
1
active
oldest
votes
up vote
3
down vote
accepted
As @VincentNivoliers said in his comment, your issue comes from the line mouse=a.
It enables the mouse in all modes of vim, ie letting you put the cursor where you click.
a means this is active in all modes. If you don't want vim to care about your mouse, just set mouse= (no value). Then, you could use your mouse to copy'n'paste from your clipboard as in a terminal.
From vim documentation:
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
answered Apr 24 '15 at 11:50
apaul
2,4101712
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
As @VincentNivoliers said in his comment, your issue comes from the line mouse=a.
It enables the mouse in all modes of vim, ie letting you put the cursor where you click.
a means this is active in all modes. If you don't want vim to care about your mouse, just set mouse= (no value). Then, you could use your mouse to copy'n'paste from your clipboard as in a terminal.
From vim documentation:
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
answered Apr 24 '15 at 11:50
apaul
2,4101712
add a comment |
up vote
3
down vote
accepted
As @VincentNivoliers said in his comment, your issue comes from the line mouse=a.
It enables the mouse in all modes of vim, ie letting you put the cursor where you click.
a means this is active in all modes. If you don't want vim to care about your mouse, just set mouse= (no value). Then, you could use your mouse to copy'n'paste from your clipboard as in a terminal.
From vim documentation:
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
answered Apr 24 '15 at 11:50
apaul
2,4101712
add a comment |
up vote
3
down vote
accepted
up vote
3
down vote
accepted
As @VincentNivoliers said in his comment, your issue comes from the line mouse=a.
It enables the mouse in all modes of vim, ie letting you put the cursor where you click.
a means this is active in all modes. If you don't want vim to care about your mouse, just set mouse= (no value). Then, you could use your mouse to copy'n'paste from your clipboard as in a terminal.
From vim documentation:
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
answered Apr 24 '15 at 11:50
apaul
2,4101712
As @VincentNivoliers said in his comment, your issue comes from the line mouse=a.
It enables the mouse in all modes of vim, ie letting you put the cursor where you click.
a means this is active in all modes. If you don't want vim to care about your mouse, just set mouse= (no value). Then, you could use your mouse to copy'n'paste from your clipboard as in a terminal.
From vim documentation:
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
answered Apr 24 '15 at 11:50
apaul
2,4101712
answered Apr 24 '15 at 11:50
apaul
2,4101712
answered Apr 24 '15 at 11:50
apaul
2,4101712
answered Apr 24 '15 at 11:50
apaul
2,4101712
2,4101712
add a comment |
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f198353%2fmy-vimrc-file-disabled-the-copy-paste-action-using-mouse-right-click%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
In the file you propose, lines 105 -- 108 mention the mouse. Have you tried removing these ?
– Vincent Nivoliers
Apr 24 '15 at 10:58