Re: xterm question [SOLVED]
On Wed, Feb 16, 2011 at 01:19:49PM -0500, Chris Jones wrote:
> On Wed, Feb 16, 2011 at 12:39:39PM EST, Mike McClain wrote:
>
> > I work mainly on the commandline and have setup my own inputrc and
> > a script that calls loadkeys for readline editing functions in bash such
> > as ^Home --> bash:backward-kill-line but never used bind by itself.
> >
> > Speaking of which, these mappings don't seem to carry over into xterm.
> > Can you point the way to setup similar bash functionality in xterm?
>
> I would suspect this may have to do with navigation keys support in
> XTerm .. arrows, Home.. End.. Pgup.. etc. I don't know the details
> because I do my best NOT to use any keys that live beyond my stubby
> fingers' reach but if you google for something like ???xterm arrow keys???
> or ???xterm home end key??? etc. you should quickly be able to tell whether
> this is relevant or yet just another bad guess on my part. If I guessed
> right, it's likely going to boil down to your terminal description (cf.
> the contents of the $TERM environment variable) - not describing such
> capabilities for the benefit of client applications. Mileage solving
> problems in this area varies.
After a day spent reading several articles on X and xterm I finally came
to the realization that the use of bind you pointed out earlier in this
thread would do what I wanted. Using ^v to see what the key combinations
were sending it wasn't much trouble to put together a file to feed to
bind to set the bindings I wanted.
mike@/deb40a:~> cat xterm_bindings
# xterm bindings 2/17/11 Mc
# use: bind -f xterm_bindings
# ^Home
"\M-[1;5H": backward-kill-line
# ^End
"\M-[1;5F": kill-line
# ^Del
"\M-[3;5~": kill-whole-line
# ^BS
"\C-H": backward-kill-word
# ^Left
"\M-[1;5D": backward-word
# ^Right
"\M-[1;5C": forward-word
I use these readline editing bindings on the CL all the time
and really missed them in xterm.
Thanks for your help,
Mike
--
Satisfied user of Linux since 1997.
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
Reply to: