From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Cygwin path completion
Date: Fri, 16 Jun 2000 17:01:38 +0200 (MET DST) [thread overview]
Message-ID: <200006161501.RAA14752@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Peter Stephenson's message of Fri, 16 Jun 2000 15:57:56 +0100
Peter Stephenson wrote:
> > I meant something different. I'd prefer if
> > /c/d/t would still complete to /cygdrive/d/temp. I meant, that
> > _path_files (BTW I agree that it already deserves to be converted to
> > shell code. It may even give old compctl the ability to complete paths)
> > should simply stuff cygdrive as first component. In the above case the
> > possible completions would consist of
>
> This is far too specific to be hard-wired into _path_files, but maybe
> there's some way of specifying transformations. I still don't understand
> how that helps you since I don't see when you want cygdrive to be the first
> component. It seems to me you should be using a named directory or
> something, e.g.
>
> c=/cygdrive
> : ~c
> echo ~c/d/...
>
> You can hardly get fewer characters than that.
Right.
I forgot to say... the fake-path thing I just suggested could also
help us to do something I've been missing some time ago (and then
forgot again, of course, sigh): completion of auto-mounted directories.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-06-16 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-16 15:01 Sven Wischnowsky [this message]
2000-06-16 15:49 ` Andrej Borsenkow
-- strict thread matches above, loose matches on Subject: below --
2000-06-16 14:54 Sven Wischnowsky
2000-06-16 13:27 Andrej Borsenkow
2000-06-16 13:47 ` Peter Stephenson
2000-06-16 14:24 ` Andrej Borsenkow
2000-06-16 14:57 ` 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=200006161501.RAA14752@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.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).