zsh: populate search input with existing line contents when ^R is pressed?

up vote
2
down vote

favorite

Given .zshrc config:

bindkey -v
bindkey "^R" history-incremental-pattern-search-backward

When I type foo<^R>bar at an empty prompt, it searches for the most recent command matching bar.

How can I make ^R use the existing prompt input? I.e. with that key sequence I want to match foobar.

edited Nov 27 at 21:51

Gilles

524k12610471577

asked Nov 27 at 21:13

Plato

1133

add a comment |

up vote
2
down vote

favorite

Given .zshrc config:

bindkey -v
bindkey "^R" history-incremental-pattern-search-backward

When I type foo<^R>bar at an empty prompt, it searches for the most recent command matching bar.

How can I make ^R use the existing prompt input? I.e. with that key sequence I want to match foobar.

edited Nov 27 at 21:51

Gilles

524k12610471577

asked Nov 27 at 21:13

Plato

1133

add a comment |

up vote
2
down vote

favorite

Given .zshrc config:

bindkey -v
bindkey "^R" history-incremental-pattern-search-backward

When I type foo<^R>bar at an empty prompt, it searches for the most recent command matching bar.

How can I make ^R use the existing prompt input? I.e. with that key sequence I want to match foobar.

edited Nov 27 at 21:51

Gilles

524k12610471577

asked Nov 27 at 21:13

Plato

1133

Given .zshrc config:

bindkey -v
bindkey "^R" history-incremental-pattern-search-backward

When I type foo<^R>bar at an empty prompt, it searches for the most recent command matching bar.

How can I make ^R use the existing prompt input? I.e. with that key sequence I want to match foobar.

zsh command-history zle

edited Nov 27 at 21:51

Gilles

524k12610471577

asked Nov 27 at 21:13

Plato

1133

edited Nov 27 at 21:51

Gilles

524k12610471577

asked Nov 27 at 21:13

Plato

1133

edited Nov 27 at 21:51

Gilles

524k12610471577

edited Nov 27 at 21:51

Gilles

524k12610471577

edited Nov 27 at 21:51

Gilles

524k12610471577

asked Nov 27 at 21:13

Plato

1133

asked Nov 27 at 21:13

Plato

1133

asked Nov 27 at 21:13

Plato

1133

add a comment |

1 Answer
1

active

oldest

votes

up vote
2
down vote

accepted

If you bind ^R to history-beginning-search-backward, it comes close, but that's not a pattern search.

You can bind ^R to a function that adds the current content of the line as the initial search pattern.

history-incremental-pattern-search-backward-from-line () 
 zle history-incremental-pattern-search-backward $BUFFER

zle -N history-incremental-pattern-search-backward-from-line
bindkey -M viins "^R" history-incremental-pattern-search-backward-from-line
bindkey -M vicmd "^R" history-incremental-pattern-search-backward-from-line
bindkey -M isearch "^R" history-incremental-pattern-search-backward

(You need that binding to the isearch map because otherwise a repeated ^R would base its search on the line you've found so far, instead of repeating the current search.)

answered Nov 27 at 21:51

Gilles

524k12610471577

add a comment |

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f484521%2fzsh-populate-search-input-with-existing-line-contents-when-r-is-pressed%23new-answer', 'question_page');

);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

up vote
2
down vote

accepted

If you bind ^R to history-beginning-search-backward, it comes close, but that's not a pattern search.

You can bind ^R to a function that adds the current content of the line as the initial search pattern.

history-incremental-pattern-search-backward-from-line () 
 zle history-incremental-pattern-search-backward $BUFFER

zle -N history-incremental-pattern-search-backward-from-line
bindkey -M viins "^R" history-incremental-pattern-search-backward-from-line
bindkey -M vicmd "^R" history-incremental-pattern-search-backward-from-line
bindkey -M isearch "^R" history-incremental-pattern-search-backward

(You need that binding to the isearch map because otherwise a repeated ^R would base its search on the line you've found so far, instead of repeating the current search.)

answered Nov 27 at 21:51

Gilles

524k12610471577

add a comment |

up vote
2
down vote

accepted

If you bind ^R to history-beginning-search-backward, it comes close, but that's not a pattern search.

You can bind ^R to a function that adds the current content of the line as the initial search pattern.

history-incremental-pattern-search-backward-from-line () 
 zle history-incremental-pattern-search-backward $BUFFER

zle -N history-incremental-pattern-search-backward-from-line
bindkey -M viins "^R" history-incremental-pattern-search-backward-from-line
bindkey -M vicmd "^R" history-incremental-pattern-search-backward-from-line
bindkey -M isearch "^R" history-incremental-pattern-search-backward

(You need that binding to the isearch map because otherwise a repeated ^R would base its search on the line you've found so far, instead of repeating the current search.)

answered Nov 27 at 21:51

Gilles

524k12610471577

add a comment |

up vote
2
down vote

accepted

If you bind ^R to history-beginning-search-backward, it comes close, but that's not a pattern search.

You can bind ^R to a function that adds the current content of the line as the initial search pattern.

history-incremental-pattern-search-backward-from-line () 
 zle history-incremental-pattern-search-backward $BUFFER

zle -N history-incremental-pattern-search-backward-from-line
bindkey -M viins "^R" history-incremental-pattern-search-backward-from-line
bindkey -M vicmd "^R" history-incremental-pattern-search-backward-from-line
bindkey -M isearch "^R" history-incremental-pattern-search-backward

(You need that binding to the isearch map because otherwise a repeated ^R would base its search on the line you've found so far, instead of repeating the current search.)

answered Nov 27 at 21:51

Gilles

524k12610471577

If you bind ^R to history-beginning-search-backward, it comes close, but that's not a pattern search.

You can bind ^R to a function that adds the current content of the line as the initial search pattern.

history-incremental-pattern-search-backward-from-line () 
 zle history-incremental-pattern-search-backward $BUFFER

zle -N history-incremental-pattern-search-backward-from-line
bindkey -M viins "^R" history-incremental-pattern-search-backward-from-line
bindkey -M vicmd "^R" history-incremental-pattern-search-backward-from-line
bindkey -M isearch "^R" history-incremental-pattern-search-backward

(You need that binding to the isearch map because otherwise a repeated ^R would base its search on the line you've found so far, instead of repeating the current search.)

answered Nov 27 at 21:51

Gilles

524k12610471577

answered Nov 27 at 21:51

Gilles

524k12610471577

answered Nov 27 at 21:51

Gilles

524k12610471577

answered Nov 27 at 21:51

Gilles

524k12610471577

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Unix & Linux Stack Exchange!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

Some of your past answers have not been well-received, and you're in danger of being blocked from answering.

Please pay close attention to the following guidance:

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

搜尋此網誌

mjhjmtu