X-Git-Url: http://git.madism.org/?p=apps%2Fmadmutt.git;a=blobdiff_plain;f=doc%2Fmuttrc.man.tail;h=b9a93b7d41834ca72a2cade47bb79511fdb8901e;hp=38bd4c78881691c3891b506e8ab298c70dc26e6d;hb=bf962aa95d973d266241deb552e5e4ffae484692;hpb=85486f8623f6d9a12f7b251445ac9d203d3ae348 diff --git a/doc/muttrc.man.tail b/doc/muttrc.man.tail index 38bd4c7..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), @@ -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://www.muttng.org +The Madmutt home page: http://www.muttng.org .SH AUTHOR .PP -Michael Elkins, and others. Use to contact +Michael Elkins, and others. Use to contact the developers.