do not make semicolons special in the config file anymore.

[apps/madmutt.git] / doc / muttrc.man.tail

diff --git a/doc/muttrc.man.tail b/doc/muttrc.man.tail
index d9399a8..b9a93b7 100644 (file)
--- a/doc/muttrc.man.tail
+++ b/doc/muttrc.man.tail
@@ -1,4 +1,21 @@
 .\" -*-nroff-*-
+.SH INCOMPABILITIES WITH MUTT
+.PP
+.nf
+\fBsemicolons and multicommands\fP
+.fi
+.IP
+Unlike mutt, madmutt does not supports multiple commands per line.  Meaning that
+semicolons (\(lq\fB;\fP\(rq) are not special characters at all, and do not need
+to be escaped anymore.  Though, if you have escaped semicolons in your rc file,
+madmutt will understand them correctly. Only multiple commands must be
+rewritten, by just splitting the commands. So it's still possible to have a
+madmuttrc that mutt understands (and the reverse too).
+.IP
+The rationale is that it's quite a common character (especially in headers as
+it's the parameter separator) and that many commands per line is not a very good
+practice for readability either. And as it was sometimes special sometimes not,
+it also complicated the parsing a lot, hence the feature has been removed.
 .SH SEE ALSO
 .PP
 .BR iconv (1),
@@ -6,15 +23,15 @@
 .BR mailcap (5),
 .BR maildir (5),
 .BR mbox (5),
-.BR muttng (1),
+.BR madmutt (1),
 .BR printf (3),
 .BR regex (7),
 .BR strftime (3)
 .PP
-The Mutt-ng Manual
+The Madmutt Manual
 .PP
-The Mutt-ng home page: http://mutt-ng.berlios.de
+The Madmutt home page: http://www.muttng.org
 .SH AUTHOR
 .PP
-Michael Elkins, and others.  Use <mutt-ng-devel@lists.berlios.de> to contact
+Michael Elkins, and others.  Use <Madmutt-devel@lists.berlios.de> to contact
 the developers.