Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!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: <4762@ogccse.ogc.edu>
Date: 16 Sep 89 06:51:29 GMT
References: <16675@pasteur.Berkeley.EDU> <10569@dasys1.UUCP> <0576.AA0576@julie> <204@titania.warwick.ac.uk>
Reply-To: schaefer@ogccse.UUCP (Barton E. Schaefer)
Organization: Oregon Graduate Center, Beaverton, OR
Lines: 31

In article <204@titania.warwick.ac.uk> cudcv@warwick.ac.uk (Rob McMahon) 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.

Presumably, if the script has output, you would like to see it? .-,    [*]

Unfortunately, the problem is actually worse than you describe.  If any
of the commands in the script rearrange the messages, the curses header
display will be incorrect.  It is advisable to end all scripts that will
be read by the -source option with:

    if iscurses
	headers
    endif

Using these as the last 3 lines will magically correct the display in
most cases.
____________

*  That's a half-smiley, if you look closely.
____________
-- 
Bart Schaefer           "And if you believe that, you'll believe anything."
                                                            -- DangerMouse
CSNET / Internet                schaefer@cse.ogc.edu
UUCP                            ...{sequent,tektronix,verdix}!ogccse!schaefer