From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Is this a bug? Why not?
Date: Thu, 01 Apr 2010 07:36:18 -0700 [thread overview]
Message-ID: <100401073618.ZM10593@torch.brasslantern.com> (raw)
In-Reply-To: <20100401082624.GA56998@redoubt.spodhuis.org>
On Apr 1, 1:26am, Phil Pennock wrote:
} Subject: Re: Is this a bug? Why not?
}
} 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).
} >
} > 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-${(~):-*}}
That isn't really what you mean, is it? The (~) flag only applies to
the (j::) et al. strings.
However, it's not even necessary to do the ${:-*} thing, ${~~foo-*} is
sufficient.
For austin-group purposes, however, I was hoping for something that did
not rely on parameter expansion flags. E.g., why doesn't the following
cause $foo to be quoted?
schaefer[516] ARGV0=sh Src/zsh
$ foo="???"
$ print ${foo+"$foo"}
Doc Etc Src
$
It works in bash.
next prev parent reply other threads:[~2010-04-01 14:36 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
2010-04-01 14:36 ` Bart Schaefer [this message]
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=100401073618.ZM10593@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).