-
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
[#148] command being typed as neither green nor red #244
base: master
Are you sure you want to change the base?
[#148] command being typed as neither green nor red #244
Conversation
290e1a5
to
155dc21
Compare
…ommand word. Adds the 'command-being-input' highlight. Builds on top of the 'command-word-separator-v1' branch from PR zsh-users#243.
155dc21
to
e13c86d
Compare
Perhaps this should use |
(Closing/reopening to trigger continuous integration) |
Can this use |
I still think a |
Thanks for the ping. Milestoning: small change, but destabilizing, so 0.8.0. (0.7.0 is closed for destabilizing changes.) |
Related to #148: this patch adds a highlight style for the command word, while it is being typed (similar to
path_prefix
).The style used is yellow underline, the same style the now-removed
path_approx
used.The intention is to avoid the unknown-token style whilst inputting the command. Future changes may fine tune this further (as discussed in #148), for example, only use the new style when the input-so-far is a prefix of a command or function name.