From: Bart Schaefer <schaefer@brasslantern.com>
To: Tomasz Pala <gotar@polanet.pl>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: cd /u/N/v/ tab expansion
Date: Sun, 17 Apr 2022 11:32:55 -0700 [thread overview]
Message-ID: <CAH+w=7bekAaUbbbKC+Uu_GRc5X3o80gNJmfTY6r349oipUFsaw@mail.gmail.com> (raw)
In-Reply-To: <20220417161727.GA31153@polanet.pl>
On Sun, Apr 17, 2022 at 9:17 AM Tomasz Pala <gotar@polanet.pl> wrote:
>
> On Sat, Apr 16, 2022 at 20:00:18 -0700, Bart Schaefer wrote:
>
> > So the results have been correctly completed and added, they're just
> > not in the tag group where they appear on the first attempt.
>
> This is why "-U" alone also "fixes" my case as far as I understand (?).
If I'm following correctly, that prevents the internal completion
matching from removing what it thinks are non-matching entries from
the tag group. That's why I'm a bit skeptical of unconditionally
passing -U, especially if the :gs change handles cases other than the
"state-leaking" (see previous response).
> This is far beyond my skills on completion flow tracking...
It's just running _complete_debug once with globcomplete off and again
with globcomplete on, and then diffing the trace files. Plus some
idea of which deltas are meaningful.
prev parent reply other threads:[~2022-04-17 18:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 12:40 zzapper
2022-04-07 20:11 ` Bart Schaefer
2022-04-07 20:20 ` zzapper
2022-04-07 23:11 ` Bart Schaefer
2022-04-08 9:53 ` zzapper
2022-04-08 17:57 ` Bart Schaefer
2022-04-08 10:22 ` david rayner
2022-04-08 18:09 ` Bart Schaefer
2022-04-10 1:04 ` Tomasz Pala
2022-04-10 14:32 ` Tomasz Pala
2022-04-10 16:27 ` Tomasz Pala
2022-04-10 16:32 ` Tomasz Pala
2022-04-10 17:45 ` Tomasz Pala
2022-04-10 18:05 ` Tomasz Pala
2022-04-16 14:17 ` Tomasz Pala
2022-04-17 3:00 ` Bart Schaefer
2022-04-17 16:17 ` Tomasz Pala
2022-04-17 18:15 ` Bart Schaefer
2022-04-17 18:44 ` Bart Schaefer
2022-04-17 18:32 ` Bart Schaefer [this message]
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='CAH+w=7bekAaUbbbKC+Uu_GRc5X3o80gNJmfTY6r349oipUFsaw@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=gotar@polanet.pl \
--cc=zsh-users@zsh.org \
--subject='Re: cd /u/N/v/ tab expansion' \
/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
Code repositories for project(s) associated with this 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).