From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 9480@debbugs.gnu.org, kjambunathan@gmail.com
Subject: bug#9480: 24.0.50; (vc-git) stash@{n} - requires shell quoting?
Date: Tue, 13 Sep 2011 14:21:10 -0400 [thread overview]
Message-ID: <0dvcswl2w9.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83sjo0wjhm.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 13 Sep 2011 18:27:17 +0300")
Eli Zaretskii wrote:
> This should generally work fine, except that IMO globbing in this case
> is simply buggy: the braces are removed although a real shell would
> expand "{0}" into itself.
I agree.
http://www.gnu.org/s/bash/manual/bash.html#Brace-Expansion
A correctly-formed brace expansion must contain unquoted opening and
closing braces, and at least one unquoted comma or a valid sequence
expression. Any incorrectly formed brace expansion is left unchanged.
http://tiswww.case.edu/php/chet/bash/FAQ
Bash FAQ D2:
D2) Why doesn't bash treat brace expansions exactly like csh?
The only difference between bash and csh brace expansion is that
bash requires a brace expression to contain at least one unquoted
comma if it is to be expanded. Any brace-surrounded word not
containing an unquoted comma is left unchanged by the brace
expansion code. This affords the greatest degree of sh
compatibility.
next prev parent reply other threads:[~2011-09-13 18:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 7:09 bug#9480: 24.0.50; (vc-git) stash@{n} - requires shell quoting? Jambunathan K
2011-09-12 7:29 ` Eli Zaretskii
2011-09-12 9:05 ` Jambunathan K
2011-09-12 10:51 ` Eli Zaretskii
2011-09-12 11:22 ` Jambunathan K
2011-09-12 11:50 ` Antoine Levitt
2011-09-12 11:56 ` Eli Zaretskii
2011-09-13 4:46 ` Jambunathan K
2011-09-13 1:39 ` Richard Stallman
2011-09-13 4:03 ` Glenn Morris
2011-09-13 4:37 ` Eli Zaretskii
2011-09-13 5:14 ` Jambunathan K
2011-09-13 6:17 ` Jambunathan K
2011-09-13 6:54 ` Eli Zaretskii
2011-09-13 18:05 ` Stefan Monnier
2011-09-13 13:35 ` Stefan Monnier
2011-09-13 15:27 ` Eli Zaretskii
2011-09-13 18:21 ` Glenn Morris [this message]
2011-09-14 10:58 ` Jambunathan K
2011-09-14 11:57 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0dvcswl2w9.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=9480@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kjambunathan@gmail.com \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).