zsh-workers
 help / color / mirror / code / Atom feed
From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: Is this a bug? Why not?
Date: Thu, 1 Apr 2010 01:26:24 -0700	[thread overview]
Message-ID: <20100401082624.GA56998@redoubt.spodhuis.org> (raw)
In-Reply-To: <100331081153.ZM2688@torch.brasslantern.com>

On 2010-03-31 at 08:11 -0700, Bart Schaefer wrote:
> Incidentally, this came up because of a discussion on the POSIX standards
> mailing list (austin-group) in which David Korn just asserted that he'd
> like to add the syntax ${"var"} which means to expand the value of var
> as if it's quoted (what zsh's normal mode does all the time).
> 
> This differs from "${var}" because you can write ${"var"-*} and get the
> value of $var quoted but the glob pattern unquoted.  Apparently the old
> Bourne shell allows the abominable "${var"-*}  (note quote placement
> overlapping with brace placement) to accomplish this.
> 
> I was hoping to be able to say "Oh, zsh already has syntax XYZ for that"
> but in fact we don't -- zsh either always, or never, does it, depending
> on the globsubst option; there's no way to flip globsubst on the fly.

No *neat* syntax.

% ls
lib         viewvc.conf
% print -l ${~~foo-${(~):-*}}
lib
viewvc.conf
% foo='???'
$ print -l ${~~foo-${(~):-*}}
???
% print -l $foo
lib
% unsetopt glob_subst
% print -l $foo      
???
%

*cough*


  reply	other threads:[~2010-04-01  8:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31  5:46 Bart Schaefer
2010-03-31  6:06 ` Phil Pennock
2010-03-31 15:11   ` Bart Schaefer
2010-04-01  8:26     ` Phil Pennock [this message]
2010-04-01 14:36       ` Bart Schaefer
2010-04-01 21:57         ` Phil Pennock
2010-04-01 22:51           ` Bart Schaefer
2010-04-09 14:37             ` Peter Stephenson
2010-04-17 13:06               ` Mikael Magnusson
2010-04-18 19:11                 ` 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=20100401082624.GA56998@redoubt.spodhuis.org \
    --to=zsh-workers+phil.pennock@spodhuis.org \
    --cc=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).