<<< Date Index >>>     <<< Thread Index >>>

Fwd: manual correction/improvements



Hi,

Mutt BTS is not working?
I reported two patch, but didn't receive them through mutt-dev.
So I forward them.

Additionally, IRC #mutt channel is now on irc.freenode.net.
This should be fixed, too.

-- 
tamo
--- Begin Message ---
Package: mutt
Version: 1.5.6i
Severity: normal

-- Please type your report below this line

0. "%o" can be used with "%?"
1. typo: s/status_char/sequence_char/
2. typo: s/when when/when/

Index: init.h
===================================================================
RCS file: /home/roessler/cvs/mutt/init.h,v
retrieving revision 3.48
diff -u -r3.48 init.h
--- init.h      17 Jun 2004 20:36:13 -0000      3.48
+++ init.h      4 Jul 2004 03:26:23 -0000
@@ -2460,7 +2460,7 @@
   ** .dt %m  .dd the number of messages in the mailbox *
   ** .dt %M  .dd the number of messages shown (i.e., which match the current 
limit) *
   ** .dt %n  .dd number of new messages in the mailbox *
-  ** .dt %o  .dd number of old unread messages
+  ** .dt %o  .dd number of old unread messages *
   ** .dt %p  .dd number of postponed messages *
   ** .dt %P  .dd percentage of the way through the index
   ** .dt %r  .dd modified/read-only/won't-write/attach-message indicator,
@@ -2487,7 +2487,7 @@
   ** .pp
   ** where \fIsequence_char\fP is a character from the table above, and
   ** \fIoptional_string\fP is the string you would like printed if
-  ** \fIstatus_char\fP is nonzero.  \fIoptional_string\fP \fBmay\fP contain
+  ** \fIsequence_char\fP is nonzero.  \fIoptional_string\fP \fBmay\fP contain
   ** other sequence as well as normal text, but you may \fBnot\fP nest
   ** optional strings.
   ** .pp
@@ -2671,7 +2671,7 @@
   { "weed",            DT_BOOL, R_NONE, OPTWEED, 1 },
   /*
   ** .pp
-  ** When set, mutt will weed headers when when displaying, forwarding,
+  ** When set, mutt will weed headers when displaying, forwarding,
   ** printing, or replying to messages.
   */
   { "wrap_search",     DT_BOOL, R_NONE, OPTWRAPSEARCH, 1 },



-- System Information
System Version: FreeBSD

-- Build environment information

(Note: This is the build environment installed on the system
muttbug is run on.  Information may or may not match the environment
used to build mutt.)

- gcc version information
cc -I/usr/local/include/db42 -I/usr/local/include -I/usr/local/include/slang
Reading specs from /usr/local/lib/gcc-lib/i386-portbld-freebsd5.1/3.3.4/specs
Configured with: ./..//gcc-3.3-20040616/configure --disable-nls 
--with-system-zlib --program-suffix=33 
--with-gxx-include-dir=/usr/local/lib/gcc-lib/i386-portbld-freebsd5.1/3.3.4/include/c++/
 --disable-shared --prefix=/usr/local i386-portbld-freebsd5.1
Thread model: posix
gcc version 3.3.4 [FreeBSD]

- CFLAGS
-Wall -pedantic -Os -march=pentium2

-- Mutt Version Information

Mutt 1.5.6i (2004-02-01)
-DOMAIN
-DEBUG
+HOMESPOOL  -USE_SETGID  +USE_DOTLOCK  -DL_STANDALONE  
-USE_FCNTL  +USE_FLOCK
+USE_POP  +USE_IMAP  -USE_GSS  +USE_SSL  -USE_SASL  -USE_SASL2  
+HAVE_REGCOMP  -USE_GNU_REGEX  
+HAVE_COLOR  -HAVE_START_COLOR  -HAVE_TYPEAHEAD  -HAVE_BKGDSET  
-HAVE_CURS_SET  -HAVE_META  -HAVE_RESIZETERM  
+CRYPT_BACKEND_CLASSIC_PGP  +CRYPT_BACKEND_CLASSIC_SMIME  -CRYPT_BACKEND_GPGME  
-BUFFY_SIZE -EXACT_ADDRESS  -SUN_ATTACHMENT  
+ENABLE_NLS  +LOCALES_HACK  -HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET  
+HAVE_LANGINFO_YESEXPR  
+HAVE_ICONV  -ICONV_NONTRANS  +HAVE_LIBIDN  +HAVE_GETSID  +HAVE_GETADDRINFO  
+USE_HCACHE  
-ISPELL
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="Maildir"
PKGDATADIR="/usr/local/share/mutt"
SYSCONFDIR="/usr/local/etc"
EXECSHELL="/bin/sh"
-MIXMASTER

