Bug#544396: please try changes to your .Xdefaults

2009-10-12 Thread Harald Dunkel
Hi Robert, sorry to say, but setting these X resources did not work. Even *allowWindowOps:true *allowTitleOps: true *allowFontOps: true did not help. Can you reproduce the problem? Regards Harri -- To UNSUBSCRIBE, email to

Bug#544396: please try changes to your .Xdefaults

2009-10-12 Thread Robert Lemmen
On Mon, Oct 12, 2009 at 09:46:21AM +0200, Harald Dunkel wrote: sorry to say, but setting these X resources did not work. Even *allowWindowOps:true *allowTitleOps: true *allowFontOps: true did not help. Can you reproduce the problem? odd, i

Bug#544396: please try changes to your .Xdefaults

2009-10-12 Thread Harald Dunkel
Robert Lemmen wrote: odd, i can reproduce it on different machines with different window managers. have you done the xrdb -merge, and restarted the xterm? Thats it, I missed to try it in a new xterm (doh). I would guess the trouble shooting section of xtermcontrol(1) is out-of-date? AFAICS

Bug#544396: please try changes to your .Xdefaults

2009-10-12 Thread Robert Lemmen
On Mon, Oct 12, 2009 at 02:36:04PM +0200, Harald Dunkel wrote: Thats it, I missed to try it in a new xterm (doh). heh, no problem, i fail on that every single time, along with adding users to groups and not logging them back in... I would guess the trouble shooting section of xtermcontrol(1)

Bug#544396: please try changes to your .Xdefaults

2009-10-05 Thread Robert Lemmen
hi harald, could you try adding these to your .Xdefaults: *VT100.allowWindowOps: true *VT100.allowTitleOps: true *VT100.allowFontOps: true you can avoid X restarts by doing a xrdb -merge ~/.Xdefaults afterwards. thanks robert -- Robert Lemmen