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

a code definition window like visual studio #10130

Closed
Shaka0723 opened this issue Nov 10, 2022 · 5 comments
Closed

a code definition window like visual studio #10130

Shaka0723 opened this issue Nov 10, 2022 · 5 comments
Labels
external Feature Request Visual Studio Code Caused by (or depends on changes from) VS Code

Comments

@Shaka0723
Copy link

Feature Request

Hi
Can your team add a code definition window like visual studio already has.
image

I know there is already a peek window in vscode, but it is not enough, for :

  1. it needs ctrl+click to call peek window
  2. peek window can not be seen when user scroll screen up or down

what I am expecting is :

  1. the definition window shows the symbol definition automatically when I put the cursor to the symbol (like visual studio)
  2. the definition window is a independent window but not build-in control in the editor (like visual studio)
  3. when I scroll down and up in the definition window, I can see the other part of codes in the file where the symbol defined.(like visual studio)
  4. when I double-click anywhere in the definition window, a new editor opened to the 2nd editor group, to show the file where I clicked
  5. when I click other symbol in the definition window, then window jumps to the new clicked symbol's defined location
@browntarik browntarik self-assigned this Nov 10, 2022
@browntarik
Copy link
Contributor

Thank you for suggesting this feature. This may be something that more languages could benefit from as well. This suggestion would be better poised toward the VS Code Team rather than the extension. Suggesting it to the VS Code Team will be a better fit since they are more suited to implement it.

@browntarik browntarik added Feature Request Visual Studio Code Caused by (or depends on changes from) VS Code labels Nov 10, 2022
@bobbrow
Copy link
Member

bobbrow commented Nov 16, 2022

@isidorn, Is this feature something the VS Code team would consider doing? We don't have permission to transfer issues to your repo, but we can copy it over if you'd like.

@Shaka0723
Copy link
Author

@isidorn, Is this feature something the VS Code team would consider doing? We don't have permission to transfer issues to your repo, but we can copy it over if you'd like.
I raised the issue to VSCode team yesterday.
Thanks all the same.

@isidorn
Copy link

isidorn commented Nov 16, 2022

@bobbrow thanks for the ping. I do not think this is something we would want to have in VS Code out of the box.
Though I think it would be best to follow the development in this issue microsoft/vscode#166340 that @Shaka0723 created

@sean-mcmanus
Copy link
Collaborator

Sure, we'll close this issue then.

@sean-mcmanus sean-mcmanus closed this as not planned Won't fix, can't repro, duplicate, stale Nov 17, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Jan 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
external Feature Request Visual Studio Code Caused by (or depends on changes from) VS Code
Projects
None yet
Development

No branches or pull requests

5 participants