Skip to content

Better defaults to avoid "do you wish to see all XXX possibilities" #791

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Floriferous opened this issue Mar 17, 2025 · 4 comments
Open

Comments

@Floriferous
Copy link

What do you want?

I recently started using this plugin, and I regularly hit "do you wish to see all XXX possibilities". It took me some time to actually understand why what I was typing was sometimes missing a letter:

Example of trying to type clear in my terminal:

# What I type on my keyboard
c -> do you wish to XX..
l -> eaten by the prompt
e -> 
a ->
r ->
enter -> command not found: cear

Now I'm looking through forums on how to potentially disable this "do you wish" thing, and honestly it's not even clear how to do it, so I ended up entirely removing this plugin.

I fail to understand how this is the default, expected, behavior, as it makes typing quickly impossible, because you will regularly have the 2nd character you type be ignored and swallowed by this interruption.

I would recommend to find a better default for this thing, as it makes the initial experience of this plugin terrible.

Maybe I didn't set it up right, or maybe I made another mistake somehow? Or maybe this issue is not related to this plugin?

@cybercussion
Copy link

cybercussion commented Apr 24, 2025

yeah just doing a git command right now soon as I hit "g" I get zsh: do you wish to see all 168 possibilities (16 lines)? and its eating my letters.

Autocomplete has become AutoEat. g··· ᗧ···I··t··ᗣ···ᗣ·· (wakka wakka wakka)

setopt interactivecomments seems to help.

@KevinFocke
Copy link

@cybercussion @Floriferous Does this help? Had to search a lot:

#654 (comment)

@j-a-h-i-r
Copy link

j-a-h-i-r commented May 9, 2025

Is this a recent development? I use zsh on my work mac which doesn't have this issue. But I face this issue in my personal mac.

Also if I type a characeter (e.g: 'n') in iterm it doesn't show me this message but if I type 'n' in vscode's integrated terminal it triggers this message

@cybercussion
Copy link

thanks @KevinFocke I'll give that a shot too, beats the hammer I used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants