nvimdev / nvimdev/lspsaga.nvim

Resume/Repeat last Finder action

Open
#1,544 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Lua
Stars
3.8k
Forks
308
PR merge metrics
No merged PRs in 30d

Description

Is your feature request related to a problem? Please describe.
Sometimes I need to find all references or implementations of something and make changes there.
The workflow is

  1. Find references
  2. Search relevant reference entry
  3. Jump
  4. Edit
  5. Repeat until done

However, after jumping, the Finder closes and I need to get back to some reference location to run another reference search.

Describe the solution you'd like
It would be useful to have a way to resume or repeat the last Finder action so you can continue where you left off.

Describe alternatives you've considered
My current alternative is to call :lua vim.lsp.buf.references() to retrieve all entries in the location list which persists accross jumps.
However, it is not as nice as the Finder.

I'm also aware that you can shuttle to the Finder preview and make changes there, but for larger scale changes it feels better to jump to the source directly.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the Finder workflow described in the issue and compare it with the existing :lua vim.lsp.buf.references() behavior and its persistent location list. Define how resuming or repeating the last Finder action should work after a jump, then verify that the Finder remains usable across repeated reference searches and edits.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua, neovim
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.