Howdy,
I am trying to get Xterm to work in practically the same way as the console, just with a bit better font support. I have searched the net and created an extensive .Xresources file, which is attached to this message. It is supposed to fix all the function keys, the six pack, and even the numpad keys. the problem is, the keyboard fix part, doesn't work.
I found that if I export TERM=vt220 that most keys do work, but home and end in applications like nano and ne do not work still and cause weird behavior. I was wondering if exporting TERM should even be necessary, because in the console, I never have to do that, and it shows as "linux".
Can someone please take a look and help fix up this .Xresources, and also, do I really need to export TERM, or can I ditch that setting?
Thanks for the help, Storm
Hi Storm,
I found that if I export TERM=vt220 that most keys do work
If you start an xterm(1) and find TERM is `xterm' then I'd leave it alone.
but home and end in applications like nano and ne do not work still and cause weird behavior.
In the xterm, run `od -c' and type `Home Enter Ctrl-D' and then adjust the appropriate resources to match as they're probably wrong:
<Key>Home: string(0x1b) string("[3~") \n \
...
<Key>Home: string(0x1b) string("[1~") \n\
It may be better to slowly build up your X resources a bit at a time, understanding each, rather than adopt a mass at once and then try and discover the problems and debug them.
Howdy Ralph,
Thanks for the help. My TERM reports as Linux. Should I export it as xterm?
Thanks, Storm
On Thu, Aug 08, 2019 at 01:57:28PM +0100, Ralph Corderoy wrote:
Hi Storm,
I found that if I export TERM=vt220 that most keys do work
If you start an xterm(1) and find TERM is `xterm' then I'd leave it alone.
but home and end in applications like nano and ne do not work still and cause weird behavior.
In the xterm, run `od -c' and type `Home Enter Ctrl-D' and then adjust the appropriate resources to match as they're probably wrong:
<Key>Home: string(0x1b) string("[3~") \n \...
<Key>Home: string(0x1b) string("[1~") \n\It may be better to slowly build up your X resources a bit at a time, understanding each, rather than adopt a mass at once and then try and discover the problems and debug them.
-- Cheers, Ralph.
--
Hi Storm,
I found that if I export TERM=vt220 that most keys do work
If you start an xterm(1) and find TERM is `xterm' then I'd leave it alone.
My TERM reports as Linux. Should I export it as xterm?
xterm(1) says
Terminal database (terminfo (5) or termcap (5)) entries that work with xterm include
an optional platform-specific entry (“xterm”), “xterm”, “vt102”, “vt100”, “ansi” and “dumb”
Xterm automatically searches the terminal database in this order for these entries and then sets the “TERM” variable (and the “TERMCAP” environment variable on a few older systems). The alternatives after “xterm” are very old, from the late 1980s.
So presumably something in your set up, e.g. .bash_profile, is setting it to ‘Linux’. Yes, set it to ‘xterm’.
I'd also expect you to have /usr/share/terminfo/x/xterm-256color that means it can alternatively be set to ‘xterm-256color’.
arch-general@lists.archlinux.org