From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Is this a bug? Why not?
Date: Wed, 31 Mar 2010 08:11:53 -0700 [thread overview]
Message-ID: <100331081153.ZM2688@torch.brasslantern.com> (raw)
In-Reply-To: <20100331060602.GA91691@redoubt.spodhuis.org>
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.
On Mar 30, 11:06pm, Phil Pennock wrote:
} Subject: Re: Is this a bug? Why not?
}
} So the string ${var} when treated as a variable-name is empty but
} defined? The four expansions with a nested ${var} are entirely
} consistent with the behaviour when expanding a variable which is
} defined with a value of length 0.
}
} Seems unusual, but consistent.
Indeed. OK, I can live with that, as it's been that way forever.
} In bash, ksh, bad substitution. In ksh93, it gets weird:
} $ echo ${var-???}
} OSM SCM bin dbg doc etc lib man src tmp www
} $ echo ${${var}-???}
} ksh93: syntax error: `!' unexpected
That is weird, but AFAIK only zsh of all shells allows wrapping ${...}
in another ${...} as valid syntax, so this may just be an error ksh93
didn't catch.
} The ksh reference-name expansion made me think of the somewhat opposite
} expansion in zsh, (P)var ...
}
} Hrm, zsh 4.3.10 1.4705:
}
} % print ${(P)-???}
} zsh: 0239BCJPXZgiklms: ??
}
} Strange that the first entry is somehow tying into expanding $- for the
} shell options ...
Actually that makes perfect sense; only the :- and :+ forms are doc'd
as working with a missing parameter name, so ${(P)-} really does mean
to grab the value of $- and try to use that as a parameter name. It
otherwise has to behave like ${-?string}.
next prev parent reply other threads:[~2010-03-31 15:12 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 [this message]
2010-04-01 8:26 ` Phil Pennock
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=100331081153.ZM2688@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).