From 6b4750772eba54f979455376713b49900a4d5016 Mon Sep 17 00:00:00 2001 From: nion Date: Fri, 11 Mar 2005 15:16:15 +0000 Subject: [PATCH] Nico Golde: - included manual patch by Lars Noschinski git-svn-id: svn://svn.berlios.de/mutt-ng/trunk@170 e385b8ad-14ed-0310-8656-cc95a2468c6d --- doc/manual.sgml.head | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/doc/manual.sgml.head b/doc/manual.sgml.head index 3397b32..2b5df61 100644 --- a/doc/manual.sgml.head +++ b/doc/manual.sgml.head @@ -814,6 +814,36 @@ A \ at the end of a line can be used to split commands over multiple lines, provided that the split points don't appear in the middle of command names. +Please note that, unlike the various shells, mutt-ng interpretes a ``\'' +at the end of a line also in comments. This allows you to disable a command +split over multiple lines with only one ``#''. + + +# folder-hook . \ + set realname="Michael \"MuttDude\" Elkins" + + +When testing your config files, beware the following caveat. The backslash +at the end of the commented line extends the current line with the next line +- then referred to as a ``continuation line''. As the first line is +commented with a hash (#) all following continuation lines are also +part of a comment and therefore are ignored, too. So take care of comments +when continuation lines are involved within your setup files! + +Abstract example: + + +line1\ +line2a # line2b\ +line3\ +line4 +line5 + + +line1 ``continues'' until line4. however, the part after the # is a +comment which includes line3 and line4. line5 is a new line of its own and +thus is interpreted again. + It is also possible to substitute the output of a Unix command in an initialization file. This is accomplished by enclosing the command in backquotes (``). For example, -- 2.20.1