[...]
>> Not some gnome terminal, KDE terminal or some other jive.. just a
>> regular xterm.
>
> I also use Gentoo.
>
> xterm-256 wasn't in portage a couple months ago, so your terminal has
> certainly changed in the last few months. Using all combinations of
> vim-7.2.{182,411} and xterm-{223,256}, though, I see the undesired
> behavior. It looks like older xterms (including 243, which was what I
> had installed when I started exploring this) have a USE-flag called
> 'paste64', which apparently adds the --enable-paste64 compile flag.
>
> My guess is that --enable-paste64 (which is no longer in the ebuild) is
> essentially built-in at this point.
>
> Upgrading back to xterm-256 and adding the line:
> UXTerm*allowWindowOps: true
> to my ~/.Xdefaults file solved the problem[1]. IIUC, this enables
> 'bracketed paste' mode[2] (possibly other things?), but may have
> security implications[1b].
I tried... putting `UXTerm*allowWindowOps true'' into .Xdefaults
which over the years I've ended up symlinking to .Xresources and
.xresources
So all were covered.
Started a second X session by first `Ctrl-Alt F2' to get a different
vt in console mode... then `startx -- :1'
Starting X on a different display, which should have activated anthing
new in ~/.Xdefaults, but I still see the stair stepping
However the technique Tony M mentioned: "*P
(Double Quote Asterisk Upper/lowercase P/p) works without stair
stepping. ... I didn't now that trick....
You don't have to be in insert mode which is handy... often I loose a
few characters from a piece of pasting because vim was in command or
maybe its normal mode, and I try to paste with middle mouse.
--
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
No comments:
Post a Comment