test-cases to cover quoting of the newline character, and the documentation extended.

1 files changed, 17 insertions, 0 deletions

diff --git a/doc/exec.n b/doc/exec.n
index 3857a71..e40b596 100644
--- a/doc/exec.n
+++ b/doc/exec.n
@@ -207,6 +207,19 @@ information is instead sent to the console, if one is present, or is
 discarded.
 .RS
 .PP
+Note that the current escape resp. quoting of arguments for windows works only
+with executables using CommandLineToArgv, CRT-library or similar, as well as
+with the windows batch files (excepting the newline, see below).
+Although it is the common escape algorithm, but, in fact, the way how the
+executable parses the command-line (resp. splits it into single arguments)
+is decisive.
+.PP
+Unfortunately, there is currently no way to supply newline character within 
+an argument to the batch files (\fB.cmd\fR or \fB.bat\fR) or to the command 
+processor (\fBcmd.exe /c\fR), because this causes truncation of command-line
+(also the argument chain) on the first newline character. 
+But it works properly with an executable (using CommandLineToArgv, etc).
+.PP
 The Tk console text widget does not provide real standard IO capabilities.
 Under Tk, when redirecting from standard input, all applications will see an
 immediate end-of-file; information redirected to standard output or standard
@@ -415,6 +428,10 @@ that sometimes pop up:
 .CE
 With the file \fIcmp.bat\fR looking something like:
 .CS
+@gcc %*
+.CE
+or like another variant using single parameters:
+.CS
 @gcc %1 %2 %3 %4 %5 %6 %7 %8 %9
 .CE
 .PP