Diff syntax highlighting in Visual Studio Code? - visual-studio-code

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

Related

Julia Plot Pane

VSCode used to create plots from Plots.jl in Julia into a separate pane. For some reason it now plots in the same pane as the editor and covers the code making it difficult to tie the code and the graph together. What setting did I inadvertently change (I didn't think I changed any of them honestly) that results in the change of VS Code's behavior?
Tried the #antonio Parrella 's suggestion but it still doesn't work. Julia on VS Code is still opening a separate pane for the plot that covers the editor rather than displaying it side by side with the editor.
Example of code :
using Plots, Random
plot(1:5, rand(5))
Julia VS Code Version:
Version: 1.63.2 (user setup)
Commit: 899d46d82c4c95423fb7e10e68eba52050e30ba3
Date: 2021-12-15T09:40:02.816Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.22000
Settings(Ctrl + ,) > Workbench > Editor: Reveal If Open.
Then tick the box. Vscode turned this off by defult in the new update.

Vscode - How using %APPDATA% in settings.json?

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.

VSCode: 3 dots popping up and disappearing in editor

I have VSCode installed with
Version: 1.52.0-insider (user setup)
Commit: 0a80aacc7be1ab03ec0f94b8ac1a84949a83f35d
Date: 2020-11-26T07:36:22.965Z
Electron: 11.0.2
Chrome: 87.0.4280.63
Node.js: 12.18.3
V8: 8.7.220.24-electron.0
OS: Windows_NT x64 10.0.19042
I also installed C/C++ for Visual Studio Code 1.1.2.
Then created some hpp file.
Also when hitting enter on some random line, 3 dots appear on some strange empty lines.
After 2 seconds these dots and lines disappear again.
This makes working in the editor really hard when lines come and go.
Here is a screenshot:
Any idea how to disable these popping up dots?
This was happening to me because of the GitLens extension. I uninstalled it and now the issue is gone. It seems they have open issues for this issue but they are not addressed (as of today)
https://github.com/microsoft/vscode/issues/111472
https://github.com/gitkraken/vscode-gitlens/issues/1312

VS Code: select file, press delete - instead of deleting file it tries to regex-find file called 'Delete'

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

How to enable Reference Search View extension

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 :)