[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#25689: xbase: Delete mapping in Xresources wrong if connecting from remote



Mr Brian May writes:
 > > > 
 > > > What happens if you change the given lines to:
 > > > 
 > > > *VT100.Translations: #override <Key>Home: string("\033OH")\n\
 > > >                                <Key>End: string("\033OF")
 > >
 > >This was my fix. Than it is working. But I haven't checked this if I
 > >log in directly int the Debian server. (Will report on this later.)
 > 
 > I think I know what your problem is. I think some X-Servers (including
 > this Ultrix 4.4 server I am currently using ;-) ), generate the
 > "Delete" keycode instead "Backspace" (I think). You can verify this
 > using a program like xkeycaps.

No, wrong. xev shows that the xserver generates correct Backspace and
Delete keycodes. 

 > 
 > I think the "Delete" keycode is meant to be delete to the right, and
 > the "Backspace" keycode is meant to be delete to the left.
 > I don't have access to a Debian system at the moment, so I can't
 > test this.  I wonder if this behaviour is standardized by X? If so,
 > it would mean the server is non-compliant.
 > 
 > I suspect your fix will break the behaviour of "Delete" under the
 > Debian server :-(
 > 
 > Solutions? Perhaps you can edit your .xsession to change your xresources
 > entries using xrdb depending on the value of "$DISPLAY"? Not
 > a very good solution though.

This is really not a problem with my personal setup. We use different
UNIXes (Solaris, HP-UX, AIX, IRIX, BSD, DUX ...) all over the
university campus and the "Debian Way" will brake it everywhere.

 > 
 > If anyone has any better ideas...

I think everything came in with the invention of "xterm-debian" to
introduce the new xterm features. But the current way to implement it
(xterm-name and VT100.Translations in Xresources) is just not the
right way to implement it.

You can get working if you reset TERM to xterm, but then you loose the
new features (like color etc.) of the new xterm.

The central issue is: Don't put defines which are essential for the
correct working of applications on Debian systems but break it on all
other systems into /etc/X11/Xresourses, because people could login to
the system other ways.

Christoph


Reply to: