Very basic question.
Every time in in VS Code and press the letter "O", it opens the output log from the bottom of the screen and it takes up most of the screen space. Not only that, it's also useless for me (at least now) and I don't need it every time I press "O".
Searched in google for an answer, and found nothing.
Any help would be appreciated.
You can change the keybindings in VS Code, these instructions may be helpful.
Related
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.
"press the restart button to restart Visiual Studio Code and enable the setting."
Now Im going to preface this by saying that this is quite possibly the most annoying thing I have ever experienced in my years computing.
I'm new to VS Code and as such I am knee deep in my settings.json a lot of the time. Especially moreso when Ive just installed a new extension and it comes with loads of parameters, alnd all sorts of goodies - sort of like I did today when I got home from work.
I open settings.json. I add a comment line indicating a new section for my new extension's myriad of settings I half understand, and move any auto-generated config settings from the bottom to the freshly minted position. I start typing, the widget pops up letting me know about all 70+ settings I can fiddle with as much as I please.
I hit tab on the first entry, it goes down. Tab again, "true" goes down.
"A setting has changed that requires a restart to take effect"
OKAY no problem VS code. Quick restart, back to my config.
I start typing the extension again, I get 200ms in or however long it takes for that widgit to appear, and
"A setting has changed that requires a restart to take effect"
I watch the text in my editor contort as the settings are unloaded and reloaded and unloaded again.
I got the first 4 characters of the extension name typed out before this lovely notification reappears.
Now,
when this happens a few times its a little irritating.
BUT THIS IS CONSTANT .Every. Single. Line. I try to add. Each and every setting. Sometimes 2 or 3 times before I actually get the string down, never-mind its value.
I don't know what to do, I am legitimately going to rip my hair out. This is by far easily up there with one of the most frustrating things I have ever been forced to endure. It is relentless.
I dont know what else to do. Ive tried all I can think of.
I just want to learn and use my new extension.
Please for the love of anything help me.
Please.
I'm using VSC and since three or four days, always when I type "r" in css files, yes only css files, a weird textbox will open. e.g. if I wanna write "margin", I'll killed at r, my cursor will be moved into the box and in the textbox then contains "ma". sth like this: https://ibb.co/fdbFtBn if I continue, in the line is "ma" and in the box is "gin".
Is this at all from VSC? Or is this a extension from me? If it is a extension, sorry for this question.
I have already googled this problem, but I found nothing that was helpfull. And on VSC's page is: "You can ask questions and search for answers on Stack Overflow"
I hope someone can help me here.
Thanks for every usefull help.
i am driven crazy by annoying pop hint every time when I hit Space key. As shown below:
Now, how to find out which extension or pop snippet hint is causing the issue when I hit space key and which one to disable it ?
There are two ways to solve this issue.
Method 1:
In VSCODE. click File > preferences > keyboard shortcuts and search for space you could see space might be wrongly assigned to some intelli sense. Click on that particular keyboard shortcut. Double click the stroke and change the shortcut.
Method 2:
Very expensive way.
Disable all extensions first and try the space keystroke then try enabling one by one. You will definitely find the culprit.
Hope it helps
I solved it eventually by disable all snippet extend one bye one, then the latest extensions, found out the cause is https://github.com/bauhausr/antd-intellisense extension.
It drives me crazy too. I just turned off Editor: Suggest On Trigger Characters and it seems to be working for me!
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...