-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Syntax highlighting is not reset after "cd fo<tab><enter>" #310
Comments
I cannot reproduce this. Could you provide a self-contained reproduction recipe (starting from Does #288 fix this? Are you using latest master? Feel free to join #zsh-syntax-highlighting on freenode. |
#288 does not fix it. I've feared that it might be related to some custom settings/config. Would need to investigate further, but cannot at the moment. |
Sorry for the confusion, this happened because of my theme. I've started using It had the nice side effect of using a different style for (parts of) the already typed text after completion was triggered, which I've thought was a new feature after also upgrading z-sy-h at the same time.. :) |
We don't have a feature for highlighting the just-added-by-completion text differently, however, there are the I use |
After
cd fo<tab><enter>
, wherecd fo<tab>
displays multiple options with " -- directory in cdpath --" the syntax highlighting is not reset, and the "cd: no such file or directory: fo" is displayed in grey, just like / similar to the (new?) part that highlights the already typed text.This only happens after the first call to this in a new shell, afterwards it works.
But there are differences, e.g. with
cd b<tab><enter>
it seemed to be triggered always?!Hopefully this is enough to reproduce, otherwise I'd be happy to bisect and/or provide more information.
The text was updated successfully, but these errors were encountered: