zsh-users/zsh-history-substring-search sits at 3.1k stars on GitHub, written primarily in Shell. 🐠 ZSH port of Fish history search (up arrow)
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
This is a clean-room implementation of the Fish shell's history search
feature, where you can type in any part of any command from history and then
press chosen keys, such as the UP and DOWN arrows, to cycle through matches.
Bind keyboard shortcuts to this script's functions.
Users typically bind their UP and DOWN arrow keys to this script, thus:
Run cat -v in your favorite terminal emulator to observe key codes.
(NOTE: In some cases, cat -v shows the wrong key codes. If the
key codes shown by cat -v don't work for you, press <C-v><UP> and
<C-v><DOWN> at your ZSH command line prompt for correct key codes.)
Press the UP arrow key and observe what is printed in your terminal.
Press the DOWN arrow key and observe what is printed in your terminal.
Press the Control and C keys simultaneously to terminate the cat -v.
Use your observations from the previous steps to create key bindings.
For example, if you observed ^[[A for UP and ^[[B for DOWN, then:
Users have also observed that [OA and [OB are correct values,
even if these were not the observed values. If you are having trouble
with the observed values, give these a try.
You might also want to bind the Control-P/N keys for use in EMACS mode:
Press the history-substring-search-up key, which was configured in
step 2 above, to select the nearest command that (1) contains your query
and (2) is also older than the current command in your command history.
Press the history-substring-search-down key, which was configured in
step 2 above, to select the nearest command that (1) contains your query
and (2) is also newer than the current command in your command history.
Press ^U the Control and U keys simultaneously to abort the search.
If a matching command spans more than one line of text, press the LEFT
arrow key to move the cursor away from the end of the command, and then:
Press the history-substring-search-up key, which was configured in
step 2 above, to move the cursor to the line above the cursored line.
When the cursor reaches the first line of the command, pressing the
history-substring-search-up key again will cause this script to
perform another search.
Press the history-substring-search-down key, which was configured in
step 2 above, to move the cursor to the line below the cursored line.
When the cursor reaches the last line of the command, pressing the
history-substring-search-down key, which was configured in step 2
above, again will cause this script to perform another search.
Configuration
This script defines the following global variables. You may override their
default values.
HISTORY_SUBSTRING_SEARCH_HIGHLIGHT_FOUND is a global variable that defines
how the query should be highlighted inside a matching command. Its default
value causes this script to highlight using bold, white text on a magenta
background. See the "Character Highlighting" section in the zshzle(1) man
page to learn about the kinds of values you may assign to this variable.
HISTORY_SUBSTRING_SEARCH_HIGHLIGHT_NOT_FOUND is a global variable that
defines how the query should be highlighted when no commands in the
history match it. Its default value causes this script to highlight using
bold, white text on a red background. See the "Character Highlighting"
section in the zshzle(1) man page to learn about the kinds of values you
may assign to this variable.
HISTORY_SUBSTRING_SEARCH_GLOBBING_FLAGS is a global variable that defines
how the command history will be searched for your query. Its default value
causes this script to perform a case-insensitive search. See the "Globbing
Flags" section in the zshexpn(1) man page to learn about the kinds of
values you may assign to this variable.
HISTORY_SUBSTRING_SEARCH_FUZZY is a global variable that defines
how the command history will be searched for your query. If set to a non-empty
value, causes this script to perform a fuzzy search by words, matching in
given order e.g. ab c will match *ab*c*
HISTORY_SUBSTRING_SEARCH_PREFIXED is a global variable that defines how
the command history will be searched for your query. If set to a non-empty
value, your query will be matched against the start of each history entry.
For example, if this variable is empty, ls will match ls -l and echo ls; if it is non-empty, ls will only match ls -l.
HISTORY_SUBSTRING_SEARCH_ENSURE_UNIQUE is a global variable that defines
whether all search results returned are unique. If set to a non-empty
value, then only unique search results are presented. This behaviour is off
by default. An alternative way to ensure that search results are unique is
to use setopt HIST_IGNORE_ALL_DUPS. If this configuration variable is off
and setopt HIST_IGNORE_ALL_DUPS is unset, then setopt HIST_FIND_NO_DUPS
is still respected and it makes this script skip duplicate adjacent search
results as you cycle through them, but this does not guarantee that search
results are unique: if your search results were "Dog", "Dog", "HotDog",
"Dog", then cycling them gives "Dog", "HotDog", "Dog". Notice that the "Dog"
search result appeared twice as you cycled through them. If you wish to
receive globally unique search results only once, then use this
configuration variable, or use setopt HIST_IGNORE_ALL_DUPS.
HISTORY_SUBSTRING_SEARCH_HIGHLIGHT_TIMEOUT is a global variable that
defines a timeout in seconds for clearing the search highlight.
History
September 2009: Peter Stephenson originally wrote this script and it
published to the zsh-users mailing list.
January 2011: Guido van Steen (@guidovansteen) revised this script and
released it under the 3-clause BSD license as part of fizsh, the
Friendly Interactive ZSHell.
January 2011: Suraj N. Kurapati (@sunaku) extracted this script from
fizsh 1.0.1, refactored it heavily, and finally repackaged it as an
oh-my-zsh plugin and as an independently loadable ZSH script.
July 2011: Guido van Steen, Suraj N. Kurapati, and Sorin Ionescu
(@sorin-ionescu) further developed it with Vincent Guerci (@vguerci).
March 2016: Geza Lore (@gezalore) greatly refactored it in pull request #55.
How active is development on zsh-users/zsh-history-substring-search?
The most recent commit recorded on zsh-users/zsh-history-substring-search was 1 month ago, based on the GitHub push timestamp. The repository has 173 forks — one of the better signals of community interest.
How many stars does zsh-users/zsh-history-substring-search have?
zsh-users/zsh-history-substring-search has 3.1k GitHub stars — refresh the page for the live number, or check github.com/zsh-users/zsh-history-substring-search. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What is zsh-users/zsh-history-substring-search?
zsh-users/zsh-history-substring-search (zsh-users/zsh-history-substring-search) is a Shell project on GitHub. From the project's own README: 🐠 ZSH port of Fish history search (up arrow)
What language is zsh-users/zsh-history-substring-search written in?
zsh-users/zsh-history-substring-search is written primarily in Shell. GitHub's language field is based on the largest share of bytes in the default branch.
What topics is zsh-users/zsh-history-substring-search associated with?
GitHub's repository topics for zsh-users/zsh-history-substring-search: "command-history", "fish-shell", "history-search", "zsh-plugins". TopGit's editorial category is open-source.
Read full README in the tab above.
Curious whether zsh-history-substring-search is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about zsh-history-substring-search.