-
-
Notifications
You must be signed in to change notification settings - Fork 168
"Do you wish to see all X Possibilities?" Bug #635
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
Comments
Sorry, I'm not able to reproduce that. Can you run the following and share the output? typeset -p COLUMNS LINES
curl -V
curl --help |
Output of first command:
Output of 2nd command:
Output of third command:
|
What output do you get when you answer |
|
Yeah alot of other commands also have the same issue, mainly if the available flags are plenty. |
@Thy-GoD Weird, I have completely different completions for
|
@l4kr What does |
@Thy-GoD Ah, now I see: |
Interesting, this issue occurs in other commands as well, I'm guessing this is because there's a conflict between the two completion functions? |
This is what I typically use when I open the terminal. I resize the terminal all the time tho... For the git: Details
On MacOS it doesn't show any prompt at all until I type in something that can be shown ( |
@Thy-GoD No, that's not the reason. The reason is that Zsh's own completion function for |
Ah got it, I've tested on my end and the fix works, |
Originally posted as a question but was told to make a bug report instead.
This screenshot sums up the problem:
This prompt will sometimes occur mid-typing and basically force me to backspace and re-type the whole thing.
It will sometimes occur for longer commands as well, though I can't remember a case off memory.
Main way to reproduce is to type in
curl -
and it should show up.Environment
Steps to reproduce
Contents of
~autocomplete-log/2023-8-22.log
(click to expand)This is a repost of an issue thread where I didn't put the format.
I might've missed out something in this template but i tried my best to fill it as much as possible.
The text was updated successfully, but these errors were encountered: