From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: [bug] {fd}<<EOF
Date: Thu, 20 Jun 2019 06:02:14 +0100 [thread overview]
Message-ID: <20190620050214.iex364omy7kfxqng@chaz.gmail.com> (raw)
$ zsh -xc $': {fd}<< EOF\nEOF'
+zsh:1> [[ - $'\C-D'zsh:1: bad cond code
]]
On the more complicated code I first ran into the problem, it
was crashing with "out of memory".
exec {fd}<<EOF
EOF
is a bash-compatible way to get a temp file that automatically
cleans up on exit. Needs Linux or Cygwin to manipulate it with
/dev/fd/$fd
--
Stephane
next reply other threads:[~2019-06-20 5:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 5:02 Stephane Chazelas [this message]
2019-06-24 19:02 ` Peter Stephenson
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=20190620050214.iex364omy7kfxqng@chaz.gmail.com \
--to=stephane.chazelas@gmail.com \
--cc=zsh-workers@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).