On 09:59 21 Jan 2002, Carl B. Constantine <[EMAIL PROTECTED]> wrote:
| * Cameron Simpson ([EMAIL PROTECTED]) wrote:
| > | > Anyone have ideas on how to get this to work? (NOTE: my home machine
| > | > uses BASH and I'm using tcsh here at work if that makes any difference).
| > |
| > | That's the problem, the `for file in...` bit is run with whatever your
| > | default shell is, and that's won't work in tcsh, since it's bash (well, sh)
| > | syntax. [...]
| > Or set $SHELL to /bin/sh (or bash, if present) in a wrapper around mutt
| > when invoking it.
|
| well, even running BASH and then running mutt does not seem to solve the
| problem.
You misread me. Do this:
#!/bin/sh
# Mutt wrapper.
SHELL=/bin/sh; export SHELL
exec real-mutt ${1+"$@"}
Just _running_ a bash doesn't set $SHELL (which is the variable used to
express your interactive shell preference). otherwise horrible horrible
things would happen.
Personally, I think mutt _should_ pass `blah...` to /bin/sh. That's what
most things do ,like make et al - this isn't interactive shell stuff, it's
programming, and the stanard UNIX shell programming language is /bin/sh.
--
Cameron Simpson, DoD#743 [EMAIL PROTECTED] http://www.zip.com.au/~cs/
When connecting, faxes send out a series of tones which, in the world of fax
machines, apparently say something like 'Wake up, roll over and make love to
me.' - Tequila Rapide