patch-1.5.6.tt.ja.1

--- End Message ---
--- Begin Message ---
Package: mutt
Version: 1.5.6i
Severity: wishlist

-- Please type your report below this line

0. more precise descriptions for quadoptions
1. s/ elect/ select/
2. "use write_bcc" should mean "unset write_bcc"
3. "lists" and "subscribe" take regexps instead of addresses
4. s/_/&lowbar;/ in "name" attribution
5. more tight regexp

Index: init.h
===================================================================
RCS file: /home/roessler/cvs/mutt/init.h,v
retrieving revision 3.48
diff -U4 -r3.48 init.h
--- init.h      17 Jun 2004 20:36:13 -0000      3.48
+++ init.h      6 Jul 2004 08:33:51 -0000
@@ -1149,11 +1149,12 @@
 
   { "move",            DT_QUAD, R_NONE, OPT_MOVE, M_ASKNO },
   /*
   ** .pp
-  ** Controls whether you will be asked to confirm moving read messages
+  ** Controls whether or not Mutt moves read messages
   ** from your spool mailbox to your ``$$mbox'' mailbox, or as a result of
-  ** a ``$mbox-hook'' command.
+  ** a ``$mbox-hook'' command. You will be asked to confirm before moving
+  ** them if this option is either \fIask-yes\fP or \fIask-no\P.
   */
   { "message_format",  DT_STR,  R_NONE, UL &MsgFmt, UL "%s" },
   /*
   ** .pp
@@ -1937,9 +1938,9 @@
   { "postpone",                DT_QUAD, R_NONE, OPT_POSTPONE, M_ASKYES },
   /*
   ** .pp
   ** Controls whether or not messages are saved in the ``$$postponed''
-  ** mailbox when you elect not to send immediately.
+  ** mailbox when you select not to send immediately.
   */
   { "postponed",       DT_PATH, R_NONE, UL &Postponed, UL "~/postponed" },
   /*
   ** .pp
@@ -1969,9 +1970,9 @@
 #endif /* USE_SOCKET */
   { "print",           DT_QUAD, R_NONE, OPT_PRINT, M_ASKNO },
   /*
   ** .pp
-  ** Controls whether or not Mutt asks for confirmation before printing.
+  ** When set to \fIask\fP, Mutt asks for confirmation before printing.
   ** This is useful for people (like me) who accidentally hit ``p'' often.
   */
   { "print_command",   DT_PATH, R_NONE, UL &PrintCmd, UL "lpr" },
   /*
@@ -2071,9 +2072,9 @@
   */
   { "recall",          DT_QUAD, R_NONE, OPT_RECALL, M_ASKYES },
   /*
   ** .pp
-  ** Controls whether or not you are prompted to recall postponed messages
+  ** Controls whether or not Mutt recalls postponed messages
   ** when composing a new message.  Also see ``$$postponed''.
   ** .pp
   ** Setting this variable to ``yes'' is not generally useful, and thus not
   ** recommended.
@@ -2105,9 +2106,9 @@
   */
   { "reply_to",                DT_QUAD, R_NONE, OPT_REPLYTO, M_ASKYES },
   /*
   ** .pp
-  ** If set, Mutt will ask you if you want to use the address listed in the
+  ** If set to \fIask\fP, Mutt will ask you if you want to use the address 
listed in the
   ** Reply-To: header field when replying to a message.  If you answer no,
   ** it will use the address in the From: header field instead.  This
   ** option is useful for reading a mailing list that sets the Reply-To:
   ** header field to the list address and you want to send a private
@@ -2700,9 +2701,9 @@
   { "write_bcc",       DT_BOOL, R_NONE, OPTWRITEBCC, 1},
   /*
   ** .pp
   ** Controls whether mutt writes out the Bcc header when preparing
-  ** messages to be sent.  Exim users may wish to use this.
+  ** messages to be sent.  Exim users may wish to unset this.
   */
   /*--*/
   { NULL }
 };
