-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
>> shou
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 oth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Micah Cowan wrote:
> My question is: is screen even right to issue the initialization string,
> at all? And particularly _after_ issuing smkx.
(Sorry, here and elsewhere, I mean smcup (termcap "ti"), not smkx.)
- --
Micah J. Cowan
Programmer, musicia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So, the other day, I suddenly found that screen was no longer using the
alternate screen buffer as it usually does. Worse, screen _thought_ it
was operating under the alternate screen buffer, so left a dirty screen
upon exit. Thinking it was a recently
