zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Why does $'' not expand inside ""?
Date: Thu, 23 Dec 2010 11:38:43 -0800	[thread overview]
Message-ID: <101223113843.ZM23418@torch.brasslantern.com> (raw)
In-Reply-To: <201012232041.34665@-zyx>

On Dec 23,  8:41pm, ZyX wrote:
} Subject: Re: ( Text in unknown character set UTF-8 not shown )

Sorry about that weird subject.

} > 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."

Ah, but backticks were already present in the shell.  The conflict is
with "How did this $'with " embedded' parse before $'existed'?"

} > 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).

Entirely understandable nowadays, but much of the zsh doc was written
when zsh was always the shell to which someone switched from another
shell with which they were already familiar.  That's not the case as
often any more now that zsh is packaged with several OS dists, and is
not the case for $'...', but the tendency to write that way remains.


      reply	other threads:[~2010-12-23 19:39 UTC|newest]

Thread overview: 2+ 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   ` ( Text in unknown character set UTF-8 not shown ) ZyX
2010-12-23 19:38     ` Bart Schaefer [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=101223113843.ZM23418@torch.brasslantern.com \
    --to=schaefer@brasslantern.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).