hey all,

well, this morning i found the answer to one of my woes.   for some reason,
my arrow keys never worked in xterms and gnome-terminals.   they DID work
in rxvt's.

so i'm playing around with eterm, and find that the arrow keys do NOT work
under eterm.  inspired by xterm,  i try a ctl-rightclick and a menu pops up.
cool.   i try clicking:

   terminal | keys | application arrow keys

not because i have any idea what it does, but simply because "hey, i'm having
trouble with the arrow keys".   sure enough, my arrow keys now work with
eterm.

i try the same deelio with xterm, and find that on middle clicking xterms,
there's an option "enable application cursor keys".   toggling it, i find
that my arrow keys now work with xterm.  whoa.


question 1 -- WTF is "application arrow keys".  i've only had this problem
since switching to the MS ergonomic keyboard (a very good keyboard, i might
add).  when i had a generic keyboard, i never had this problem.


so now, the thing to do is write something into .Xdefaults.   looking through
man xterm,


      The following resources are specified as part of the vt100
       widget (class VT100):

      appcursorDefault (class AppcursorDefault)
               If ``true,'' the  cursor  keys  are  initially  in
               application mode.  The default is ``false.''


question 2 -- so what exactly do i put in my .Xdefaults, something like

   xterm.VT100*appcursorDefault: True

i've always been confused by this file.  take for instance:

xterm*reverseWrap:   true
*visualBell:      true
*scrollTtyOutput: False
*scrollKey:    True
Scrollbar.JumpCursor:   True

what exactly is the syntax here?  i assume lines beginning with a * modify
the same application as the one previous, so the above is equivalent to

xterm*reverseWrap:   true
xterm*visualBell:      true
xterm*scrollTtyOutput: False
xterm*scrollKey:    True
Scrollbar.JumpCursor:   True

but how do you explain the last line which doesn't seem to belong to any
application?   or does it apply to ALL scrollbars?


by looking at lines like:

XTerm.VT100*dynamicColors:  on

it looks like the actual variable is separated from the application and
subclass with an asterisk, but then there are lines which don't have an
asterisk like:

XTerm.VT100.titeInhibit:  true


i'm in need of either an explanation or a good man/info page.   can someone
give me either one?

pete

Reply via email to