Repository navigation
Conversation
- Inputs confirmed with <cr> are saved to the `input_history` file under the coc data home (100 entries, newest first, deduplicated on recall). - <up>/<down> navigate the history in plain input dialogs and restore the text typed before navigation when moving past the newest entry. - QuickPick (list) mode is unchanged: <up>/<down> still navigate the list. - Vim8 reuses the existing PromptKeyPress channel of the prompt terminal; Neovim maps <up>/<down> to PromptKeyPress when the input window is not a list. Co-Authored-By: Claude Code <noreply@anthropic.com>
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #5775 +/- ##
==========================================
- Coverage 98.15% 98.14% -0.01%
==========================================
Files 306 306
Lines 53074 53123 +49
Branches 9366 9380 +14
==========================================
+ Hits 52094 52138 +44
- Misses 847 852 +5
Partials 133 133 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Plain input dialogs (e.g.
workspace.rename,requestInput) now keep apersistent input history, like Vim's built-in
input()history:<cr>are saved to theinput_historyfileunder the coc data home (
~/.config/coc/input_historyby default),reusing the existing
Mruclass (same storage as the commandshistory): newest first, deduplicated on recall, capped at 100 entries.
Cancelled (
<esc>) and single-character inputs are not saved.<up>recalls the previous accepted input,<down>moves to the morerecent one; moving past the newest entry restores the text typed
before navigation. The cursor is clamped at both ends (no wrap).
Behavior notes:
<up>/<down>previously movedthe cursor within the single line; they now navigate the history.
C-p/C-nare deliberately not bound to avoid conflicting withinsert-mode completion.
<up>/<down>still navigatethe filtered list; the history is only recalled in plain input
dialogs.
bin/prompt.jsalreadyforwards
<up>/<down>through the existingPromptKeyPresschannel, previously only consumed by QuickPick. The recalled value is
rendered through the existing programmatic value update
(
coc#dialog#change_input_value).Tested on both lanes (
node scripts/test/cli.mjs): history navigationand persistence on Neovim, QuickPick list navigation regression, and
Vim8 recall incl. confirming a recalled entry with a placeholder
active.
🤖 Generated with Claude Code