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

ctrl + click "go to definition" clashes with ctrl + click "follow link" #7591

Closed
AngusWR opened this issue Sep 25, 2019 · 2 comments
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@AngusWR
Copy link

AngusWR commented Sep 25, 2019

Environment data

  • VS Code version: Version: 1.38.1
  • Extension version (available under the Extensions sidebar): Version: 2019.9.34911
  • OS and version: Windows 10 Pro 1903 18362.356
  • Python version (& distribution if applicable, e.g. Anaconda): 3.6.7

Expected behaviour

ctrl + click on a string representation of a url opens the url in chrome

Actual behaviour

ctrl + click on a string representation of a url opens the url in chrome and also goes to the definition for str in builtins.pyi

Holding ctrl and hovering the url:

1

After clicking the url

2

I haven't been able to find a way of changing the key binding for the "go to definition" feature. Any advice?

@AngusWR AngusWR added triage-needed Needs assignment to the proper sub-team bug Issue identified by VS Code Team member as probable bug labels Sep 25, 2019
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Sep 26, 2019
@karrtikr
Copy link

For changing keybindings, go to File -> Preferences -> Keyboard shortcuts. Search for Go to definition.
Anyways, this is controlled by VSCode, not the extension. So I am transferring the issue.

@karrtikr
Copy link

Issue moved to microsoft/vscode #81520 via ZenHub

@ghost ghost removed the triage label Sep 26, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

3 participants