X-Git-Url: http://git.madism.org/?a=blobdiff_plain;f=doc%2Fmanual.sgml.head;h=199c8519d7b3dc2bf87d472303b4f7500c26dc08;hb=e6737dc67953504df4a3f1e82849ef092a337b99;hp=3397b3279ae8d91fe30111df1e3f639b6a700601;hpb=f1ca09e359410e2b578a24a647fc383edd5ab4b5;p=apps%2Fmadmutt.git
diff --git a/doc/manual.sgml.head b/doc/manual.sgml.head
index 3397b32..199c851 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,
@@ -1745,14 +1775,14 @@ ifndef feature_nntp 'push q'
# ifndef newsrc 'push q'
# or
# ...
-
+
To only set the when the system's SVN
is recent enough to have it:
ifdef imap_mail_check 'set imap_mail_check=300'
-
+
Removing hooks