From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Matching against file suffix
Date: Thu, 9 Mar 2000 13:42:39 +0100 (MET) [thread overview]
Message-ID: <200003091242.NAA25899@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Thu, 9 Mar 2000 13:36:33 +0300
Andrej Borsenkow wrote:
> So far, the two major uses I had for globbing were:
>
> 1. patch < /.../zsh/patches/<1234->TAB
>
> This is nice for manually applying patches; I save them with article number and simply get
> the next by incrementing number and hitting TAB
>
> 2. foo .../zsh/Doc/*.texi
>
> That is the case, when I do know file suffix and want to get just this one file.
> Unfortunately, as was oft seen, this has problems with _path_files - and, Sven, you once
> wrote, that you do not use globbing at all but use spiffy match controls instead.
>
> Is it possible to match by file suffix with matching control? It is 'course possible by
> moving cursor before suffix - but that I'd like to avoid. The idea is to hit TAB at the
> end of input word and still get completion.
The simple 'r:|.=* r:|=*' works for me, i.e. `foo .../.texi<TAB>'
gives me the *.texi files.
Btw, I have the _match completer in my completer style, but only after
all the matcher-list specs have been tried (which include the one
above and the substring-matcher `l:|=* r:|=*').
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-03-09 12:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-09 12:42 Sven Wischnowsky [this message]
2000-03-09 13:41 ` Andrej Borsenkow
-- strict thread matches above, loose matches on Subject: below --
2000-03-13 10:13 Sven Wischnowsky
2000-03-10 10:27 Sven Wischnowsky
2000-03-10 11:04 ` Andrej Borsenkow
2000-03-09 15:07 Sven Wischnowsky
2000-03-10 9:57 ` 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=200003091242.NAA25899@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).