microsoft / microsoft/vscode-atom-keybindings
GoToDefinition stop working when upgrading to vscode 17.4.1 (or 17.4.2) on MAC
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 150
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I just updated my vscode to the latest version and I lost the ability to go to definition (cmd + click) when Atom Keybinding is activated.
Do you know what could cause this issue?
Thank you
Here is my config :
Version : 1.74.2
Validation : e8a3071ea4344d9d48ef8a4df2c097372b0c5161
Date : 2022-12-20T10:26:09.430Z
Electron : 19.1.8
Chromium : 102.0.5005.167
Node.js : 16.14.2
V8 : 10.2.154.15-electron.0
Système d’exploitation : Darwin x64 21.6.0
Sandboxé : No
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with Atom Keybinding activated in VS Code 1.74.1 or 1.74.2 on macOS, using the reported configuration and cmd-click on a symbol. Trace the extension behavior around Go to Definition and compare it with Atom Keybinding disabled; done means cmd-click navigation works while the keybinding extension remains active.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100