On 2009-12-08, Peter Princz wrote: > Dear vimmers on this list, > > please help me with my problem, it is driving me crazy, I'm giving up. It is > the flip question that we normally have, i.e. I cannot reproduce a behaviour > on > a fresh install that works as expected on my machine, I just can't remember > how > did I this. > > I am on gvim 7.2 in parallel on linux and windows. > Have one vimrc file that is named as _vimrc on windows and .gvimrc on linux. I > am using ctrl-ins, shift-ins for copy/paste on windows as well, ctrl-v is > vsual > block in both environments. > Everything is fine, I could not be happier, and I haven't touch these _vimrc > /.gvimrc files this year. > Ironically, even mswin.vim is left as sourced i.e. not commented out, yet > everything works. > > ...And then my colleague walked by and became envy on my ctrl-v and clipboard > handling shortcuts. But I cannot reproduce my settings at his machine. > My _vimrc is 10 kBytes, my colleague would want just the needed settings to be > merged into his _vimrc. > I've been playing around half on hour by toggling on/off the settings one by > one I have in _vimrc but still no luck. > :map shows ctrl-v is not mapped at all, I cannot comprehend how ctrl-v does > not > paste on a windows machine. Even worse, I did that somehow, but cannot > remember > how.
In Vim alone, when it doesn't source a _vimrc and Ctrl-V is left unmapped, Ctrl-V performs visual-block selection, not paste. The only reason Ctrl-V performs paste on some Vim installations is because the user has mapped it to do so, either explicitly in his _vimrc or by sourcing $VIMRUNTIME/mswin.vim in his _vimrc. The standard Vim installation on Windows includes a _vimrc that sources $VIMRUNTIME/mswin.vim, so that Ctrl-V is mapped to perform paste. In your case, since you say you are sourcing $VIMRUNTIME/mswin.vim, you must either have modified your mswin.vim to not map Ctrl-V, or you are unmapping Ctrl-V in your _vimrc or in another plugin. > It does paste in all other applications, so I must have done > something within vim and not on Windows level. > I did find the unix like ctrl-ins, shift-ins copy/paste > definition, but not ctrl-v to visual mode mapping. To be clear, there is no Ctrl-V to visual-block mode mapping--that is Ctrl-V's unmapped behavior. HTH, Gary -- You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php
