Tony Mechelynck <antoine.mechely...@gmail.com> writes: >> Typing in an xterm: >> xterm -version >> XTerm(256) > > Hm. Here (on openSUSE Linux 11.2) the answer is: > > X.Org 6.8.99.903(242)
Its starting to look like that might be the culprit... my later version of xterm.... I haven't installed an older version to test yet. > not star-bigpee but doublequote-star-bigpee. When used at the keyboard > in Normal mode, this means "put the X selection before the cursor". Or > use a lowercase p instead of an uppercase (i.e. shifted) P to put > after. Or use + (plus) instead of * (star) between the " (double > quote) and the P or p to put from the clipboard (as with Edit=>Paste) > instead of the X11 selection (as with middle-click). (Note: Vim > terminology uses "put", "yank" and "delete" instead of "paste" "copy" > and "cut" respectively. Any register can be involved.) Thanks for `"*P'... I didn't now that trick.. and it pastes flawlessly. It's handy in that it doesn't need vim to be in insert mode. I often lose little bits of pasted code trying to paste into vim with middle mouse when vim is NOT in insert mode. (Might lose a few characters, until vim sees one that turns on insert mode) Might take awhile to acclimate my retarded hands to use "*P, its a little awkward to hit quickly. But I suppose it could become like `:wq' if I used it often enough. One thing though... I don't see a bit of difference when using upper or lower case P/p. The pasting goes ahead of the cursor in either case. If I open vim, go to insert mode... and scroll down a few lines so I can tell where a paste/put is going.... then back to normal mode, and put some perl code with `"*P', clear that out and try it again with `"*p'... either way the code goes in ahead of the cursor. > But I usually use gvim, or sometimes Vim in konsole or in the > pure-text Linux console (accessed by Ctrl-Alt-F1 fot /dev/tty1 to > Ctrl-Alt-F6 for /dev/tty6, come back to X by Ctrl-Alt-F7). The latter > is very handy when I decide to boot without X (into runlevel 3 instead > of the default 5) for maximum throughput of console-only operations. Yeah, I used to use that often... here's another one. Ctrl-alt-F2 to get a new vt in console mode... then `startx -- :1 (starts another X session on a different display) You can go back to the first Xsession with C-A-7, or back to the second one with C-A-8. Its a way to startx after making changes to .Xdefaults or whatever, and see what any changes did, without have to back out of your current session. Or restart it. -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
