Summary
Cycling through search results can be time-consuming when the set of results is large. This is especially problematic in terse codebases where the text is so vast and sprawling that the LSP and indexers struggle to link references to their definitions. A user would have to manually navigate to a symbol as opposed to using the native Go To Definition (F12) methods or similar.
With this change, the user would have a better line of sight to the target symbol no matter how large the file is and no matter how poorly the LSP is performing.
Feature Request
Add an input field to findWidget and others, and allow the user to type the desired match number and jump to it arbitrarily.
Implementation Details
See vscode PR
See xterm.js PR
Summary
Cycling through search results can be time-consuming when the set of results is large. This is especially problematic in terse codebases where the text is so vast and sprawling that the LSP and indexers struggle to link references to their definitions. A user would have to manually navigate to a symbol as opposed to using the native
Go To Definition (F12)methods or similar.With this change, the user would have a better line of sight to the target symbol no matter how large the file is and no matter how poorly the LSP is performing.
Feature Request
Add an input field to
findWidgetand others, and allow the user to type the desired match number and jump to it arbitrarily.Implementation Details
See vscode PR
See xterm.js PR