--- /dev/null
+.\" -*-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.