Skip to content
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

Taking over change history #661

Open
alerque opened this issue Mar 28, 2021 · 2 comments
Open

Taking over change history #661

alerque opened this issue Mar 28, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@alerque
Copy link
Contributor

alerque commented Mar 28, 2021

  • OS: Arch Linux
  • (Neo)Vim version: 0.4.0
  • vim-clap version: current HEAD

Sometime since I last updated vim-plugins (up to a month perhaps?), the behavior of vim-clap has regressed.

A common workflow for me is to open a file, search for some next, make a change, then use vim-clap with a grep or files provider to load up another file with related content. My expectation is that I should be able to use n without further ado to find the next instance from my previous search, then . to repeat the fix.

At some point vim-clap has started registering things typed into the search (for example using the files provider) as an action in VIM's command history. Now when I get a new buffer open n works to find the next instance of my last search, but when I try to repeat the last action using . I get whatever fuzzy string I typed into the files provider inserted in my file.

@alerque alerque added the bug Something isn't working label Mar 28, 2021
@liuchengxu
Copy link
Owner

It can be helpful if you bisect the commit that introduces this change.

@alerque
Copy link
Contributor Author

alerque commented Mar 28, 2021

Yes, and if I did that I could probably fix it myself too. Trouble is I don't have the bandwidth today or in the next couple days. I may get to it eventually if nobody else does first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants