On: Thu, 18 Jun 1998 16:41:28 -0700 (PDT) Micha Feigin writes:
> 
> I'm having trouble configuring the keyboard under x.  It used to
> work ok once, i don't know what i changed but the delete and
> backspace keys don't work. The backspace sends ~ signs (or at list
> thats how they apear) and delete sends .  they both beep when i
> press them. when i use ^d and ^h it works fine.  also the alt key
> won't work as meta.

This is probably a xterm problem.  I recently changed my xterm
settings to let Meta and Alt both work as Meta as recognized by the
zsh (i.e., Meta-D deletes the current word):

XTerm*VT100.Translations: #override \
   Meta<KeyPress>Shift_L,Meta<KeyPress>: string(0x01B) insert() \n\
   Meta<KeyPress>Shift_R,Meta<KeyPress>: string(0x01B) insert() \n\
   Meta Ctrl <KeyPress>: string(0x01B) insert() \n\
   Meta      <KeyPress>: string(0x01B) insert() \n\
   Alt<KeyPress>Shift_L,Alt<KeyPress>: string(0x01B) insert() \n\
   Alt<KeyPress>Shift_R,Alt<KeyPress>: string(0x01B) insert() \n\
   Alt Ctrl <KeyPress>: string(0x01B) insert() \n\
   Alt      <KeyPress>: string(0x01B) insert() \n\

For delete add the following line:

      <KeyPress>Delete:string("\033[3~") \n\

I didn't find a definition for backspace, but:

      <KeyPress>BackSpace:string("\010") \n\

should be the right one.

You have to enter these lines in your .Xresources file, which should
be read using xrdb somewhere in your .xinitrc file: The
XTerm*VT100... starts the keyboard definition, the other line are
continuation lines (note the backslash at the lineend).

I wish xterm had these keyboard definition already provided in the
Debian distribution (is there any specific reason that it isn't).

        Torsten

-- 
Whenever a system becomes completely defined, some damn fool discovers
something which either abolishes the system or expands it beyond recognition.
                                                        Fortune Cookie
PGP Public key available


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to