-----BEGIN PGP SIGNED MESSAGE----- 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 http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIoITD7M8hyUobTrERApgJAJ4iBWCjzEYpoHIjiW+3s0lRiwxFJACfYNoi KEnfdvCBZZL/QEgMpIu8CVc= =j7wl -----END PGP SIGNATURE----- _______________________________________________ screen-users mailing list screen-users@gnu.org http://lists.gnu.org/mailman/listinfo/screen-users
