Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucsd!telesoft!garym
From: garym@telesoft.telesoft.com (Gary Morris @nova)
Newsgroups: comp.mail.mush
Subject: Re: Help with auto-processing of messages?
Summary: use -noheaders with -source
Keywords: auto-executing script files?
Message-ID: <501@telesoft.telesoft.com>
Date: 18 Sep 89 15:17:33 GMT
References: <16675@pasteur.Berkeley.EDU> <10569@dasys1.UUCP> <0576.AA0576@julie> <4762@ogccse.ogc.edu>
Organization: TeleSoft, San Diego, CA.
Lines: 29

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'.  Mush
> } puts up the list of headers, and then the output from the script destroys
> } the
> } display again, so that you immediately have to redraw it.

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. 

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. 

--GaryM
-- 
Gary Morris			uunet!ucsd!telesoft!garym
TeleSoft, San Diego		telesoft!garym@ucsd.ucsd.edu
(619) 457-2700			garym@crash.cts.com