From: Andrej Borsenkow <borsenkow.msk@sni.de>
To: Peter Stephenson <pws@ifh.de>
Cc: Zsh hackers list <zsh-workers@math.gatech.edu>
Subject: Re: Announcement draft
Date: Thu, 1 Aug 1996 13:10:42 +0400 (MOW) [thread overview]
Message-ID: <Pine.SV4.3.95.960801125025.4508D-100000@itsrm1> (raw)
In-Reply-To: <199608010831.KAA28871@hydra.ifh.de>
On Thu, 1 Aug 1996, Peter Stephenson wrote:
>
> Anyone know the proper backslash rules for here documents?
>
It depends on what "proper" rules are ;)
Here is relevant part form XPG4 Shell:
1. Section 2.7.4 (Here-document)
...
If no character in word are qouted, all lines of the here-document will be
expanded for parameter expansion, command substitution and arithmetic
expansion. In this case, the backslash in the input will behave as the
backslash inside double-quotes (see Section 2.2.3) However, the
double-quote character (") will not be treated specially within a
here-document, except when the double-quote appears within $(), ``, or
${}.
...
2. Section 2.2.3 (Double-quoting)
Characters to be treated specially in double-quotes:
$ - dollar sign
` - backquote
\ - backslash *only when followed by one of characters $ ` " \ <newline>*
...
In double-quote, if a backslash is immediately followed by a character
that would be interpreted as having special meaning, the backslash is
deleted and the subsequent character is taken literally. If a backslash
does not precede a character, that would have a special meaning, it is
left in place unmodified and the character immediately following it is
also left unmodified.
...
=== End of citation
It implies, that \" and \\" are the same in here-document. Wonder.
If it helps ...
greetings
-------------------------------------------------------------------------
Andrej Borsenkow Fax: +7 (095) 252 01 05
SNI ITS Moscow Tel: +7 (095) 252 13 88
NERV: borsenkow.msk E-Mail: borsenkow.msk@sni.de
-------------------------------------------------------------------------
next prev parent reply other threads:[~1996-08-01 9:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-31 21:11 Zoltan Hidvegi
1996-07-31 22:15 ` Zefram
1996-08-01 6:36 ` Bas V. de Bakker
1996-08-01 8:31 ` Peter Stephenson
1996-08-01 9:04 ` Running zsh as sh (Was: Announcement draft) Bas V. de Bakker
1996-08-01 9:10 ` Andrej Borsenkow [this message]
1996-08-01 13:49 ` Here docs Peter Stephenson
1996-08-01 14:07 ` Zoltan Hidvegi
1996-08-01 16:27 ` More Configure problems Peter Stephenson
1996-08-01 17:40 ` Peter Stephenson
1996-08-01 17:55 ` Zoltan Hidvegi
1996-08-01 21:03 ` Zoltan Hidvegi
1996-08-01 23:30 ` Zoltan Hidvegi
1996-08-02 8:32 ` Peter Stephenson
1996-08-02 10:03 ` Andrej Borsenkow
1996-08-02 13:29 ` Zoltan Hidvegi
1996-08-02 1:03 ` Zefram
1996-08-01 14:42 ` Announcement draft Zoltan Hidvegi
1996-08-08 15:13 ` sh compatibility again :-> Andrej Borsenkow
1996-08-12 2:18 ` Zoltan Hidvegi
1996-08-12 4:36 ` Bart Schaefer
1996-08-12 5:00 ` Zefram
1996-08-12 6:01 ` Bart Schaefer
1996-08-12 6:34 ` Bart Schaefer
1996-08-12 6:20 ` Andrej Borsenkow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SV4.3.95.960801125025.4508D-100000@itsrm1 \
--to=borsenkow.msk@sni.de \
--cc=pws@ifh.de \
--cc=zsh-workers@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).