I'm aware of the following question and answers:
Visual Studio: How to trigger an alarm when a breakpoint is hit?
However, none of the solutions seem to work for me. I'm on Windows 10, with Visual Studio Code 1.52.1. When I go to the Windows sound settings, there is no Visual Studio section, so I can't set it there. The "ding" extension is no longer supported. The macro option also does not seem possible in my version of VS.
Does anyone know of any alternative solutions? I'm running code that takes sometimes 30+ minutes, so I would really benefit from an audible alert so I can immediately get back to work when it completes.
In the Insiders Build v1.65 there a few new individual settings controlling audio and it appears that the general Audio Cues: Enabled has been removed in favor of the more specific settings.
audioCues.onDebugBreak: Plays a sound when the debugger stopped on a breakpoint.
audioCues.lineHasBreakpoint: "Plays a sound when the active line has a breakpoint."
audioCues.lineHasInlineSuggestion: "Plays a sound when the active line has an inline suggestion."
audioCues.lineHasError: "Plays a sound when the active line has an error."
audioCues.lineHasFoldedArea: "Plays a sound when the active line has a folded area that can be unfolded."
audioCues.lineHasWarning: "Plays a sound when the active line has a warning." (off by default)
And see https://stackoverflow.com/a/70988028/836330 for how to list, hear and modify these settings using the
Help: List Audio Cues command from the Command Palette.
This is in the Stable Build v1.64 now.
Setting: Audio Cues: Enabled
auto : default - Enable audio cues when a screen reader is attached
on : Enable audio cues
off : Disable audio cues
This works for breakpoints.
I suggested the feature on GitHub a while ago and they actually implemented it in vs code insiders January build.
My github issue
VS Code Insiders
Related
When an error occurs,NDepend beeps.
When the project has errors.
How do I turn off the sound signal?
Update-1
I use:
Visual NDepend.
The event at which the sound signal appeared:
I performed the close project action.
File -> Close Project.
There was some kind of malfunction in the project.
Therefore, a beep sounded and a dialog box appeared.
Window content: Probably suggested saving something.
Update-2
Created the NDepend project.
Added a project for analysis.
Clicked: File -> Close Project.
NDepend - performed a beep and displayed a window with a suggestion to save the project NDepend.
Since NDepend v2022.2.1 released 10th of November 2022 there is a new Miscellaneous option panel that contains the disable sound required setting:
This is the view I get when I try to use my VS Code:
I have reinstalled and restarted my system, but no headway. Whenever I open VS Code and want to start a project, it becomes increasingly worse as I hover my mouse, I initially thought my general display had issues, it doesn't affect other apps, just VS Code.
What can I do?
Try disabling hardware acceleration.
From https://code.visualstudio.com/updates/v1_40#_disable-gpu-acceleration
Disable GPU acceleration
We have heard issue reports from users that seem related to how the
GPU is used to render VS Code's UI. These users have a much better
experience when running VS Code with the additional --disable-gpu
command-line argument. Running with this argument will disable the GPU
hardware acceleration and fall back to a software renderer.
To make life easier, you can add this flag as a setting so that it
does not have to be passed on the command line each time.
To add this flag:
Open the Command Palette (⇧⌘P).
Run the Preferences: Configure Runtime Arguments command.
This command will open a argv.json file to configure runtime arguments. You might see some default arguments there already.
Add "disable-hardware-acceleration": true.
Restart VS Code.
Note: Do not use this setting unless you are seeing issues! Editor
I am currently using Flutter with Dart. How do I permanently disable this annoying "Run|Debug" line in vscode?
That Run | Debug is not built-in to vscode. It must be contributed by one of your extensions. These seem like likely culprits:
Dart: Show Main Code Lens
// Whether to show CodeLens actions in the editor for quick running/debugging scripts with main functions.
Dart: Show Test Code Lens
// Whether to show CodeLens actions in the editor for quick running/debugging tests.
In case people get here because there is a Debug or Run in their package.json, that is a separate issue and answer, see https://stackoverflow.com/questions/62358131/how-to-disable-debug-from-showing-in-package-json/62368407?r=SearchResults&s=1|57.9327#62368407
Just disable Enable Code Lens in jest plugin.
It's very annoying! When you write test code, small Debug text shows on top of a test (above it method) when it fails.
During programming, it constantly shows and hides, causing lines of code move up and down a bit. It's terrible experience. Fortunately, easy to disable.
After disabling it, we still have test status feedback:
In VSC settings, search for "Pester Code Lens".
You can disable the first option.
Disable Pester Code Lens
Add this line to your settings:
"editor.codeLens": false,
Or do this in settings:
For Java Extension paste this in your settings.json file
"java.debug.settings.enableRunDebugCodeLens": false
you just open your vs Code Setting -> Text Editor -> Code Lean [Check mark this Box]
I installed VS Code to use with Unity. Everything is great except for one small annoyance. When I edit my source code in Code and switch to Unity to run my game, the code is not automatically saved. I have to manually save the VS Code before switching.
I checked settings, but could not find anything. Is there anyway to effect this?
This works fine for me, is this option visible to you?
It is very annoying to see that background around code is lighter then the rest of the program. When the cursor moves the highlighting moves up and down to full window width. Can you please propose solution how to turn this highlighting off. Same problem is in output of task log, and in file explorer.
I have deleted all the settings and Application data and I have same problem. I have installed vscode on windows and I do not have this problem with same settings.
Unfortunately this is an issue in Chromium. You can work around this by starting VS Code with --disable-gpu from the command line.
Sean
It appears this can be fixed for some users by selecting a different color profile in macOS display settings. Note that you have to change this separately for all monitors that you use.
For me, "Apple RGB" will show these blocks, and switching to "LED Cinema Display" or "iMac" solves the issue.
See also: https://github.com/Microsoft/vscode/issues/12473#issuecomment-269024219