From: "Benjamin R. Haskell" <zsh@benizi.com>
To: Joke de Buhr <joke@seiken.de>
Cc: zsh-users <zsh-users@zsh.org>
Subject: Re: Completion and double quotes
Date: Wed, 11 Aug 2010 17:51:24 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.01.1008111741040.19568@hp> (raw)
In-Reply-To: <201008112130.10895.joke@seiken.de>
On Wed, 11 Aug 2010, Joke de Buhr wrote:
> Hi,
>
> Currently my completion is somehow configured to transform double
> quoted paths to backslash escaped paths.
>
> Example:
> ls /path/to/"file with"<TAB> -> /path/to/file\ with\ spaces
>
> I would like the completion not to touch the quotation. But I can't
> figure out how to get zsh to do this. The completion should work like
> this.
>
> Example:
> ls /path/to/"file with"<TAB> -> /path/to/"file with spaces"
>
> I don't remember what completion options caused the current behavior
> but I remember having zsh configured to not touch the quotes.
Are you sure your above example worked before? It's always bugged me a
little (but not enough to search for it) that zsh leaves:
"/path/to/file with<Tab>
as a quoted string:
"/path/to/file with spaces"
but:
/path/to/"file with<Tab>
becomes toothpicked[1]:
/path/to/file\ with\ spaces
So, I'd also be interested to know what I'm overlooking.
A similar thing that bothers me is the way named directories are
somewhat inconsistently expanded. (From my perspective, that is. It's
probably entirely internally consistent.) I can't come up with a
minimal example right now, but I notice it most when trying to do things
like:
for l in ~/bin/{*.pl,<Tab>
(That is: combinations of bracket expansion and file completion.)
Perhaps the cure(s) are the same or similar? (Wouldn't be surprised if
the latter weren't curable.)
--
Best,
Ben
[1] http://en.wikipedia.org/wiki/Leaning_toothpick_syndrome
next prev parent reply other threads:[~2010-08-11 21:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 19:30 Joke de Buhr
2010-08-11 21:51 ` Benjamin R. Haskell [this message]
2010-08-11 22:29 ` Joke de Buhr
2010-08-12 9:31 ` Peter Stephenson
2010-08-12 10:53 ` Joke de Buhr
2010-08-12 11:03 ` Peter Stephenson
2010-08-12 15:57 ` Bart Schaefer
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.LNX.2.01.1008111741040.19568@hp \
--to=zsh@benizi.com \
--cc=joke@seiken.de \
--cc=zsh-users@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).