From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: "Jason R. Coombs" <jaraco@jaraco.com>
Cc: zsh-workers@zsh.org
Subject: Re: spaces not escaped when completion matches filename with spaces
Date: Mon, 24 Oct 2016 20:54:27 +0000 [thread overview]
Message-ID: <20161024205427.GA8911@fujitsu.shahaf.local2> (raw)
In-Reply-To: <5DA37713-53DD-43BA-A4C7-B77BB05E6811@jaraco.com>
Jason R. Coombs wrote on Mon, Oct 24, 2016 at 20:19:06 +0000:
> $ git add f^t
> fatal: pathspec 'foo' did not match any files
>
> The ^t represents a tab and completes “f” to “foo bar”, but without any escaping.
In master it does add the escaping:
% git add fo<TAB>
% git add foo\ bar
prev parent reply other threads:[~2016-10-24 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 20:19 Jason R. Coombs
2016-10-24 20:54 ` Daniel Shahaf [this message]
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=20161024205427.GA8911@fujitsu.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=jaraco@jaraco.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).