zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
	<zsh-workers@sunsite.auc.dk>
Subject: RE: Cygwin path completion
Date: Fri, 16 Jun 2000 19:49:23 +0400	[thread overview]
Message-ID: <000901bfd7aa$713823e0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <200006161501.RAA14752@beta.informatik.hu-berlin.de>

> >
> > 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.
>
>

The point is not how many characters I type (but wiht Zsh I tend to use
less :-) The point is: I expect zsh to complete /c/d/t to a valid path
(all possibly valid paths) that match this string. And /cygdrive/d/temp
is valid path in my case. It is the same, as if Zsh simply always
skipped one directory.

Small explanation to Sven:

To access other drives under Cygwin I need either to

- mount each drive explicitly somewhere under root
or
- simply use /cygdrive that gives you "single filesystem tree" image

For this reason I really wish Zsh could assist here.

-andrej


  reply	other threads:[~2000-06-16 15:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-16 15:01 Sven Wischnowsky
2000-06-16 15:49 ` Andrej Borsenkow [this message]
  -- 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='000901bfd7aa$713823e0$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=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).