From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Kirill Likhodedov <kirill.likhodedov@jetbrains.com>
Cc: git <git@vger.kernel.org>
Subject: Re: git show doesn't work on file names with square brackets
Date: Sat, 6 Feb 2016 15:21:02 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1602061518220.2964@virtualbox> (raw)
In-Reply-To: <6A7D4447-AC25-4591-9DA7-CD153198EC64@jetbrains.com>
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
Hi Kirill,
On Sat, 6 Feb 2016, Kirill Likhodedov wrote:
> Is it a bug or I just didn’t find the proper way to escape the brackets?
>
> Steps to reproduce:
>
> git init brackets
> cd brackets/
> echo ‘asd’ > bra[ckets].txt
> git add bra\[ckets\].txt
> git commit -m initial
> git show HEAD:bra[ckets].txt
This is expected behavior of the Bash you are using. The commands that I
think would reflect your intentions would be:
git init brackets
cd brackets
echo 'asd' > 'bra[ckets].txt'
git add 'bra[ckets].txt'
git commit -m initial
git show 'HEAD:bra[ckets].txt'
You could also escape the brackets with a backslash, as you did, but you
would have to do it *every* time you write the path, not just in the `git
add` incantation.
Ciao,
Johannes
next prev parent reply other threads:[~2016-02-06 14:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 13:16 git show doesn't work on file names with square brackets Kirill Likhodedov
2016-02-06 14:21 ` Johannes Schindelin [this message]
2016-02-06 14:29 ` Kirill Likhodedov
2016-02-06 16:10 ` Johannes Schindelin
2016-02-06 23:48 ` Duy Nguyen
2016-02-07 15:11 ` Kirill Likhodedov
2016-02-08 5:06 ` Duy Nguyen
2016-02-08 14:15 ` Jeff King
2016-02-08 14:24 ` Jeff King
2016-02-08 15:07 ` Jeff King
2016-02-08 19:35 ` Junio C Hamano
2016-02-08 19:52 ` Jeff King
2016-02-08 20:20 ` Jeff King
2016-02-08 20:56 ` Jeff King
2016-02-08 22:36 ` Junio C Hamano
2016-02-10 15:45 ` Jeff King
2016-02-09 20:37 ` Junio C Hamano
2016-02-10 16:15 ` Jeff King
2016-02-10 17:35 ` Junio C Hamano
2016-02-10 21:12 ` Jeff King
2016-02-10 21:12 ` [PATCH 1/3] checkout: reorder check_filename conditional Jeff King
2016-02-10 21:31 ` Junio C Hamano
2016-02-10 21:14 ` [PATCH 2/3] check_filename: tighten dwim-wildcard ambiguity Jeff King
2016-02-10 21:19 ` [PATCH 3/3] get_sha1: don't die() on bogus search strings Jeff King
2016-02-10 21:52 ` Junio C Hamano
2016-02-07 15:09 ` git show doesn't work on file names with square brackets Kirill Likhodedov
2016-02-07 17:10 ` Johannes Schindelin
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=alpine.DEB.2.20.1602061518220.2964@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=kirill.likhodedov@jetbrains.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.
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).