Path: utzoo!attcan!uunet!parcplace!khaw
From: khaw@parcplace.com (Mike Khaw)
Newsgroups: comp.mail.mush
Subject: Re: 2 questions
Message-ID: <732@parcplace.com>
Date: 21 Oct 90 05:50:11 GMT
References: <730@parcplace.com> <143938@sun.Eng.Sun.COM>
Organization: ParcPlace Systems, Mt. View, CA
Lines: 35

argv@turnpike.Eng.Sun.COM (Dan Heller) writes:

-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

Sorry, my fingers slipped. I meant to use the -m switch and kept
typing -s for some odd reason. Thanks, -m works just fine.

-> 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,

Nope, same results when I go into line mode first and then try to
execute the pipe command.
-- 
Mike Khaw
ParcPlace Systems, Inc., 1550 Plymouth St., Mountain View, CA 94043
Domain=khaw@parcplace.com, UUCP=...!{uunet,sun,decwrl}!parcplace!khaw