From: Bart Schaefer <schaefer@brasslantern.com>
To: Oliver Kiddle <opk@zsh.org>
Cc: Marlon Richert <marlon.richert@gmail.com>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Why does _main_complete not try the next completer when $_comp_mesg is non-zero?
Date: Sun, 28 Mar 2021 18:22:13 -0700 [thread overview]
Message-ID: <CAH+w=7aY7+=DFH5XSDvk9hXRMaDU7cXLuCUjUav92EXMcdjZ2w@mail.gmail.com> (raw)
In-Reply-To: <74277-1616967738.353098@Tsys.Nn18.rMz7>
On Sun, Mar 28, 2021 at 2:42 PM Oliver Kiddle <opk@zsh.org> wrote:
>
> If you want to experiment with it, guarding the first _comp_mesg
> assignment in _message with [[ -n "$3" ]] && allows the format style to
> be set to the empty string to disable the setting.
I don't follow how the format style gets involved here?
Adding on to my previous partial dissection of _guard, it appears that
_main_complete does some messing about with compstate[insert] when
_comp_mesg is set which in a way which is contradictory to what
_message does with it: _main_complete sets it unconditionally to the
empty string, but _message only does so if the existing value contains
"unambiguous".
What am I missing?
next prev parent reply other threads:[~2021-03-29 1:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 16:33 Marlon Richert
2021-03-28 17:10 ` Mikael Magnusson
2021-03-28 17:27 ` Marlon Richert
2021-03-28 17:46 ` Bart Schaefer
2021-03-28 18:06 ` Marlon Richert
2021-03-28 20:51 ` Bart Schaefer
2021-03-28 21:42 ` Oliver Kiddle
2021-03-29 1:22 ` Bart Schaefer [this message]
2021-03-31 6:29 ` Marlon Richert
2021-03-31 9:25 ` Oliver Kiddle
2021-03-31 10:07 ` Marlon Richert
2021-03-31 23:20 ` Daniel Shahaf
2021-04-01 5:11 ` Marlon Richert
2021-04-01 17:08 ` Daniel Shahaf
2021-04-02 12:58 ` Marlon Richert
2021-04-03 3:12 ` Daniel Shahaf
2021-04-05 10:26 ` Marlon Richert
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=7aY7+=DFH5XSDvk9hXRMaDU7cXLuCUjUav92EXMcdjZ2w@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=marlon.richert@gmail.com \
--cc=opk@zsh.org \
--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).