Zsh Mailing List Archive
Messages sorted by:
Re: cd /u/N/v/ tab expansion
On Sun, Apr 17, 2022 at 9:17 AM Tomasz Pala <gotar@xxxxxxxxxx> wrote:
> On Sat, Apr 16, 2022 at 20:00:18 -0700, Bart Schaefer wrote:
> > I don't seem to be able to re-create the setup for your "ctrl-g
> > toggling of behaviour" incident. Can you specify?
> Sure, minimal config that exposes this "state-leaking":
> setopt glob_complete
This is the trigger again, the other settings just make it possible to
see the difference. I'm again suspicious of menu=yes being forced on
by _path_files for globcomplete.
On the first tab, menu completion is entered. When you hit ctrl+g,
you exit menu completion, but do not exit/restart the ZLE editor.
That leaves $_lastcomp initialized, so when you hit tab again,
_main_complete line 83 sees that the word on the line has not changed
and therefore deliberately re-enters completion with the state from
the previous attempt. Even though the command line shows the cursor
at the end of the word, the unambiguous_cursor position is used, which
splits the word into SUFFIX=/g and PREFIX=a/b/d/e and the rest of the
behavior follows from that.
The next ctrl+g has the same effect -- leaves menu completion but
leaves $_lastcomp alone -- so the behavior isn't really "toggling".
What's different on the third (and fifth, etc.) tab presses is that
the last trial completion ("a/b/d/e /g" with space) is no longer the
same as the word on the line ("a/b/d/e/g"), so _main_complete behaves
as if you've started a whole new completion, which generates the same
menu as the first tab.
The important part here is that it is not wrong (in most cases) to
re-enter completion with the preserved state when the word on the line
has not changed, so resetting _lastcomp is not the answer.
One possible fix is this:
diff --git a/Completion/Base/Core/_main_complete b/Completion/Base/Core/_main_co
index 169ca1f40..4ab572894 100644
@@ -82,7 +82,8 @@ fi
if [[ "$compstate[pattern_match]" = "*" &&
"$_lastcomp[unambiguous]" = "$PREFIX" &&
- -n "$_lastcomp[unambiguous_cursor]" ]]; then
+ -n "$_lastcomp[unambiguous_cursor]" &&
+ "$CURSOR" -eq "$_lastcomp[unambiguous_cursor]" ]]; then
However, I'm concerned that will negatively affect behavior in other
circumstances, particularly when always_to_end is set or
complete_in_word is not set.
The question to be answered is whether Tomasz's expection that ctrl+g
will reset the state is correct, and if so, how to make that happen
when exiting menu completion that way.
Messages sorted by: