From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: <zsh-workers@sunsite.dk>
Subject: RE: Preserve initial // in path name completion
Date: Fri, 6 Jul 2001 14:32:52 +0400 [thread overview]
Message-ID: <004f01c10607$02c00180$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <200107060924.LAA12231@beta.informatik.hu-berlin.de>
>
> Currently not. Seems like we never came aroud to implementing it, but
> it can be made quite simply, see the patch below. It adds a style
> `preserve-prefix' which can be given a pattern and _path_files will then
> blindly keep any prefix matched by that pattern unchanged.
>
To my immense surprise even with preserve-prefix unset (but with your patch
and suitably set fake-files) and squeeze-slashes it happily completed inside
UNC paths, even respecting all matchers. Looks, like fake-files win?
> Would that be enough?
I do not quite understand but may be it even is not needed? Anyway, the only
problem. I have \\itsrm2\root$. I defined
zstyle ':completion:*' fake-files //:itsrm2 //itsrm2:root\$
zstyle ':completion:*' squeeze-slashes true
Then
(tty1)% l //i/r/t/s/zTAB
(tty1)% l //itsrm2/root\$/tools/share/z
Completing files
share/ src/
(tty1)% l //itsrm2/root\$/tools/src/zTAB
No matches for: `files' or `file'
I *do* have /tools/src/zsh:
(tty1)% l //i/r/t/s/z/s/mTAB
(tty1)% l //itsrm2/root\$/tools/src/zsh/s/m
Completing files
zsh/ zsh-4.0.x/
This obviously happens only with root$; any other share I've tried works.
-andrej
next prev parent reply other threads:[~2001-07-06 10:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 5:14 Andrej Borsenkow
2001-07-06 9:24 ` Sven Wischnowsky
2001-07-06 10:32 ` Andrej Borsenkow [this message]
2001-07-06 10:41 ` Sven Wischnowsky
2001-07-06 11:03 ` Andrej Borsenkow
2001-07-06 11:16 ` Andrej Borsenkow
2001-07-06 12:22 ` Sven Wischnowsky
2001-07-06 12:34 ` Andrej Borsenkow
2001-07-13 12:22 ` Andrej Borsenkow
2001-07-17 9:02 ` PATCH: " Sven Wischnowsky
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='004f01c10607$02c00180$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=zsh-workers@sunsite.dk \
/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).