Index: doc/manual.sgml.head
===================================================================
RCS file: /home/roessler/cvs/mutt/doc/manual.sgml.head,v
retrieving revision 3.29
diff -U4 -r3.29 manual.sgml.head
--- doc/manual.sgml.head        12 Apr 2004 20:02:49 -0000      3.29
+++ doc/manual.sgml.head        6 Jul 2004 08:34:16 -0000
@@ -410,9 +410,9 @@
 
 <p><bf/list-reply/<label id="list-reply"> (default: L)<newline>
 
 Reply to the current or tagged message(s) by extracting any addresses which
-match the addresses given by the <ref id="lists" name="lists or subscribe">
+match the regular expressions given by the <ref id="lists" name="lists or 
subscribe">
 commands, but also honor any <tt/Mail-Followup-To/ header(s) if the
 <ref id="honor_followup_to" name="&dollar;honor&lowbar;followup&lowbar;to">
 configuration variable is set.  Using this when replying to messages posted
 to mailing lists helps avoid duplicate copies being sent to the author of
@@ -1181,9 +1181,9 @@
 someone else.  For instance, when replying to a message that you
 sent to a different party, mutt will automatically suggest to send
 the response to the original message's recipients -- responding to
 yourself won't make much sense in many cases.  (See <ref
-id="reply_to" name="&dollar;reply_to">.)
+id="reply_to" name="&dollar;reply&lowbar;to">.)
 
 Many users receive e-mail under a number of different addresses. To
 fully use mutt's features here, the program must be able to
 recognize what e-mail addresses you receive mail under. That's the
@@ -1210,9 +1210,9 @@
 the Mail-Followup-To header is a non-standard extension which is not
 supported by all mail user agents.  Adding it is not bullet-proof against
 receiving personal CCs of list messages.  Also note that the generation
 of the Mail-Followup-To header is controlled by the <ref id="followup_to"
-name="&dollar;followup_to"> configuration variable.
+name="&dollar;followup&lowbar;to"> configuration variable.
 
 More precisely, Mutt maintains lists of patterns for the addresses
 of known and subscribed mailing lists.  Every subscribed mailing
 list is known. To mark a mailing list as known, use the ``lists''
@@ -1220,9 +1220,9 @@
 
 You can use regular expressions with both commands.  To mark all
 messages sent to a specific bug report's address on mutt's bug
 tracking system as list mail, for instance, you could say
-``subscribe [0-9]*@bugs.guug.de''.  Often, it's sufficient to just
+``subscribe [0-9]*@bugs&bsol;&bsol;.guug&bsol;&bsol;.de''.  Often, it's 
sufficient to just
 give a portion of the list's e-mail address.
 
 Specify as much of the address as you need to to remove ambiguity.  For
 example, if you've subscribed to the Mutt mailing list, you will receive mail
@@ -1230,10 +1230,10 @@
 mailing list, you could add ``lists mutt-users'' to your
 initialization file.  To tell mutt that you are subscribed to it,
 add ``subscribe mutt-users'' to your initialization file instead.
 If you also happen to get mail from someone whose address is
-<em/mutt-users@xxxxxxxxxxx/, you could use ``lists mutt-users@xxxxxxxx'' 
-or ``subscribe mutt-users@xxxxxxxx'' to
+<em/mutt-users@xxxxxxxxxxx/, you could use ``lists 
mutt-users@mutt&bsol;&bsol;.org'' 
+or ``subscribe mutt-users@mutt&bsol;&bsol;.org'' to
 match only mail from the actual list.
 
 The ``unlists'' command is used to remove a token from the list of
 known and subscribed mailing-lists. Use ``unlists *'' to remove all
@@ -1374,9 +1374,9 @@
 to <ref id="record" name="&dollar;record"> mailbox.
 
 See <ref id="pattern_hook" name="Message Matching in Hooks"> for information 
on the exact format of <em/pattern/.
 
