Re: 1.5.17 batch mode does not append .signature
On 11/27/2007 13:38, Aron Griffis wrote:
> Roger Cornelius wrote: [Tue Nov 27 2007, 11:50:07AM EST]
> > Whether by error or design, mutt 1.5.17 and earlier does not append
> > the .signature file when sending in batch mode.
>
> Pretty sure it's by design. Batch mode assumes the complete email on
> stdin and that it shouldn't be modified.
The brief blurb pertaining to batch mode in the manual doesn't mention
this. Viz:
Mutt also supports a ``batch'' mode to send prepared messages. Simply
redirect input from the file you wish to send. For example,
mutt -s "data set for run #2" professor@xxxxxxxxxxxxx < ~/run2.dat
This command will send a message to ``professor@xxxxxxxxxxxxx'' with a
subject of ``data set for run #2''. In the body of the message will be
the contents of the file ``~/run2.dat''.
Maybe a line from your email could be added as a caveat:
Mutt also supports a ``batch'' mode to send prepared messages. Batch
mode assumes the complete email on stdin and that it shouldn't be
modified. Simply redirect input from the file you wish to send.
For example,
...
The manual's description of the $signature variable also makes no
mention of the behaviour and even implies otherwise (note "all"):
3.261. signature
Type: path
Default: "~/.signature"
Specifies the filename of your signature, which is appended to all
outgoing messages. If the filename ends with a pipe (``|''), it is
assumed that filename is a shell command and input should be read from
its stdout.
The descriptive text could be changed to, e.g.:
Specifies the filename of your signature, which is appended to all
outgoing messages, except when sending in batch mode. If the filename
ends with a pipe (``|''), it is assumed that filename is a shell
command and input should be read from its stdout.
--
Roger Cornelius rac@xxxxxxxxxxx