From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: Aryn Starr <whereislelouch@icloud.com>
Cc: zsh-workers@zsh.org
Subject: Re: [Feature Request] Adding option to support triple quotes
Date: Wed, 14 Aug 2019 10:54:49 +0100 [thread overview]
Message-ID: <20190814095449.s7mgevyo5tdhfyby@chaz.gmail.com> (raw)
In-Reply-To: <6EA30061-5610-4CCA-93FB-0A160E2002A3@icloud.com>
2019-08-13 10:36:53 +0430, Aryn Starr:
> Adding an option to zsh to support triple quotes
> (TRIPLE_QUOTES) would make possible much more readable code.
[...]
We could also implement mksh's "$(<<'EOF'
arbitrary text that mustn't end in empty lines
EOF
)"
That already works in zsh, but is not optimised like in mksh as
it does "$(cat <<'EOF'
arbitrary text that mustn't end in empty lines
EOF
)" while mksh treats it specially as effectively a kind of
quotes.
mksh also supports $(<<'EOF'
foo
EOF)
(though that's probably not POSIX).
See also perl's q(...) and qq(...) that are more compatible with
the shell syntax than those python '''/""".
See:
$ a="'"; print -r ${(qq)a}
''\'''
--
Stephane
next prev parent reply other threads:[~2019-08-14 9:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 6:06 Aryn Starr
2019-08-13 9:06 ` Mikael Magnusson
2019-08-13 20:52 ` Aryn Starr
2019-08-13 16:28 ` Daniel Shahaf
2019-08-13 20:40 ` Aryn Starr
2019-08-14 9:54 ` Stephane Chazelas [this message]
2019-08-15 14:28 ` Aryn Starr
2019-08-15 15:56 ` Daniel Shahaf
[not found] <2c845fb0-d628-400f-a805-ad8356b6d87a@www.fastmail.com>
[not found] ` <7EBD1ADA-7179-4EEF-97CA-DBE4371D80D6@icloud.com>
[not found] ` <876f807b-dfdd-4246-8cfe-7cf6f373ac88@www.fastmail.com>
[not found] ` <f053e72e-e22e-4729-a2de-eaa712119728@www.fastmail.com>
2019-08-15 16:23 ` Aryn Starr
2019-08-17 5:31 ` Bart Schaefer
2019-08-17 6:30 ` Stephane Chazelas
2019-08-17 8:19 ` Stephane Chazelas
2019-08-18 4:24 ` Mikael Magnusson
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=20190814095449.s7mgevyo5tdhfyby@chaz.gmail.com \
--to=stephane.chazelas@gmail.com \
--cc=whereislelouch@icloud.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).