Index | Thread | Search

From:
"Theo de Raadt" <deraadt@openbsd.org>
Subject:
Re: wscons 256 colour support
To:
Mark Kettenis <mark.kettenis@xs4all.nl>, tech@openbsd.org
Date:
Sat, 28 Jun 2025 08:33:37 -0600

Download raw body.

Thread
Crystal Kolipe <kolipe.c@exoticsilicon.com> wrote:

> On Sat, Jun 28, 2025 at 08:13:40AM -0600, Theo de Raadt wrote:
> > - Basic compatibility with xterm
> > 
> > - So that we can change the default tty type to xterm, and stop
> >   saying "vt220" in /etc/ttys, and say "xterm" instead.
> 
> What is still missing for this to happen?

I don't know.

> The main thing I am aware of is the F-keys patch that I posted separately.

I doubt that is in the critical path.  I suspect the problems will be that
programs assume they can send xter sequences which are mis-executed.

> > - Throwing away non-xterm operations.  If we don't remove junk,
> >   the kernel bloat will be unacceptable.  None of this can happen
> >   unless the codesizes stay the same, but it if even better if it
> >   shrinks.
> 
> So this means removing support for vt220 control sequences that are not
> required by TERM=xterm?

How else do we avoid the codebase becoming a bloaty kitchen-sink which
noone needs?  My argument would be that if it says it is vt220, it should
ONLY support vt220 operations.  If it says it is xterm, only xterm operations.

My opinion is that the kernel should not waste any effort on bizzare
hybrid behaviours, and code supporting hybrid behaviour should be deleted.