Ken W <[EMAIL PROTECTED]> wrote:
>
> If for example I save an attachment into my home directory and then
> try to chmod it after hitting '!', using a relative pathname like
> dir/filename it works fine. If I use ~/dir/filename I get the
> following:
>
> chmod: WARNING: can't access ~/dir/filename
The chmod command was handed the literal string '~/dir/filename', and it
didn't find a directory by that name. Mutt spawns commands using
/bin/sh, and the Bourne shell is not smart enough to expand the '~' into
your full $HOME pathname.
You could use '$HOME' instead of '~', that would work. But it's not
really Mutt's job to expand pathnames in random commands that you give.
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there is no man really clever who has not
Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson
Convex Division | PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
