From: "J.D. Laub" <jdl@clinicom.com>
To: zsh-workers@math.gatech.edu
Subject: here-document/multiline parameter conflict
Date: Fri, 23 Aug 1996 11:11:49 -0600 (MDT) [thread overview]
Message-ID: <199608231711.LAA52966@clinicom.com> (raw)
I didn't see this mentioned in Etc/BUGS for 3.0.0. Is the following
behavior by design? It seems really bizarre.
This (trivial) script works under a standard ksh:
#!/bin/ksh
cat <<EOF | sed -e '/t/{
s/t/T/
}'
one
three
five
EOF
Changing the first line to #!/usr/local/bin/zsh -f yields this:
quirk: unmatched ' [9]
However, if I embed the here-document within the parameter to sed, it
works under zsh:
#!/usr/local/bin/zsh -f
cat <<EOF | sed -e '/t/{
one
three
five
EOF
s/t/T/
}'
--
J.D. Laub (Laubster) HBOC/CliniCom|"I think you're very, very, very, very, very,
jdl@clinicom.com Boulder,CO |very, very, very, very, ..." - Flying Lizards
next reply other threads:[~1996-08-23 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-23 17:11 J.D. Laub [this message]
1996-08-23 17:53 ` Zoltan Hidvegi
1996-08-23 17:58 ` J.D. Laub
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=199608231711.LAA52966@clinicom.com \
--to=jdl@clinicom.com \
--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).