Is there a way to improve linting errors highlight in Visual Studio Code? - visual-studio-code

Currently eslint/tslint highlighting for issues/errors is super invisible (comparing, for example, to Atom). Its almost impossible to catch the issue - find the small green highlight zone (see screenshot)
VSCode:
Atom:
Question is not relevant since June 2018 (VSCode now has awesome highlights)

Simple. I use 2 extensions for that:
Error Lens (usernamehw.errorlens) for highlight the entire line and show on real time the error diagnostic
Error Gutters (igorsbitnev.error-gutters) for put error icons next of line number
Both look like this:

For those who would like a partial solution for this you can actually open up the console in vscode on the PROBLEMS tab to display all errors on across your application grouped by file.
I would prefer the inline visualised approach, but this does resolve this problem more or less.
To open the PROBLEMS tab, click CMD+Shift+M on Mac.
Not sure about windows.

Related

Highlighting problem in Jupyter Notebook - VSCode

Lately when using Jupyter Notebook in VS Code to write some assignments for my studies I ran into a quite annoying problem - whenever there is a mistake in my code cell that prevents it from running, the "traceback" (or however you call it) to the place where the error persists is colored with a high-contrast marker (the color depends on the theme used) and makes the content pretty much invisible unless you manually "select" it with the mouse coursor. Is there any way I could fix it without going too much in-depth into VSCode/Jupyter Notebook extension settings?
The highlighting looks like shown below.
Yellow syntax marker problem.
And another one here.
I tried all the themes preinstalled with VS Code such as Monokai, Solarized Light etc., and also a custom theme of my choice called Dracula.
Thanks in advance.
This issue has recently reappeared. While the issue is being fixed you can change the highlight colour within the vscode settings.
Open settings and search for "Workbench:ColorCustomizations"
Image of settings page
Create or alter the "terminal.ansiYellow": "#eed202" to a more appropriate value like "terminal.ansiYellow": "#9b4550". See the linked image.
Credit for this fix: https://github.com/microsoft/vscode-jupyter/issues/8717#issuecomment-1241776226
I also have this problem. It looks like they fixed it less than 1 month ago as of writing this, so it may go away if you update to a recent pre-release of Jupyter in VS Code. Personally, I am going to live with it until the next stable release.
My version of Jupyter in VS Code:
Screenshot of Jupyter Versions
Screenshot of vscode-jupyter github: Screenshot of vscode-jupyter github
https://github.com/microsoft/vscode-jupyter/issues/8697

VSCode editor on macos. Strange behaviour of the multiline selected block

Some time ago I've got a problem with Editor. I select multiple lines (with option-command-<up/down>) and trying to add multiple spaces to shift the whole block to the right. But editor adds tons of extra spaces. Please see screens attached.
Can anyone please help me to bring this to normal state?
Problem has been appeared recently (few days maybe).
VSCode version: 1.46.1
Found it. It was "editor.multiCursorMergeOverlapping". Setting it to true brings the behaviour to default.

Function Selection highlighter/wrapper is missing in VS Code

When I put the mouse pointer inside a function, the entire function should be marked like the picture. But it is missing now. Please suggest me some fixes regarding this issue. https://i.stack.imgur.com/5OL0Y.png
N.B: Currently I'm running VS Code 1.41.0 with Flatland Monokai theme.
If by "marked" you mean the yellow line connecting the opening and closing bracket, then this is part of the Bracket Pair Colorizer extension. There are two versions in the Marketplace, I am using version 0.0.29 and tested it with your theme.
The lines should be enabled by default, however, you might want to check your settings JSON for:
"bracket-pair-colorizer-2.showVerticalScopeLine"
"bracket-pair-colorizer-2.showHorizontalScopeLine"

How to highlight cells in vscode?

Hello,
I have been using vscode (Visual Studio Code) text editor for couple of days. I have come from Spyder IDE for python. I am developing a great likeness towards vscode. It encompasses all of my needs to python programming with also being lightweight.
However, one thing that I am missing and wish it were here in vscode is cell highlighting. Though the editor has feature to segment the code into several cells by typing # %% before a block, it lacks the feature to highlight the cell where mouse pointer is hovered on.
Maybe, there is an option there in settings.json but i don't know where it is in particular. Though it is not a great lack or causes major issues but i like to enable this feature in my vscode editor.
Below pictures illustrate my point.
Previous image is the visual studio code editor and the below one is for Spyder IDE.
It seems it is supported now.
Bellow there's a screenshot for the current version of VSCode using Microsoft's Python extension.
If this answers the question, please, inform as answer.

vscode on mac is incorrectly highlighting text around text blocks

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