-
-
Notifications
You must be signed in to change notification settings - Fork 164
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
Figure out what the default completion UI should be #1078
Comments
A core issue is that we don't use GNU readline's tokenization, which is good. We use our own shell parser However it also means we can't use the default completion display, which knows about the TERMINAL WIDTH. So we have to write our own. If we disable the completion display hook (only using the candidate hook), then we get something like this, which is bad:
That is, the entire line is displayed. |
Maybe we can write a binding for this function and call it, so then the shell doesn't have to know about the width at all?
But the Ah it looks like we can do this:
|
TODO
Another idea.
|
Document known issue: completion on second line doesn't really work, I think because we're just parsing each line as is
Hm this is sort of bad though. Maybe it can be fixed. |
Hm might not need Because Python does a TODO: see how zsh and fish detect this condition in code. |
Fixed #257 with I think this means the zsh-like UI can be the deafult? I think the bash-like UI makes sense in case there are still some drawing problems, but I don't think it's a big priority right now. I think the |
I think we need to pick something "modest" which can be translated to C++. If we have color errors that might offset the lack of fanciness
Although there is also the issue that completion uses Python
yield
, which doesn't translate wellThe text was updated successfully, but these errors were encountered: