From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: _path_files and _cd with explicit glob pattern
Date: Fri, 19 Mar 1999 09:35:38 +0100 (MET) [thread overview]
Message-ID: <199903190835.JAA00723@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Thu, 18 Mar 1999 19:37:04 +0300
Andrej Borsenkow wrote:
> bor@itsrm2:/tools/src/zsh-3.1.5-pws-12/Completion%> zsh -f
> itsrm2% fpath=($PWD/${^~:-*(/)})
> itsrm2% source Core/compinit
> itsrm2% cdpath=(/tools/src)
> itsrm2% setopt globcomplete
> itsrm2% cd /tools
> itsrm2% l s/*3TAB
> itsrm2% l src/autoconf-2.13/
> autoconf-2.13/ samba-2.0.3/ tk8.0.3/ zsh-3.1.5-pws-12/
> mc-4.5.13/ sendmail-8.9.3/ top-3.4/
> ncftp-3.0beta18/ tcl8.0.3/ wget-1.5.3/
>
> In other words, all files with ``3'' in them are taken. And menu starts
> immediately.
That's because with `globcomplete', the code inserts a `*' at the
cursor position. I'm reluctant to change this (since that would be an
incompatible change), but I always was aware of the problem and the
patch for matching-cleanup I'm working on will allow one to say that
no `*' should be inserted -- this is also interesting to have when
using auto-correction (and somehow I got a mail from Peter replying to
a mail from Bart where this problem was mentioned).
> I think, if user explicitly gives glob pattern, he probably knows what he's
> doing. I noted this, when I tried to change to a directory; there were three
> dirs:
> SIN3C1 SIN3C2 SIN3C3 - and I wanted to select exactly one (the last) but got
> all three.
>
> And another problem with _cd (I think)
>
> itsrm2% cd s/*3TAB
> Beep
Is this still with the setting of `cdpath' you gave above? If so, this
is correct ;-)
> Ahem ... I'd expect it to complete to src/whatever
>
> itsrm2% cd *3TAB (they are all in /tools/src)
> itsrm2% cd autoconf-2.13
> autoconf-2.13 samba-2.0.3 tk8.0.3 zsh-3.1.5-pws-12
> mc-4.5.13 sendmail-8.9.3 top-3.4
> ncftp-3.0beta18 tcl8.0.3 wget-1.5.3
>
> I get the same names and menu starts immediately (that's due to _path_files
> I think) but they are not marked with slash (and no autoremoved slash
> either)
Hm, this should work, and it does for me.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-03-19 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-19 8:35 Sven Wischnowsky [this message]
1999-03-19 9:59 ` Andrej Borsenkow
1999-03-20 4:49 ` Geoff Wing
-- strict thread matches above, loose matches on Subject: below --
1999-03-18 16:37 Andrej Borsenkow
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=199903190835.JAA00723@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).