Path: utzoo!mnetor!tmsoft!torsqnt!jarvis.csri.toronto.edu!rutgers!ucsd!ogccse!schaefer
From: schaefer@ogccse.ogc.edu (Barton E. Schaefer)
Newsgroups: comp.mail.mush
Subject: Re: Help with auto-processing of messages?
Keywords: auto-executing script files?
Message-ID: <4790@ogccse.ogc.edu>
Date: 19 Sep 89 17:25:03 GMT
References: <16675@pasteur.Berkeley.EDU> <10569@dasys1.UUCP> <0576.AA0576@julie> <4762@ogccse.ogc.edu> <501@telesoft.telesoft.com>
Reply-To: schaefer@ogccse.UUCP (Barton E. Schaefer)
Organization: Oregon Graduate Center, Beaverton, OR
Lines: 41

In article <501@telesoft.telesoft.com> garym@telesoft.com (Gary) writes:
} In article <4762@ogccse.ogc.edu>, schaefer@ogccse.ogc.edu (Barton) writes:
} > In article <204@titania.warwick.ac.uk> cudcv@warwick.ac.uk (Rob) writes:
} > } >Dan Heller writes:
} > } >>% mush -source script_file
} > } 
} > } Unfortunately this doesn't work too cleanly in conjunction with `-C'.
} 
} Another way of handling this problem is to use -N (-noheaders) (which only
} seems to work in line mode), then start up in line mode instead of curses
} (without the -C), and finally switch to curses mode at the end of the script
} being sourced.  This starts up without the header display, does your stuff
} and then goes into curses mode and displays the header.  It seemed to work
} OK on my version (6.5.6) even when the script rearranged the order of the
} messages.

Correct.  The problem with -curses -source is that the curses screen gets
generated when the folder is first loaded, and unless something in the
script redraws it, it won't change.  If you wait until after the script
has finished to go into curses mode, then the screen gets built at that
time with the correct headers.

} BTW, the "curses" command itself isn't mentioned in the man page except in
} one place, the section on initialization says not to use the "curses"
} command from an initialization file.  It's not in the list of line mode 
} commands, though it does work.  I take it that means it can't go in
} .mushrc but it's ok in a file that used with -source. 

That is precisely what it means, although its omission from the list of
line mode commands in the man page is an oversight (it shows up in the
list from the ? command).

Furthermore, I have just removed from 7.0 alpha the restriction on
giving the "curses" command from a .mushrc file.  Effectively, the
"curses" command in a .mushrc file now turns on the -C switch.  Look
for that in the next release.
-- 
Bart Schaefer           "And if you believe that, you'll believe anything."
                                                            -- DangerMouse
CSNET / Internet                schaefer@cse.ogc.edu
UUCP                            ...{sequent,tektronix,verdix}!ogccse!schaefer