-
Notifications
You must be signed in to change notification settings - Fork 156
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
Add: search prefix only #115
Conversation
I just checked this and it works perfectly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this PR. Please see my comments in the code review. I think we can simplify this feature's implementation further.
@@ -48,6 +48,7 @@ typeset -g HISTORY_SUBSTRING_SEARCH_HIGHLIGHT_NOT_FOUND='bg=red,fg=white,bold' | |||
typeset -g HISTORY_SUBSTRING_SEARCH_GLOBBING_FLAGS='i' | |||
typeset -g HISTORY_SUBSTRING_SEARCH_ENSURE_UNIQUE='' | |||
typeset -g HISTORY_SUBSTRING_SEARCH_FUZZY='' | |||
typeset -g HISTORY_SUBSTRING_SEARCH_PREFIX='' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use true
/false
values for boolean feature flags rather than non/empty strings?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that all the other flags are using the non/empty pattern. I don't think it's good to introduce inconsistency.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, thanks for checking this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code looks good now, thanks! Could you please also add some documentation for this new variable in the Configuration section of the README? After this, we can merge the PR. Thanks.
Documentation added. |
NOTE: I have since renamed the configuration variable, in commit 4abed97:
|
Close #112