Re: sh.1: backslash within double quotes

2017-12-29 Thread Jason McIntyre
On Sat, Dec 30, 2017 at 06:01:56AM +, kshe wrote:
> Hi,
> 
> Within double quotes, backslashes also escape newlines.  This is
> correctly documented in ksh.1, but not in sh.1.
> 

fixed, thanks.
jmc

> Index: sh.1
> ===
> RCS file: /cvs/src/bin/ksh/sh.1,v
> retrieving revision 1.145
> diff -u -p -r1.145 sh.1
> --- sh.1  15 Dec 2017 20:51:28 -  1.145
> +++ sh.1  28 Dec 2017 20:44:07 -
> @@ -1165,7 +1165,7 @@ if the user wants to indicate to the she
>  The following characters need quoting if their literal meaning is desired:
>  .Bd -literal -offset indent
>  | & ; < > ( ) $ \` \e " \(aq   
> -* ?  [ # ~ = %
> +* ? [ # ~ = %
>  .Ed
>  .Pp
>  A backslash
> @@ -1190,7 +1190,7 @@ A backslash
>  .Pq \e
>  within double quotes retains its special meaning,
>  but only when followed by a backquote, dollar sign,
> -double quote, or another backslash.
> +double quote, newline, or another backslash.
>  An at sign
>  .Pq @
>  within double quotes has a special meaning
> 
> Regards,
> 
> kshe
> 



sh.1: backslash within double quotes

2017-12-29 Thread kshe
Hi,

Within double quotes, backslashes also escape newlines.  This is
correctly documented in ksh.1, but not in sh.1.

Index: sh.1
===
RCS file: /cvs/src/bin/ksh/sh.1,v
retrieving revision 1.145
diff -u -p -r1.145 sh.1
--- sh.115 Dec 2017 20:51:28 -  1.145
+++ sh.128 Dec 2017 20:44:07 -
@@ -1165,7 +1165,7 @@ if the user wants to indicate to the she
 The following characters need quoting if their literal meaning is desired:
 .Bd -literal -offset indent
 | & ; < > ( ) $ \` \e " \(aq   
-* ?  [ # ~ = %
+* ? [ # ~ = %
 .Ed
 .Pp
 A backslash
@@ -1190,7 +1190,7 @@ A backslash
 .Pq \e
 within double quotes retains its special meaning,
 but only when followed by a backquote, dollar sign,
-double quote, or another backslash.
+double quote, newline, or another backslash.
 An at sign
 .Pq @
 within double quotes has a special meaning

Regards,

kshe