From: Bart Schaefer <schaefer@brasslantern.com>
To: Samy Dulor <samy.dulor@orange.fr>
Cc: zsh-workers@zsh.org
Subject: Re: [BUG] complist interactive mode overwrites command line
Date: Sun, 3 Mar 2024 18:05:27 -0800 [thread overview]
Message-ID: <CAH+w=7YF818QHb2FvorYbs+=83mW3V5pNKy0JYTLh9E5du3qvA@mail.gmail.com> (raw)
In-Reply-To: <90469bbe-acdf-6dad-baaa-fbf3d1e7ed6c@orange.fr>
On Sun, Mar 3, 2024 at 5:44 PM Samy Dulor <samy.dulor@orange.fr> wrote:
>
> So I just tried fixing it by correcting the values in minfo when domenuselect restores the command line content,
Yours may be the one combination I did not try, in the thread ending here:
https://www.zsh.org/mla/workers/2023/msg01041.html (workers/52312)
The real test is whether it handles this ...
>> Anything that resets the
>> appearance of the line -- such as hitting TAB again after accept-line,
>> because (as in the "user defined widget doesn't execute suffix
>> removal" thread), we are actually still in menu completion at that
>> point even though we've left interactive completion -- also loses
>> track of the fact that the original line is back the way it was, and
>> so minfo.len becomes wrong again and things like navigating the menu
>> with the arrow keys start foredel()-ing too much.
next prev parent reply other threads:[~2024-03-04 2:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 16:30 Marlon Richert
2024-03-04 1:44 ` Samy Dulor
2024-03-04 2:05 ` Bart Schaefer [this message]
2024-03-04 6:33 ` Bart Schaefer
2024-03-04 11:30 ` Samy Dulor
2024-03-04 22:38 ` Bart Schaefer
[not found] <8964126.CDJkKcVGEf.ref@phy-nordri>
2022-07-15 13:39 ` Andrea Manenti
2022-07-16 18:11 ` Bart Schaefer
2022-07-16 22:57 ` Bart Schaefer
[not found] ` <2844417.e9J7NaK4W3@phy-nordri>
2022-07-22 16:32 ` Bart Schaefer
2022-07-22 17:55 ` Bart Schaefer
2022-07-22 18:23 ` Bart Schaefer
2022-07-22 19:10 ` Andrea Manenti
2023-11-17 3:35 ` 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='CAH+w=7YF818QHb2FvorYbs+=83mW3V5pNKy0JYTLh9E5du3qvA@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=samy.dulor@orange.fr \
--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).