🚀 go-pugleaf

In article <15151@bfmny0.UU.NET> tneff@bfmny0.UU.NET (Tom Neff) writes:
} One other wish list item would make life with huge (and less than
} huge) folders easier over slow baud rate connections:
} 
} Allow a "+initial_command" switch on the Mush invocation line, and obey
} it the command before initial display.  This would be generally useful,
} like the "+cmd" feature in 'vi' and 'less'.

Just the other day I was trying to figure out how to implement a -e
option, ala sed, perl, etc., which would be pretty much equivalent.
You also ought to be able to use multiple -I or -F options, which you
can't at the moment.

} Specifically what I would tend to do on slow speed dialup lines
} is say
} 
} 	mush -f mylist +last-msg			# or +$
} 
} so that I enter the folder at the BACK rather than having to sit
} fidgeting through the entire initial display and THEN switch to
} the final screenful of messages.

I take it you have "alias mush 'mush -C'" or the like, so that it
wouldn't work to use "mush -N"?

Note also that the "curses" mode can now be turned on and off in
the .mushrc file, so you can

    if $TERM == slow-dialup-terminal-type	# whatever
	curses off
    endif

or, alternately, get rid of the alias for -C and use

    if $TERM == fast-at-the-office-type
	curses
    endif

If the two types are the same I'm sure you can figure out some way to
differentiate; e.g. put "setenv TTY `tty`" in your .login and then

    if $TTY =~ *ttyd*
	curses off
    endif

I'm not rejecting your suggestion, I'm just offering workarounds for
the present situation.
-- 
Bart Schaefer                             "Live and don't learn, that's us."
                                                                   -- Hobbes

schaefer@cse.ogi.edu (used to be cse.ogc.edu)