Please have a look at the image given below and guide me how to fix it. This is making difficult it to read the comments and it is annoying because I like to have my code perfectly indented. Please help me out.
In the image tabsize is 8 (I set it for demonstration purpose)
This is probably caused by using a non-monospace font. To fix, try to reset your font the default settings:
Type Ctrl+Shift+P to open the command menu
Type Preferences: Open Settings (JSON)
Remove the line starting with "editor.fontFamily"
Related
I have an issue where my code-lines wrap to the next line too soon and there's a weird empty margin on the right side of my editor, which takes up useless space. I thought it was the minimap at first, but it's not that. The size remains the same regardless of the editor window size.
I've probably added it by accident through some shortcut keys but can't find anything related to it from the settings.
Looks like you have the Dart extension installed. If so, change Dart: Line Length to a higher number (9999999 if you want). 0 might also work to disable that option.
As it says, you might also need to change the rulers in the dart section of settings.json
enter image description here
Open Extensions on the menu on the left or File menu.
Then click on the extension settings button.
Change the line length for the extension you are working with.
Recently whenever I am coding specifically in Java and have a line of code like sysout, I keep getting the data type or variable before the actual code. Unable to backspace it as it seems to be an overlay without doing anything to the code. I've never had this picky issue before and am unsure if its been implented through vs code or its an extension I have. If anyone knows how I could get rid of the "x: " in line 4 of the image below then that would be great.
Thank you
Line 4 of code
This is a new vscode feature and has nothing to do with Java or any extensions. To get rid of it, put the following in your settings.json:
"editor.inlayHints.enabled": false
To open your settings.json, open the command palette and search for “settings” and click on Open user settings (JSON).
I am a new Flutter learner, and this is kinda annoy me, I think the "Problems" tab under is fully understand, I don't want to see warning next to my code. Is there a way I can disable or hide it? Thank you.
Hey, In visual studio code you can do minute changes.
Step1:
Press ctrl+shift+p , a command pallet will open
Step2:
Type settings.json and click on Open Settings (JSON)
a file will open
step3:
Add this lines in that
"editor.codeActionsOnSave": {
"source.fixAll": true
}
**After this whenever you save, const will be added automatically.
Note: Sometimes you might get error because after saving some widgets are prefixed with const but, sometimes when your values in widget get dynamic, there will be a error, so be careful.
disable this line or add source.fixAll to config.json
Perhaps you are using some vscode plugin like https://marketplace.visualstudio.com/items?itemName=usernamehw.errorlens to show code diagnostics.
Though that feature seems very useful to me incase you find that annoying you may disable it by going through your list of extensions.
I stupidly messed around with my vs code settings and now the intellisense option list is condensed. Does anyone know the fix for this?
Cheers
You should look at the
Editor: Suggest Line Height
0 is the default in which case it uses the Editor: Line Height setting, so it could be either one that is your issue.
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.