Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!sun-barr!newstop!sun!argv
From: argv@turnpike.Eng.Sun.COM (Dan Heller)
Newsgroups: comp.mail.mush
Subject: Re: 2 questions
Message-ID: <143938@sun.Eng.Sun.COM>
Date: 19 Oct 90 06:24:59 GMT
References: <730@parcplace.com>
Sender: news@sun.Eng.Sun.COM
Organization: O'Reilly && Associates
Lines: 30

In article <730@parcplace.com> khaw@parcplace.com (Mike Khaw) writes:
> 1. How can I get mush to treat +/incoming/inbox as my spoolfile
>    for all commands, e.g., "mush -s ~/mail/incoming/inbox -H",
>    ":folder %", w/o compiling it into mush? The -s commandline option
>    doesn't do it.

You can use the -m option to specify that the "spool file" is the
argument to that switch.
% mush -m +incoming/inbox

> 2. Is there a way to pass mush variables to an external executable
>    invoked by a "pipe" command; e.g., if I
> 
> 	:pipe "foo $folder $show_hdrs > /tmp/foo.out"
> 
>    foo gets no command line arguments, as though "pipe" doesn't do
>    $ expansion. I've tried all kinds of variations of quoting (or
>    not quoting, but either I haven't found the right combination or
>    it just doesn't work at all.

This should work.  I don't know why it doesn't.  It appears from
the ':' you're using that you are executing this from curses mode.
Does it act differently for line mode or command mode?  Actually,
I shouldn't have replied to this so soon -- I'm terribly busy with
other things at the moment and I can't fully test it out.
--
dan
----------------------------------------------------
O'Reilly && Associates   argv@sun.com / argv@ora.com
Opinions expressed reflect those of the author only.