From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: RE: Matching against file suffix
Date: Fri, 10 Mar 2000 11:27:05 +0100 (MET) [thread overview]
Message-ID: <200003101027.LAA03185@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Fri, 10 Mar 2000 12:57:46 +0300
Andrej Borsenkow wrote:
> > >
> > > That reminds me. Matcher-list is way too general - it applies to any completion in any
> > > context. And matcher is tried unconditionally, isn't it?
> >
> > I'm not sure what you mean by `unconditionally' -- I always consider
> > the context for which it is set to be a `condition'.
> >
>
> I mean, that if matcher style is set for a tag, it is always used. I have no way to
> emulate matcher-list with semantic "try each in turn until you get matches".
Yep, see 10027 where I tried to explain why I haven't implemented
it. Btw, if someone sees a way around the problems mentioned there,
I'd be interested to hear about it.
> One more (well, somewhat different) question. I tried to play with tag-order.
> Unfortunately, it has one nasty effect - you cannot reject current tag.
>
> With
>
> zstyle ':completion:*:complete:cd:*' tag-order local-directories path-direcories
>
> and
>
> ./foo1
> foo2 somewhere in $cdpath
>
> cd fTAB
>
> will never complete foo2.
>
> I think, it was discussed at least once, but may be in different context.
>
> The same is true for example in docs (gunzip). If no *.gz exists but you have a
> subdirectory, you will never get a chance to complete other file.
>
> Or did I miss something?
My first reaction was: yes. My second reaction: so what? ;-)
Maybe I'm too slow in the brain today, but... what exactly do you want
to say? You selected the order explicitly. If you want to see foo2,
you have to give the tag in one string (I guess you are aware of that
-- just making sure):
zstyle ':completion:*:complete:cd:*' tag-order 'local-directories path-direcories'
(note the quotes). With gunzip this is slightly different, because we
have a default for the order of globbed-files/directories/all-files.
Maybe you prefer:
zstyle ... tag-order globbed-files all-files
Or maybe you want to have a way to switch from one type of matches to
the `next'. That would be nice, yes. It's just that nobody didn't find
the time to write that yet -- maybe a bindable command, working a bit
like _complete_help, gathering possible tags and then selecting one of
them... (I haven't missed that yet, that's why I haven't tried to
write it).
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-03-10 10:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-10 10:27 Sven Wischnowsky [this message]
2000-03-10 11:04 ` Andrej Borsenkow
-- strict thread matches above, loose matches on Subject: below --
2000-03-13 10:13 Sven Wischnowsky
2000-03-09 15:07 Sven Wischnowsky
2000-03-10 9:57 ` Andrej Borsenkow
2000-03-09 12:42 Sven Wischnowsky
2000-03-09 13:41 ` Andrej Borsenkow
2000-03-09 10:36 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=200003101027.LAA03185@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).