Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: completion autolist has time-sensitive interface
- X-seq: zsh-users 23585
- From: frederik@xxxxxxx
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: completion autolist has time-sensitive interface
- Date: Wed, 15 Aug 2018 18:45:13 -0700
- Cc: Zsh Users <zsh-users@xxxxxxx>
- In-reply-to: <CAH+w=7Z_swkvkJv97F0ULmzvZsDk-FZUSXNeSuV1bwa_Y44ofA@mail.gmail.com>
- List-help: <mailto:zsh-users-help@zsh.org>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:zsh-users@zsh.org>
- List-unsubscribe: <mailto:zsh-users-unsubscribe@zsh.org>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <CGME20180815061554epcas3p4806e2cb2444ee67f4cb404ed2957a750@epcas3p4.samsung.com> <20180815054958.GA27844@ofb.net> <20180815083359eucas1p157426370c46cd6d59b96b8964f0445ce~LAcQObm1u2570325703eucas1p1b@eucas1p1.samsung.com> <20180815155700.GD30438@ofb.net> <CAH+w=7Z_swkvkJv97F0ULmzvZsDk-FZUSXNeSuV1bwa_Y44ofA@mail.gmail.com>
- Reply-to: frederik@xxxxxxx
- Sender: <frederik@xxxxxxx>
Thanks Bart.
> The delay is almost certainly the time required to generate the 201
> possibilities rather than any "intentional" pause that zsh is doing.
Yeah I wasn't suggesting that, my goodness.
> Yes, at that particular prompt TAB and y/Y are equivalent, also ctrl-C
> and ctrl-D (eof) and n/N are equivalent.
>
> But there's more going on than that. Before displaying the prompt,
> zsh checks to see whether you have already typed something else
> (typeahead) and if you have, it assumes you decided to disambiguate
> the input further, so it skips printing the prompt and proceeds as if
> you had answered "n". So by pressing the second TAB while zsh is
> still working on the set of completion for the menu, you have told the
> shell you don't want to wait for the menu and it should simply
> proceed.
>
> > However, if I press TAB twice quickly in succession then I see no
> > list, it is exactly as if there are no completions at all. (Actually
> > if the prompt is at the bottom of the screen, I get a newline)
>
> The faster you press the two TABs, the more likely you are to trigger
> the typeahead detection.
>
> > I find
> > it confusing that the completion interface would be time-sensitive in
> > this manner. Why TAB-delay-TAB would behave differently from TAB-TAB.
>
> Back in the day, a lot of people would automatically muscle-memory
> whack the tab key after typing part of a word, realize they didn't
> mean to, and keep typing more of the word. They were annoyed when the
> shell ate part of their continued typing as the answer to the prompt,
> leaving them with a word with one missing letter in the middle, so the
> shell was changed to not do that. This is also why pressing a second
> TAB when the prompt does appear is treated as yes.
Interesting! I wonder if some workaround could be devised, either
showing a "..." to indicate that the shell is busy coming up with
completions, or not eating the typeahead when it consists of TABs.
There seems to be a lot of history here, anyway, thanks for explaining
what was going on.
By the way where do we control the number of completions which
triggers the "do you wish to see ..." prompt to appear?
Frederick
Messages sorted by:
Reverse Date,
Date,
Thread,
Author