Re: [arch-general] Xterm and .Xresources

2019-08-11 Thread Ralph Corderoy
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

Re: [arch-general] Xterm and .Xresources

2019-08-10 Thread Storm Dragon via arch-general
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

Re: [arch-general] Xterm and .Xresources

2019-08-08 Thread Ralph Corderoy
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

[arch-general] Xterm and .Xresources

2019-08-07 Thread Storm Dragon via arch-general
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