Re: [RP] Ideas about some screen commands..

[shawn]

Doug Kearns <address@hidden> writes:
> On Tuesday 18 September 2001 17:25, shawn wrote:
> > >The patches should be applied in reverse order (startup_message
> > > first, then unsetenv, lastmsg and info)
>
> For what it's worth, I still take issue with the way unsetenv is
> implemented.  It currently passes the entire argument list to
> unsetenv() which is inconsistent with the way the other commands
> handle excess arguments.
>
> eg. :unsetenv foo bar
>
> will not unset foo, since it passes 'foo bar' to unsetenv(), which is
> unexpected given the way the other commands work, however
>
> :msgwait 5 99
>
> sets message wait to 5 and ignores 99.
>
> On the other hand, when Gergely has finished his new command parsing
> work, I imagine this point may be moot.

Yes, I'm hoping the argument parsing glob will fix those sort of
shortcomings.

> > I've committed these patches with the exception of the shell
> > scripts and cmd_startup_message. If we implement a full screen
> > banner ala screen, then I'll add this command but as it stands
> > suppressing a petit message in the corner isn't worth the code (I
> > think).
>
> Personally, I _hate_ all welcome messages and feel there really
> _must_ be a way to disable them ;-)

Hmm, well...hmmm. I'm thinking...it would look clean if plain ol' X
and nothin' but shows up. I'll think about it.