X-Git-Url: http://git.madism.org/?p=apps%2Fmadmutt.git;a=blobdiff_plain;f=legacy%2Fdoc%2Fmuttrc.man.tail;fp=legacy%2Fdoc%2Fmuttrc.man.tail;h=b9a93b7d41834ca72a2cade47bb79511fdb8901e;hp=0000000000000000000000000000000000000000;hb=3ad8157bbbc6b9fae1c3252aad1c07fcccd92004;hpb=2fea7732a573b94a4d5dcf7e641ef067472e9cab;ds=sidebyside

diff --git a/legacy/doc/muttrc.man.tail b/legacy/doc/muttrc.man.tail
new file mode 100644
index 0000000..b9a93b7
--- /dev/null
+++ b/legacy/doc/muttrc.man.tail
@@ -0,0 +1,37 @@
+.\" -*-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),
+.BR iconv (3),
+.BR mailcap (5),
+.BR maildir (5),
+.BR mbox (5),
+.BR madmutt (1),
+.BR printf (3),
+.BR regex (7),
+.BR strftime (3)
+.PP
+The Madmutt Manual
+.PP
+The Madmutt home page: http://www.muttng.org
+.SH AUTHOR
+.PP
+Michael Elkins, and others.  Use <Madmutt-devel@lists.berlios.de> to contact
+the developers.