[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Screen, xterm, initialization strings.

From: Micah Cowan
Subject: Re: Screen, xterm, initialization strings.
Date: Mon, 11 Aug 2008 11:28:19 -0700
User-agent: Thunderbird (X11/20080724)

Hash: SHA1

Stephane Chazelas wrote:
> On Sun, Aug 10, 2008 at 07:42:22PM -0700, Micah Cowan wrote:
> [...]
>> I propose that screen not send the initialization string. Probably with
>> a command-line option that specifies it should be sent (though, IMO it
>> should be sent before smkx, and not after). Any thoughts on this?
> [...]
> On the other hand, it seems to me that sending the init sequence
> would be the best way to ensure the terminal is in the state we
> expect it to be in.

Probably; except that we _don't_ expect it to be switched to 80-col
mode, which is apparently one of the things is2 is expected to do.

If is2 is expected to be sent at a user's login, then perhaps we should
simply expect that it's already been taken care of, as a large variety
(most? all?) of other terminal apps appear to do (with the obvious
exception of "tput init" :) ).

> But I agree doing the smcup and switching to alternate screen
> *before* doing the "init" sounds wrong.

Okay, so I'm not crazy there, then. :)

- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer.
GNU Maintainer: wget, screen, teseq
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla -


reply via email to

[Prev in Thread] Current Thread [Next in Thread]