From: frederik@ofb.net
To: Peter Stephenson <p.stephenson@samsung.com>, zsh-users@zsh.org
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: completion autolist has time-sensitive interface
Date: Wed, 15 Aug 2018 08:57:00 -0700 [thread overview]
Message-ID: <20180815155700.GD30438@ofb.net> (raw)
In-Reply-To: <20180815083359eucas1p157426370c46cd6d59b96b8964f0445ce~LAcQObm1u2570325703eucas1p1b@eucas1p1.samsung.com>
I'm adding zsh-users at Peter's suggestion.
Thanks in advance.
On Wed, Aug 15, 2018 at 09:33:58AM +0100, Peter Stephenson wrote:
> On Tue, 14 Aug 2018 22:49:58 -0700
> <frederik@ofb.net> wrote:
>
> > Dear Zsh Hackers,
> >
> > Sometimes completion is so laggy on my system that when I press TAB
> > after e.g. "man perl", nothing seems to happen. So I press it again.
> > Still nothing happens. Completion seems broken.
> >
> > Took me a while to figure out the problem. It's related to "setopt
> > autolist" (which is on by default for me?).
> >
> > What happens is that if I just press TAB once, e.g. after "man perl",
> > there is a one-second delay and a prompt "zsh: do you wish to see all
> > 201 possibilities (51 lines)?". At this point I can press TAB again,
> > which is equivalent to "y" I guess, and I see a list of completions.
> >
> > 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) 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.
> > Usually everything I do on the terminal has the property that it
> > doesn't matter how fast or slow I type, it's only the order of the
> > keys that's important...
>
> One possibility would be if you had (presumably inadvertently) a
> key with TAB as a prefix. Then it would delay to see if you're
> going to type the full key stroke, and only execute the TAB binding
> if you didn't. It's not very likely, but it's the best I can think
> of.
>
> If you run
>
> bindkey | grep '\^I'
>
> you'll probably see something like
>
> "^I" complete-word
> "^[^I" self-insert-unmeta
>
> where the second isn't relevant as there's an ESC in front. If you
> see something else starting with ^I that's a problem.
>
> BTW this is probably more suitable for zsh-users where the larger
> audience is more likely to have seen something similar.
Thanks. When I run `bindkey | grep '\^I'` it shows me the same thing
that you see.
Maybe it will be hard for others to reproduce this as a slow computer
is needed. Or maybe if there were some way to run Zsh with input
provided programmatically, like `echo "man perl\t\t" | zsh`...
Frederick
next parent reply other threads:[~2018-08-15 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180815061554epcas3p4806e2cb2444ee67f4cb404ed2957a750@epcas3p4.samsung.com>
[not found] ` <20180815054958.GA27844@ofb.net>
[not found] ` <20180815083359eucas1p157426370c46cd6d59b96b8964f0445ce~LAcQObm1u2570325703eucas1p1b@eucas1p1.samsung.com>
2018-08-15 15:57 ` frederik [this message]
2018-08-15 17:54 ` Bart Schaefer
2018-08-16 1:45 ` frederik
2018-08-16 3:55 ` Eric Cook
2018-08-16 12:05 ` frederik
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=20180815155700.GD30438@ofb.net \
--to=frederik@ofb.net \
--cc=p.stephenson@samsung.com \
--cc=zsh-users@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).