From: ZyX <zyx.vim@gmail.com>
To: zsh-workers@zsh.org
Subject: Re: ( Text in unknown character set UTF-8 not shown )
Date: Thu, 23 Dec 2010 20:41:34 +0300 [thread overview]
Message-ID: <201012232041.34665@-zyx> (raw)
In-Reply-To: <101222231721.ZM21959@torch.brasslantern.com>
[-- Attachment #1: Type: Text/Plain, Size: 1101 bytes --]
Reply to message «Re: ( Text in unknown character set UTF-8 not shown )»,
sent 10:17:21 23 December 2010, Thursday
by Bart Schaefer:
> I believe the reasoning is that double-quote is allowed to appear
> inside $'...' and to expand $'...' inside double-quotes creates a
> parsing conflict. "How does this $'with " embeded' parse?"
"How does this $'with " embeded' parse?"
"Just like this `with " embedded` parse."
There are no parsing conflicts here, but
> Because it doesn't in any of the shells that introduced it before
> zsh had it.
is legitimate enough for me because it helps porting scripts from/to zsh.
> } It's not, as far as I can tell, mentioned in the documentation.
>
> The documentation for zsh tends to omit things that are assumed
> knowledge, particularly when a concept or feature originates from
> another source -- because if you didn't already know about it from
> the original source, why did you even think to use it?
But when I worked in bash I knew nothing about $'...' (because I even did not
know where to find documentation to tweak my inputrc).
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next parent reply other threads:[~2010-12-23 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=vnaRw3qxpuuEWF9t0K-TyPJKkhVUYy_8qR-=e@mail.gmail.com>
[not found] ` <101222231721.ZM21959@torch.brasslantern.com>
2010-12-23 17:41 ` ZyX [this message]
2010-12-23 19:38 ` Why does $'' not expand inside ""? Bart Schaefer
2010-11-13 15:07 _multi_parts -f doesn’t seem to have any effect Nikolai Weibull
2010-11-13 15:53 ` ( Text in unknown character set UTF-8 not shown ) Bart Schaefer
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=201012232041.34665@-zyx \
--to=zyx.vim@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).