🚀 go-pugleaf

I wrote:
mcr> not a command (which could be called from the init file) that
mcr> would cause the mailbox to be read in?

Dan Heller wrote:
dan>Part of the initialization of mush is to "read in init file(s), load folder
dan>specified, process commands from user-interface".  Loading a folder from
dan>your .mushrc isn't wise because not everything has been initialized such
dan>as tmpdir, and other variables that are important to the startup process.

  I guess I didn't phrase my question properly. I'm asking why a command
like `mush_init' couldn't cause all the above to happen, and then continue
execution of the script. (Or even, "init_to script-file", if maintaining
an open script is too difficult. The script-file(s) specified in
the different init files [e.g. /usr/lib/mushrc, .mushrc] might even
all take effect once the folder has loaded, etc...)

  The init_to command might not even cause the init file to terminate
or even for the script to run immediately, but rather to continue
on and run when all the initialisation is complete.

>The reason $first_time is used is to demonstrate that the .mushrc can be
>reused -- possibly recursively.  Many people forget that mush is more of
>a "shell" than it is a Mail-clone.  The use of command line aliases,
>history, and variable usage greatly enhances the usability of the product.

  I'm just not sure that the $first_time example is a particularly
great example of the programming/shell features of mush...
(An aside --- my boss was looking for a way to print out a folder,
one per page to a laser. I handed him mush. [He still uses /bin/mail.
All my mail from him says `Apparently-To:' :-)])  But, I think
there are enough examples of good usage in there to get people
going...



--

  :!mcr!:
  Michael Richardson                     Amiga
                                  v--------+
 UUCP: uunet!attcan!lsuc!nrcaer!julie!mcr  | INTERNET mcr@doe.carleton.ca
 Fido: Michael Richardson @ 1:163/109.10<--+ WORK: michael@fts1.UUCP