From: Enrico Maria Crisostomo <enrico.m.crisostomo@gmail.com>
To: zsh-users@zsh.org
Subject: Re: Different behaviour when interpreting a here-document between 5.3 and 5.5.1
Date: Sat, 21 Apr 2018 00:04:56 +0200 [thread overview]
Message-ID: <54E1C2BA-1A1B-4C54-85B8-2BF958938213@gmail.com> (raw)
In-Reply-To: <E1DC38CD-F8BD-4128-8808-261D260462F7@gmail.com>
> On 19 Apr 2018, at 23:52, Enrico Maria Crisostomo <enrico.m.crisostomo@gmail.com> wrote:
>
> Hi,
>
> I'm struggling with an apparently simple problem. A script of mine has a function that writes a here-document whose lines end with a backslash. The script has been working fine until zsh has been updated recently.
>
> The relevant part of the code is the following
>
> mp_calculate_checksums()
> {
> cat <<EOF
> checksums rmd160 ${CHECKSUM_RMD160} \\
> sha256 ${CHECKSUM_SHA256} \\
> size ${CHECKSUM_SIZE}
> EOF
> }
>
> The expected output is something like:
>
> checksums rmd160 281d97a37125fca07ff81a72ac337f6a23f5d2b0 \
> sha256 233cd8724fd95e10b82ed62c692e7e79cca9114b49be834e65cd05b529d8ba70 \
> size 31
>
> When running the same script on 5.5.1, I get a single line of output, as if the last backslash of \\ were escaping the newline.
>
> checksums rmd160 281d97a37125fca07ff81a72ac337f6a23f5d2b0 \ sha256 233cd8724fd95e10b82ed62c692e7e79cca9114b49be834e65cd05b529d8ba70 \ size 31
>
> I haven't been able to troubleshoot it so far, and the zsh documentation seems to imply that the correct behaviour is the former, not the latter.
>
> Thanks in advance for you help,
> --
> Enrico
Thanks for your answer, Bart. Apologies for manually quoting it, but I haven't received a mail from the mailing list, so I can't reply:
> Yeah, this is commit 47aa6095 aka workers/42355. It's recognizing
> backslash-newline but not whether the backslash is itself escaped.
>
> The NEWS file should have mentioned the change to here-documents, I
> think. However, not catching the double backslash is a bug. However,
> part 2, figuring this out requires scanning backwards to see if you
> have an even or odd number of trailing backlashes, or scanning forward
> and tokenizing while consuming the document. Bleah.
Should I file a bug report, write to zsh-workers, or do something else? Or may I consider that your answering the mail is equivalent to a bug having been open?
Thanks,
--
Enrico
prev parent reply other threads:[~2018-04-20 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 21:52 Enrico Maria Crisostomo
2018-04-19 23:48 ` Bart Schaefer
2018-04-20 22:04 ` Enrico Maria Crisostomo [this message]
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=54E1C2BA-1A1B-4C54-85B8-2BF958938213@gmail.com \
--to=enrico.m.crisostomo@gmail.com \
--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).