How to disable vscode's inbuilt suggestions? - visual-studio-code

I only want to keep the consoleLog but I want the rest gone. I've disabled all extensions and those suggestions are still there. I have no idea which language's suggestions are those but I want them gone. Just the vscode's inbuilt suggestions not the extensions' suggestions.

From looking at the little icon that precedes each entry and finding it here: types of completions - those are variables suggestions.
So you can specifically disable those with
Editor > Suggest: Show Variables

Related

VSCode inserts space after comment sequence

Whenever VSCode formats code, for almost all languages, it will insert spaces after the comment escape sequence (//, #, et cetera).
Although this does not work for C code, I assume that this might be some kind of global setting.
Is it possible to disable the insertion of this extra space somewhere? I follow a style where I don't use the extra spaces after "code-only" comments.
Any (lightweight) extensions that do this (or similar)? Should I make my own...?
I'd like for this solution to work for all languages, although Java is what I use the most.
I tried searching for some extensions related to comments, but it seems that there are none doing this. Is a linter what I need..?
Sorry and thank you in advance!
VS Code doesn't have a default formatter that works across every language so, there is no global solution for you. You will have to check, for every language you noticed such behavior, if the formatter is built in or not, and look for settings individually.
You commented about using Java, and VS Code Java support doesn't provides a formatter, so I suppose you have some Java extension installed, maybe from RedHat. If that's the case, I've noticed (based on extension's Readme) that It has a Java: Open Java Formatter Settings command, which says opens the Eclipse formatter settings. Creates a new settings file if none exists. It's been a long time I don't use Eclipse, so I'm not sure how its settings works, and if it does support the format rule you want. But I suggest you to take a look.
Hope this helps
There is a setting that should affect all languages:
Editor > Comments: Insert Space
It is enabled by default, uncheck it.
It seems that setting java.format.comments.enabled to false was somewhat helpful:
java.format.comments.enabled setting in VSCode
However, it disables formatting for all comments, even JavaDoc ones.

What extension is causing my custom php snippets to get overwritten, and how can I fix this?

If this is due to an extension, how can I remove that extension?
It overwrites my custom snippet, which bothers me.
I disabled many extensions, but nothing changed.
What you're seeing in your screenshot (suggestions for dba_<etc.>) are not coming from any extension. One can verify that by running the command Developer: Reload With Extensions Disabled and trying triggering suggestions again. So this is just functionality that comes out-of-box with a standard VS Code installation. You don't even need to install any PHP extension to get this.
As for your custom snippets getting "overwritten", it's hard to tell without more detail why this is happening. If you're on version 1.75, it might just be due to a bug that will be fixed later (Ex. As was the case in this other recent Q&A: Visual Studio Code's recent update is disrupting autocompletion).
As #Mark showed in their answer, these are function suggestions. You can disable function suggestions with the following setting:
"[php]": {
"editor.suggest.showFunctions": false
}
Those icons indicate that those are Methods and Functions (not Snippets). See What do the Intellisense icons mean.
So you can try to disable two settings in your Settings UI:
Editor > Suggest: Show Methods
Editor > Suggest: Show Functions - this looks like the right one to disable
Of course, there might be situations where you want to see Function suggestions, so you will have to see if disabling the setting is acceptable.
You can disable those Function suggestions for php files only with this setting (in your settings.json):
"[php]": {
"editor.suggest.showFunctions": false
}

How to make vscode start with a blank file?

I want to use vscode instead of notepad. I prefer to type as fast as possible when launching vscode but i can't seem to find this option to do this. Does anyone know what this option is named after or if it's possible with a plugin?
This can by making a small tweak in vscode settings. All you need to do is open preferences and search for Startup editor. Under the Workbench section you'll find the Workbench: Startup Editor option. Change the value of this option to newUntitledFile.
Thanks to Torge Rosendahl whose comment provided the answer:
The setting you are looking for is workbench.startupEditor

Disable ESLint "Quick Fix" suggestions in VSCode

I am using ESLint in my React project to format and lint my code. I use VSCode as editor, and I find the "Quick Fix" suggestions offered by VSCode quite handy, like "import module" etc. However, after enabling ESLint, the default Quick Fix suggestion of VSCode is replaced by ESLint's Quick Fix suggestions:
How do I disable this? Please note that I still want ESLint to format and fix my code, but I don't want its quick fix suggestions. Instead I want VSCode to show its original Quick Fix suggestions. Like in above case, I want VSCode to suggest importing Link from react-router-dom rather than ESlint offering me its own quick fix suggestions (this was happening before enabling ESLint).
I had a similar issue with bash scripts. Disabling the ShellCheck extension solved the issue for me.

VSC command palette (too narrow)

Is there any possibility to make command palette wider?
When looking for symbol (e.g. same functions with different set of arguments) to less characters are shown to choose proper definition.
Is there any possibility to mitigate this problem?
Using standard VS Code settings looks like you can't do this, which I agree should be possible. The strange thing is that I can't find an extension too that does this, so there may be a specific reason why this can't be done at the moment. By the way you can open an Issue on the VSCode Github and ask the developers themself to add this feature or why seems to be missing at the moment