> 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
Yeck... I should have caught that but instead just blindly pasted it
in there.
But anyway, it doesn't help with no `class' selector either.
[...]
> 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
Thanks .. thats one of those things I knew all about 4-5 yrs ago but
haven't used much for a few yrs.. and it just left my pea brain
altogether.
But even after refreshing with xrdb ~/.Xdefaults after removing the
`class' selector I still see the same old stair stepping.
Looks like the fartherest back I could downgrade on current portage
would be xterm 250.
I might try that later.
--
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