Hi,
On Sat, Apr 15, 2000 at 06:44:05PM +0300, Mikko H�nninen wrote:
> Hmm, that's true for "man mutt". If you do "mutt -h", it does list
>
> <addr> [ ... ]
>
> ... at the end of the second format, which seems to be correct.
> But I just noticed another problem with the "mutt -h" synopsis: the
> -y command line option is not included anywhere.
You're using mutt 1.1.9i. With mutt 1.1.11i it _is_ listed:
$ > mutt -h
Mutt 1.1.11i (2000-03-30)
usage: mutt [ -nRzZ ] [ -e <cmd> ] [ -F <file> ] [ -m <type> ] [ -f
<file> ]
mutt [ -nx ] [ -e <cmd> ] [ -a <file> ] [ -F <file> ] [ -H
<file> ] [ -i
<file> ] [ -s <subj> ] [ -b <addr> ] [ -c <addr> ] <addr> [ ... ]
mutt [ -n ] [ -e <cmd> ] [ -F <file> ] -p
mutt -v[v]
options:
-a <file> attach a file to the message
-b <address> specify a blind carbon-copy (BCC) address
-c <address> specify a carbon-copy (CC) address
-e <command> specify a command to be executed after initialization
-f <file> specify which mailbox to read
-F <file> specify an alternate muttrc file
-H <file> specify a draft file to read header from
-i <file> specify a file which Mutt should include in the reply
-m <type> specify a default mailbox type
-n causes Mutt not to read the system Muttrc
-p recall a postponed message
-R open mailbox in read-only mode
-s <subj> specify a subject (must be in quotes if it has spaces)
-v show version and compile-time definitions
-x simulate the mailx send mode
-y select a mailbox specified in your
-z exit immediately if there are no messages in the
mailbox
-Z open the first folder with new message, exit
immediately if none
-h this help message
$ >
Michael
--
Real Programs don't use shared text. Otherwise, how can they use
functions for scratch space after they are finished calling them?
