From: Ray Andrews <rayandrews@eastlink.ca>
To: Zsh Users <zsh-users@zsh.org>
Subject: here document within a switch fails to parse.
Date: Wed, 6 Jan 2021 07:13:45 -0800 [thread overview]
Message-ID: <db51fbd9-20d4-9a52-1925-1a2c9115771c@eastlink.ca> (raw)
function test1 ()
{
: <<'ENDCOM' # No problems here with either ending #1 or #2
echo "Bad Idea!" # Some commented code.
ENDCOM # Ending #1: comment-out one line ok.
case ${1} in
n ) echo en ;;
#: <<'ENDCOM' # This pair: "parse error near `\n'"
#ENDCOM
esac
#ENDCOM # Ending #2: comment-out most of function ok.
echo "What's goin' on?"
}
... So it seemed that a case statement won't tolerate a here document
within itself. But then there's this, which parses fine:
function test2 ()
{
case ${1} in
n ) echo en ;;
v )
: <<'ENDCOM' # But this pair works fine.
echo "BAD!" # Some commented code
ENDCOM
echo GOOD!: # Much better.
;;
esac
}
... So what am I missing? Sometimes the here document is perfectly
ignored, other times it creates an error. Looks wrong. So far I haven't
found any comparable errors but this.
next reply other threads:[~2021-01-06 15:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 15:13 Ray Andrews [this message]
2021-01-06 16:20 ` Daniel Shahaf
2021-01-06 17:17 ` Ray Andrews
2021-01-06 17:58 ` Lawrence Velázquez
2021-01-06 19:18 ` Bart Schaefer
2021-01-07 7:55 ` Ray Andrews
2021-01-07 15:32 ` Daniel Shahaf
2021-01-07 20:16 ` Ray Andrews
2021-01-08 15:27 ` Karsten Borgwaldt
2021-01-08 15:53 ` Lawrence Velázquez
2021-01-08 17:13 ` Ray Andrews
2021-01-08 18:06 ` Peter Stephenson
2021-01-08 19:39 ` Ray Andrews
2021-01-08 19:56 ` Bart Schaefer
2021-01-09 0:45 ` Ray Andrews
2021-01-09 17:28 ` Ray Andrews
2021-01-12 13:28 ` Daniel Shahaf
2021-01-12 14:45 ` Ray Andrews
2021-01-13 16:17 ` Daniel Shahaf
2021-01-13 21:57 ` Pier Paolo Grassi
2021-01-13 23:39 ` Ray Andrews
2021-01-13 23:54 ` Lawrence Velázquez
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=db51fbd9-20d4-9a52-1925-1a2c9115771c@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/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).