-Example: <tt/fcc-hook aol.com&dollar; +spammers/
+Example: <tt/fcc-hook [@.]aol&bsol;&bsol;.com&dollar; +spammers/
 
 The above will save a copy of all messages going to the aol.com domain to
 the `+spammers' mailbox by default.  Also see the <ref id="fcc-save-hook" 
 name="fcc-save-hook"> command.
@@ -1987,9 +1987,9 @@
 my_hdr directive:
 
 <tscreen><verb>
 send-hook . 'unmy_hdr From:'
-send-hook ~Cb@xxx my_hdr from: c@xxx
+send-hook ~C'^b@b\.b$' my_hdr from: c@xxx
 </verb></tscreen>
 
 <sect2>Message Matching in Hooks<label id="pattern_hook">
 <p>
@@ -2181,12 +2181,12 @@
 than the author of the message.  This can create problems when trying
 to reply directly to the author in private, since most mail clients
 will automatically reply to the address given in the ``Reply-To''
 field.  Mutt uses the <ref id="reply_to" name="&dollar;reply&lowbar;to">
-variable to help decide which address to use.  If set, you will be
+variable to help decide which address to use.  If set to <em/ask/, you will be
 prompted as to whether or not you would like to use the address given in
 the ``Reply-To'' field, or reply directly to the address given in the
-``From'' field.  When unset, the ``Reply-To'' field will be used when
+``From'' field.  When set to <em/yes/, the ``Reply-To'' field will be used when
 present.
 
 The ``X-Label:'' header field can be used to further identify mailing
 lists or list subject matter (or just to annotate messages



-- System Information
System Version: FreeBSD

-- Build environment information

(Note: This is the build environment installed on the system
muttbug is run on.  Information may or may not match the environment
used to build mutt.)

- gcc version information
cc -I/usr/local/include/db42 -I/usr/local/include -I/usr/local/include/slang
Reading specs from /usr/local/lib/gcc-lib/i386-portbld-freebsd5.1/3.3.4/specs
Configured with: ./..//gcc-3.3-20040616/configure --disable-nls 
--with-system-zlib --program-suffix=33 
--with-gxx-include-dir=/usr/local/lib/gcc-lib/i386-portbld-freebsd5.1/3.3.4/include/c++/
 --disable-shared --prefix=/usr/local i386-portbld-freebsd5.1
Thread model: posix
gcc version 3.3.4 [FreeBSD]

- CFLAGS
-Wall -pedantic -Os -march=pentium2

-- Mutt Version Information

Mutt 1.5.6i (2004-02-01)
Copyright (C) 1996-2002 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: FreeBSD 5.1-SECURITY (i386) [using slang 10405] [using libiconv 1.9] 
[using libidn 0.4.6 (compiled with 0.4.6)]
-DOMAIN
-DEBUG
+HOMESPOOL  -USE_SETGID  +USE_DOTLOCK  -DL_STANDALONE  
-USE_FCNTL  +USE_FLOCK
+USE_POP  +USE_IMAP  -USE_GSS  +USE_SSL  -USE_SASL  -USE_SASL2  
+HAVE_REGCOMP  -USE_GNU_REGEX  
+HAVE_COLOR  -HAVE_START_COLOR  -HAVE_TYPEAHEAD  -HAVE_BKGDSET  
-HAVE_CURS_SET  -HAVE_META  -HAVE_RESIZETERM  
+CRYPT_BACKEND_CLASSIC_PGP  +CRYPT_BACKEND_CLASSIC_SMIME  -CRYPT_BACKEND_GPGME  
-BUFFY_SIZE -EXACT_ADDRESS  -SUN_ATTACHMENT  
+ENABLE_NLS  +LOCALES_HACK  -HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET  
+HAVE_LANGINFO_YESEXPR  
+HAVE_ICONV  -ICONV_NONTRANS  +HAVE_LIBIDN  +HAVE_GETSID  +HAVE_GETADDRINFO  
+USE_HCACHE  
-ISPELL
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="Maildir"
PKGDATADIR="/usr/local/share/mutt"
SYSCONFDIR="/usr/local/etc"
EXECSHELL="/bin/sh"
-MIXMASTER

patch-1.5.6.tt.ja.1

--- End Message ---