Today in my colleague's vscode I saw that finding references opens in sidebar.
I searched the web and I understood that it's done by Reference Search View, an extension shipped by vscode but it's not working for me. How can I enable it?
Version: 1.30.2
Commit: 61122f88f0bf01e2ac16bdb9e1bc4571755f5bd8
Date: 2019-01-07T22:49:48.319Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
OS: Linux x64 4.15.0-43-generic
This is a built-in extensions. It is included in VS Code 1.30+ and is enabled by default. Search #builtin references in the extension view to make sure you have not accidentally disabled it.
To show references, run the References: Find all references command. This should open the references sidebar with the reference results
Fixed!
The issue was that I was using
"command": editor.action.referenceSearch.trigger"
instead of
"command": "references-view.find"
in my keybindings.
I'm actually pleased! because I can still have the old behaviour by using the first command :)
Related
I am getting this error when trying to open the settings.json files or access preferences in VSCode. The preferences pages are blank. I have examined the settings.json file by opening it from the regular Windows File Explorer and don't see anything obviously amiss with it. I didn't see anything on the web in other questions about it. I tried deleting the settings.json file and it reset it, but I don't think that fixed it and I lose all my settings. I tried adding them back in a few at a time, to track down a setting that might be causing it and updated the recommendations, but still getting the error. I'm not sure where the "defaultSettings.json" file is. Is this a bug or am I doing something wrong? Also, I noticed that I am not able to authorize some of the OAuth logins, but I'm not sure if that is a separate issue. When the browser redirects after logging in it displays a can't access page in the browser and doesn't respond in vscode. I'm not sure if there is a setting that is missing or what is causing it. I'm also using WSL2 and Docker containers.
Thanks!
Version: 1.59.0 (system setup)
Commit: 379476f0e13988d90fab105c5c19e7abc8b1dea8
Date: 2021-08-04T23:13:12.822Z
Electron: 13.1.7
Chrome: 91.0.4472.124
Node.js: 14.16.0
V8: 9.1.269.36-electron.0
OS: Windows_NT x64 10.0.22000
Installed the VSCode insider edition and installed all my packages there and things seem to work with that version. Unless someone has a better idea I'll just mark this closed. I'll just use that the insider edition for now and keep the other one as a backup.
edit - nov 2022 - I didn't need this anymore, I've switched to Linux & Docker, no more coding under Windows
Does someone knows how to refer to my APPDATA folder in my vscode settings.json file?
I'm trying to set the path to my php-cs-fixer like below so, on all my development computer, the path can be retrieved.
"php-cs-fixer.executablePathWindows": "$env:APPDATA/Composer/vendor/bin/php-cs-fixer.bat",
To be clear: $env:APPDATA seems to be unsupported.
I'm using the latest version of vscode.
Version: 1.52.1 (user setup)
Commit: ea3859d4ba2f3e577a159bc91e3074c5d85c0523
Date: 2020-12-16T16:34:46.910Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.19041
I tried this on VSCode Insiders 1.53, was able to set using ~:
{
"php-cs-fixer.executablePathWindows": "~\\AppData\\Roaming\\Composer\\vendor\\bin\\php-cs-fixer.bat"
}
Seems that the ~ is transformed to match C:\Users\[you].
I know for sure that ${env:APPDATA} works because I use it in the setting : "emmet.extensionsPath": "${env:APPDATA}\\Code\\User\\Emmet Settings",
Check this documentation section. Unfortunately, this issue complains that it is not supported in every settings and extensions. I strongly suggest that every one upvote this issue so we have better chance MS takes care of it.
The Visual Studio Code setting "files.autoSave": "onWindowChange" has stopped working for me. It has worked properly for me every day in the past year. (I'm wondering if it may possibly be related to either my most recent update to Catalina or the most recent update to VS Code.) I have the files.autoSave setting only in this file: ~/Library/Application Support/Code/User/settings.json.
Does anyone have suggestions on how I can get the autosave feature in vscode working again?
Visual Studio Code 1.49.0
Commit: e790b931385d72cf5669fcefc51cdf65990efa5d
Date: 2020-09-10T17:39:53.251Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Darwin x64 19.6.0 - macOS Catalina 10.15.6
i personally don't like to use autosave on window change. I use "files.autoSave": "afterDelay" and set the delay files.autoSaveDelay": 500 here. Why I used this over the autosave window change is because it's much faster and automatically done every 500ms!
I was using Witch by Many Tricks, https://manytricks.com/witch/. After updating MacOs to Catalina 10.15.6, I believe that Which may have been interfering with VS Code ability receive window focus callbacks (I'm guessing). When I disabled Which, all is fine now. Thank you.
Is there an extension or setting, which makes a file with a .diff extension, opened in VS Code, display added lines in green and deleted lines in red? Currently, when I open a diff file, it displays added and deleted lines in the same color. I'm using VS Code Version: 1.37.1.
P.S. I tried the diff extension, but it doesn't work for me.
P.P.S. I tried reloading VS Code with extensions disabled and the highlighting is still broken:
I observed that .diff files are highlighted by default(without requiring any extensions), it's just that certain themes do not work well.
VS Code currently have this feature, if you get the .diff extension the sintax highlight performs correctly like git bash.
My VS Code is:
Version: 1.47.2 (system setup)
Commit: 17299e413d5590b14ab0340ea477cdd86ff13daf
Date: 2020-07-15T18:22:06.216Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 6.3.9600
In VS Code I select my file in the Explorer tab:
After I press Delete button, instead of deleting VSCode starts file search:
If I press delete multiple times it just keeps doing its thing:
It looks like a bug but maybe there is a secret shortcut to turn file search mode on/off that I don't know. Is there?
I'm on Ubuntu x64 with VSCode:
Version: 1.36.0
Commit: 0f3794b38477eea13fb47fbe15a42798e6129338
Date: 2019-07-03T13:20:56.241Z
Electron: 4.2.5
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Linux x64 4.18.0-25-generic
EDIT: please ignore my terrible terrible praxis of deleting spec files
Update:
Microsoft fixed it in last update
Original answer:
This is a known issue from last patch, it's going to be fixed in the next update.
Check this:
https://github.com/microsoft/vscode/issues/76514
Workaround:
https://github.com/microsoft/vscode/issues/76514#issuecomment-508841597