> "Benjamin R. Haskell" writes:
>
> > [...] adding the line:
> > UXTerm*allowWindowOps: true
> > to my ~/.Xdefaults file solved the problem[...]
>
> I tried... putting `UXTerm*allowWindowOps true'' into .Xdefaults
My line may have been too specific. In the bug report my previous post
referenced[1], the line causing problems was the more general:
*allowWindowOps: false
I used UXTerm in mine, because... well... I use uxterm. So, maybe try
without the class name (UXTerm):
*allowWindowOps: true
or with the class name for xterm proper (XTerm):
XTerm*allowWindowOps: true
> [...] 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
For future reference/further testing, you can use the 'xrdb' program
(x11-apps/xrdb in Gentoo) to alter your X resources in various ways.
E.g. to fully reload:
$ xrdb ~/.Xdefaults
To see current:
$ xrdb -q
$ xrdb -q | grep allowWindowOps
--
Best,
Ben
[1] http://bugs.gentoo.org/91453
>
> 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