From: Johan Grande <nahoj@crans.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: [bug] Completion functions _files/_path_files -F filter on escaped file names
Date: Sat, 24 Jun 2023 21:55:16 +0200 [thread overview]
Message-ID: <c1145f4b-2569-6a80-e6e1-222c706739b0@crans.org> (raw)
In-Reply-To: <CAH+w=7Z4Ud0RxmzAaF6YZusxTVbSVD_feQiw8DT+Y3ERYTx_aw@mail.gmail.com>
Le 22/06/2023 à 05:54, Bart Schaefer a écrit :
> On Wed, Jun 21, 2023 at 12:29 PM Johan Grande <nahoj@crans.org> wrote:
>> Do you think that this behavior could be fixed?
>
> We could try this. However, it's not backward-compatible for people
> who are already quoting spaces etc. for _files -F patterns.
After looking at your suggestion and other, existing completions such as
_git, I get the impression that I shouldn't use _files but rather mimic
its basic behavior with _multi_parts and have more flexibility in
filtering matches. I assume I'll lose some perks of _files but it'll
hopefully fit my needs.
If you have any tips or a good example to study, I'll be grateful.
What I'll be aiming to do is:
- complete will all files under a path filtered with a regex or an
arbitrary command
- contrary to _git, I won't have a root dir so if I'm working in a
directory with >10k files under it, I might want to suggest only
immediate children in the first instance rather than browse everything
at once.
Thanks
--
Johan
next prev parent reply other threads:[~2023-06-24 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 19:29 Johan Grande
2023-06-22 3:54 ` Bart Schaefer
2023-06-24 19:55 ` Johan Grande [this message]
2023-07-20 5:15 ` Bart Schaefer
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=c1145f4b-2569-6a80-e6e1-222c706739b0@crans.org \
--to=nahoj@crans.org \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/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).