X-Git-Url: http://git.madism.org/?p=apps%2Fmadmutt.git;a=blobdiff_plain;f=doc%2Fmuttrc.man.tail;h=b9a93b7d41834ca72a2cade47bb79511fdb8901e;hp=2f0b8955831e5dc9aefdda8527d05d723ff722a8;hb=bf962aa95d973d266241deb552e5e4ffae484692;hpb=59f5843ea1ff2f68a60ceaeb497cf195bb512238

diff --git a/doc/muttrc.man.tail b/doc/muttrc.man.tail
index 2f0b895..b9a93b7 100644
--- 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),