Article View: comp.mail.mush
Article #5482 questions
From: Mike Khaw
Date: Fri, 19 Oct 1990 00:11
Date: Fri, 19 Oct 1990 00:11
18 lines
1072 bytes
1072 bytes
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.
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.
--
Mike Khaw
ParcPlace Systems, Inc., 1550 Plymouth St., Mountain View, CA 94043
Domain=khaw@parcplace.com, UUCP=...!{uunet,sun,decwrl}!parcplace!khaw
Technical Details
Message-ID:
<730@parcplace.com>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!parcplace!khawShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!parcplace!khaw From: khaw@parcplace.com (Mike Khaw) Newsgroups: comp.mail.mush Subject: 2 questions Message-ID: <730@parcplace.com> Date: 19 Oct 90 00:11:18 GMT Organization: ParcPlace Systems, Mt. View, CA Lines: 18