For some reason I have multiple ESLint linters in VSCode options.
Where could they come from, and is there a well known way to remove the duplicates?
Related
Objective
I've a huge vscode Project:
2 Mio Files
100+ GB.
a lot of C-Files, but also build folders a lots of other irrelevant crap.
vscode is slow.
The project includes besides a lot of C/C++ files maybe in some parts cmake files, some codegen/glue-code, external headers, build scripts, external includes from SDK.
I want to use vscode to edit the code, not to compile or run it. The project consists besides the relevant c-files out of a lot of precompiled libs, helper tools, a huge amount of other files and images.
I want to speed my vscode setup up.
How to tell the user supporting tools of vscode, where to set their focus?
Are there any other options to speed up vscode?
Approach
My First Idea: "Make vscode ignore of everything I do not need and tell the tools precisely on what to focus and which leave aside."
Is there a way to make vscode ignore all of such folders in search and in the c++ indexer, the tool which supports code navigation and syntax highlighting?
Clarification / Additional info
I do not have configured vscode. I do not know how. Most the time intellisens/code heighlighting / autocompletion etc. works fine and I can jump around in that code. How ever I've encountered some huge projects, where intellisens failed half or in total or took a lot of time to do so. I do want to set up an project properly. I do not know where to find such settings and most important, which behavior it affects:
intellisense, please have a look only at folders ...
actially, ignore everything below those folders
take this single subfolder, but ignore everything around it.
btw, there is an totally different location for SDK headers, could you also use code and header from there?
I do use vscode to edit the code, I do not use it to compile or debug the code.
In short, I do not know which support tool (intellisense, c++ Extension, ???, ...) have which effect and where they can be configured. Like which vscode components make my life as easy as it is and how do I configure them?
EDIT: List of installed Plugins
as from #user requested :). If cmake is known for eating resources, I could discard it. Is it mandatory for the intellisens stuff?
Could discard python too, if necessary.
ms-vscode.cpptools
https://code.visualstudio.com/docs/editor/codebasics#_advanced-search-options
ms-vscode.cpptools-extension-pack
https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools-extension-pack
ms-vscode.cpptools-themes
https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools-themes
alefragnani.bookmarks
https://marketplace.visualstudio.com/items?itemName=alefragnani.Bookmarks
twxs.cmake
https://marketplace.visualstudio.com/items?itemName=twxs.cmake
ms-vscode.cmake-tools
https://marketplace.visualstudio.com/items?itemName=ms-vscode.cmake-tools
ms-python.python
https://marketplace.visualstudio.com/items?itemName=ms-python.python
ms-python.vscode-pylance
https://marketplace.visualstudio.com/items?itemName=ms-python.vscode-pylance
I love what prettier does in tandem with eslint. I am glad that we can't push up misformatted code without errors, but is there a way to turn off the complaints in vscode? I don't need vscode giving things a red underline because I hit enter and now something is on a new line that the formatter doesn't like, especially when I have format on save. I would guess that the only solution to this is to remove all linting related to formatting and just have things fixed with the running of formatting in pre commit hooks and github actions...
To add onto this. I think the errors I'm getting come from this plugin included in .eslintrc:
"plugin:prettier/recommended"
When I turn it off the errors go away. My preference would be to find a way to hide these errors in vscode while keeping this plugin
I recently started writing SCSS in VSCode. VSCode itself along with vscode-scss extension provides relatively good support for SCSS, but an important feature seems missing - error checking.
Though VSCode and vscode-scss can offer suggestions through Intellisense based on scanning, no errors will be prompted if I misspelled a variable, or used a mixin that hadn't been imported yet. Also, no auto refactoring takes place after renaming an SCSS file that has been used by other sources.
Is there any VSCode extension that provides such validations? Or maybe they can be turned on through some options in extension settings?
Note: I do have noticed the scss.showErrors option of vscode-scss, but no errors get prompted in scenarios mentioned above after turning this option on.
I'm using VSCode and i've been chasing an issue for some time. I've narrowed it down to prettier, thought I don't know how to fix it.
I use autosave extensively to quickly see changes in code through live server. I'd like to keep that if at all possible. I've tried turning format on save off and on, however it appears that so long as I have Prettier enabled, it touches my files and thus overwrites any redo logs.
I've only been using VSCode for about 8 months, and don't have all that much customized, but I do have a few other extensions. However, I've narrowed it down to prettier such that I get the functionality I expect (minus prettier) with it disabled.
I don't really want prettier to format or touch anything unless I press a key combination, so I'm not sure what is wrong. I've tried changing a few other things and looked online, but most everything says to check the "Format on Save" option. However, it doesn't matter whether it's ticked or not, so long as prettier is enabled.
Is there a way to explicitly tell vscode or prettier to only format when I press Shift+Alt+F ?
My project has a prettier.config.js. My colleagues and I use prettier, and format documents on save.
On my machine, but not my colleague's machines, saving files changes the indentation for multiline code (function arguments, objects, etc). See below.
On my colleagues machines it doesn't - if I give them I file I have saved with prettier, it will change the multiline formatting back.
I have deleted and reinstalled the prettier (esbenp.prettier-vscode) extension and this has not solved the problem.
What is this setting called? I have looked in the prettier docs regarding multiline statements.
Why is prettier using a different setting from prettier.config.js?
Here is a diff, when I saved (and ran prettier) over some vcode that my colleagues have already ran prettier over: