I would like to change the following VS code behavior but can't find a way to do so:
When the cursor is on some items a box pops up with info about that item. I find this extremely annoying as it often blocks what I'm trying to edit. How to disable the pop up?
I code CSS on a single line, such as:
h1 {something; something; something; } And the next CSS on the next line. No Spaces!
But when I save it VS code automatically reformulates it, putting each something on a new line. This is extremely, extremely annoying! It horribly wastes space, and forces me to scroll down a lot to find something I want to edit. How do I get VS code to stop messing with My Coding Style?
To disable the pop up. Do these necessary changes Disable pop up
To stop the CSS formatting, just see in the extensions if you have downloaded CSS formatter, if so then uninstall it or disable it.
Related
Is there a way to change the style of how dead code is displayed in VSCode?
As of now, it draws to much attention that, and I would like something more subtle.
So Prettier is finicky as it is, but here's a weird situation. The image below shows what happens after a save in VS Code with Prettier set up normally. It randomly removed the tabs for these two lines. If I tab it back into place and save it does it again.
Can anyone tell me why, and how to stop it? Makes the code look really bad.
I have a problem with automatic indentation in VS Code. If you pay attention to the gif below, you will see that the editor only moves a tab forward for the first time, but the second time it should automatically detect that a tab moves forward, but this is not the case. Many editors do not have this problem, but it has really become a problem for me. Also, for example, I do not want to press a shortcut key to solve this problem, I expect the editor to handle.
I found theanswer. Just disable trimAutoWhitespace in VS Code settings.
Anyone knows how to disable automatic removing tabs on new line after delay? Like you can see on picture below, VS Code deletes tabs on new line everytime when I don't start typing very fast.
Something similar is situation when I'm writing comment, create space and wait for a while. VS Code will delete my last space.
I fixed this by turning off the setting "files.autoSave", (I didn't want that in any case.) or disable your formatting tool. (most likely cause)
My problem was that I had a formatting tool run on save, which was removing excess white space and therefore squashing my tabs during editing. Looks like you have the same problem to me.
You can affect a delay if you want to use the auto-save feature by setting auto save to afterDelay and setting the delay to your liking
So, Ive been using Visual Studio code now for several months, and I love it. BUT, there is one thing that is driving me nuts that I'm tired of dealing with.
VSCode has a terrible habit of changing my text when i hit TAB or ENTER at the end of typing. For example, Let's say I'm writing something and I want to tab over a few tabs. So, as an example:
I type "fix", meaning, i hit tab at the end so I can tab over a few columns. When I do this, my line changes to:
"<fix></fix>" (hope this doesnt looks weird, I had to edit to the tags wouldnt be hidden)
So, in order to tab to the right for in-line comments or something, I have to hit SPACE before i hit tab. Lame.
Similar stuff happens when I hit enter immediately after typing something. It changes my text to something else before leaving the line. So, again, I find myself adding an extra space at the end of every line.
Does an extra space hurt me in the long run? No. But my OCD is freaking out over it.
I dont have tab autocomplete turned on, so why is this behaving as such?
I'm using vscode on a Mac. I disabled and uninstalled all extensions... still happens.
So yeah, I've messed with this for days, and only now after I post a question do I figure it out. These two settings took care of my issues:
// When enabled, emmet abbreviations are expanded when pressing TAB.
"emmet.triggerExpansionOnTab": false,
// Controls if suggestions should be accepted 'Enter' - in addition to 'Tab'. Helps to avoid ambiguity between inserting new lines or accepting suggestions.
"editor.acceptSuggestionOnEnter": false
Emmet was the tab issue, and the accept suggestion on enter was the second, even though no suggestion was showing. Hope this helps someone else...