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

Add goto next/prev reference match command #44414

Closed
jrieken opened this issue Feb 26, 2018 · 10 comments
Closed

Add goto next/prev reference match command #44414

jrieken opened this issue Feb 26, 2018 · 10 comments
Assignees
Labels
editor-symbols definitions, declarations, references feature-request Request for new features or functionality on-testplan release-notes Release notes issues
Milestone

Comments

@jrieken
Copy link
Member

jrieken commented Feb 26, 2018

Similar to F4 and search results

@jrieken jrieken self-assigned this Feb 26, 2018
@jrieken jrieken added editor-symbols definitions, declarations, references feature-request Request for new features or functionality labels Feb 26, 2018
@jrieken jrieken added this to the March 2018 milestone Feb 26, 2018
@steveluc
Copy link

👍 Would to be able to use F4 etc. to go to next/prev reference. Would love it if reference list would also scroll as necessary. Also great would be if you could dismiss reference list and peek, creating a mode in which going through references is like going through errors (and like errors, would be helpful to be able to re-display the list as needed).
Thanks!

@jrieken
Copy link
Member Author

jrieken commented Feb 28, 2018

Also great would be if you could dismiss reference list and peek,

@steveluc Interesting idea. When you say 'dismiss' to you mean dismiss as 'it's gone from the UI and it only stays in my head' or do mean something like 'gone from the editor but inside another panel (like search results)'?

@steveluc
Copy link

steveluc commented Feb 28, 2018 via email

@jrieken
Copy link
Member Author

jrieken commented Feb 28, 2018

Key scenario is a systematic change across multiple files and you need to edit at each reference and make sure you don’t miss any references.

I like that, I actually often want to work in that way. Challenge (and difference to errors) is how long we should keep the list of references? Until the next invocation of reference search? Or, similar to squiggles show "reference-markers" which you visit (and somehow can clear/reset)?

The goto commands should work across files

we track that here and I optimistically scheduled it for March: #14783

@steveluc
Copy link

steveluc commented Feb 28, 2018 via email

@jrieken
Copy link
Member Author

jrieken commented Mar 2, 2018

@roblourens I see that the find viewlet binds F4/Shift+F4 unconditional which makes it hard for another part to also use F4. Can you add a when-clause in the spirit of 'when having search results'? Today F4 simply reveals the find viewlet when not having results...

screen shot 2018-03-02 at 12 39 41

@roblourens
Copy link
Member

Sure. What do you expect when search results and references are both present?

@jrieken
Copy link
Member Author

jrieken commented Mar 8, 2018

One of them wins ;-) It's like having an editor selection, the editor-find-widget, and a peek widget and then pressing ESC. It will be statically spelled out using a priority

@roblourens
Copy link
Member

I added a context key hasSearchResults, and bound F4/shift+F4 to that. We could also only set it when the search view is visible, but F4 is still useful when it's hidden, so I left that out for now.

@jrieken
Copy link
Member Author

jrieken commented Mar 21, 2018

Closing this as we have F4/Shift-F4 in latest insiders. The continuation, esp. navigating references without peek view, is now tracked in #22261

@jrieken jrieken added the release-notes Release notes issues label Mar 28, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators May 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
editor-symbols definitions, declarations, references feature-request Request for new features or functionality on-testplan release-notes Release notes issues
Projects
None yet
Development

No branches or pull requests

3 participants