Re: [dev] [st][PATCH] Add support for utmp in st

From: <random832_AT_fastmail.us>
Date: Sun, 12 Oct 2014 00:38:22 -0400

On Sat, Oct 11, 2014, at 04:07, k0ga_AT_shike2.com wrote:
> Value of erase key for example, or in general the configuration
> of line kernel driver

These can't come from the profile either; since st opens a new tty that
is not the same device the user logged in on.

 (stty(1)). Backspace key in st generates
> BACKSPACE, but almost all terminals generate DELETE instead
> (read FAQ for more details).

It's not clear why the position of the key and the intent of the user
typing it is less important than the label of the key.

What's st's position on prior/next/find/select vs pgup/pgdn/home/end?
And speaking of the editing keypad keys, the code that most terminals
send for the del key is that for the VT220 "remove here" key. The delete
key above enter on the VT220 is labeled <x], so it clearly has a meaning
of delete left despite sending ^?, and thus establishes an association
between ^? and delete left long before linux. The fact that the PC
keyboard key in this position is labeled Backspace is the historical
accident.

> I also have some adittionals
> configurations like for example 'tput smkx' (set keypad on),
> or `tabs`.About the three variables you tell, TERM is the only
> that a terminal must set, LINES and COLUMNS are shell stuff
> and are not even standard.

Their meaning is defined in the standard. The method of obtaining
default values is not, but that means it's the implementation's
responsibility, not that it doesn't mean anything at all.

But unsetting it, along with the initial call to cresize, should be fine
on most systems, so maybe I've been too harsh about this.
Received on Sun Oct 12 2014 - 06:38:22 CEST