From: Hannu Koivisto <azure@iki.fi>
To: Nikolai Weibull <now@bitwi.se>
Cc: "Zsh Users' List" <zsh-users@zsh.org>
Subject: Re: Completing UNC paths in Windows/Cygwin
Date: Wed, 07 Sep 2011 18:54:42 +0300 [thread overview]
Message-ID: <83r53sbb5p.fsf@kalahari.s2.org> (raw)
In-Reply-To: <CADdV=Ms37Km-uZFoG3FMjrwTM5GezgvRSXhr00Mt-mNwndKG0w@mail.gmail.com> (Nikolai Weibull's message of "Wed, 7 Sep 2011 11:58:37 +0200")
Nikolai Weibull <now@bitwi.se> writes:
> 2011/9/7 Hannu Koivisto <azure@iki.fi>:
>> //machine/share/directory/f<complete> doesn't work either for me.
>
> Try setting the accept-exact-dirs zstyle and see if that helps.
It does indeed fix //machine/share/directory/f<complete> and
//machine/C\$/directory/f<complete> but //machine/C\$/<tab> just
causes the shell to get stuck forever (Ctrl-C helps), just like
//machine/<tab> (I guess that one is not surprising as it would
probably require some special code for listing shares).
I have also observed that Program\ Files\ \(x86\)/<tab> fails if
accept-exact style is true. Without the parentheses it doesn't
fail.
It turns out that setting accept-exact-dirs to true in addition to
accept-exact fixes that case.
Admittedly I don't really understand accept-exact, even after
reading the documentation. For some reason I no longer remember I
have copy&pasted it to my .zshrc's Windows/Cygwin specific section
in addition to zstyle ':completion:*' matcher-list
'm:{a-zA-Z}={A-Za-z}' (which I believe I understand).
Am I supposed to set accept-exact-dirs to true if accept-exact is
true? Is there something that zsh could do so that users wouldn't
have to set accept-exact-dirs in order to have
//machine/foo/bar/<tab> work?
--
Hannu
next prev parent reply other threads:[~2011-09-07 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 17:47 Hannu Koivisto
2011-09-07 7:45 ` Nikolai Weibull
2011-09-07 9:51 ` Hannu Koivisto
2011-09-07 9:58 ` Nikolai Weibull
2011-09-07 15:54 ` Hannu Koivisto [this message]
2011-09-07 16:02 ` 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=83r53sbb5p.fsf@kalahari.s2.org \
--to=azure@iki.fi \
--cc=now@bitwi.se \
--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).