From 1f9b40a4bd80acec404c57a29fd0159220f2a057 Mon Sep 17 00:00:00 2001
From: kichik <kichik@212acab6-be3b-0410-9dea-997c60f758d6>
Date: Sat, 9 Sep 2006 08:57:38 +0000
Subject: [PATCH] explain about comments being extended

git-svn-id: https://svn.code.sf.net/p/nsis/code/NSIS/trunk@4745 212acab6-be3b-0410-9dea-997c60f758d6
---
 Docs/src/script.but | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/Docs/src/script.but b/Docs/src/script.but
index 91c78e61..bcf80eed 100644
--- a/Docs/src/script.but
+++ b/Docs/src/script.but
@@ -17,6 +17,9 @@ Lines beginning with ; or # are comments. You can put comments after commands. Y
 \c ; Comment
 \c # Comment
 \c
+\c # Comment \
+\c     Another comment line (see `Long commands` section below)
+\c
 \c /*
 \c Comment
 \c Comment
@@ -84,6 +87,11 @@ To extend a command over multiple lines, use a backslash (\\) at the end of the
 \c      to keep, click No)" \
 \c     IDNO NoRemoveLabel
 
+Line extension for long commands works for comments as well. It can be a bit confusing, so it should be avoided.
+
+\c # A comment \
+\c     still a comment here...
+
 \\<b\\>Configuration file\\</b\\>
 
 If a file named "nsisconf.nsh" in the config directory exists, it will be included by default before any scripts (unless the /NOCONFIG command line parameter is used). The config directory on Windows is the same directory as makensis.exe is in. On other platforms this is set at install time and defaults to $PREFIX/etc/. You can alter this at runtime, see \k{usageenvironment} for more information.