vscode.generateeditorconfig not found
See original GitHub issueWhen I type > EditorConfig: Generate
in the command palette, I receive the following error:
command ‘vscode.generateeditorconfig’ not found
Am I missing some configuration/setting that I need to enable in my VSCode Settings?
- I made sure I’m using the latest version of the plugin.
- I made sure I’m using the latest version of VS Code.
- I can replicate this error in a new, empty VS Code editor window.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
EditorConfig for VS Code not working - Stack Overflow
Here is how I managed to make it work. Install the node package and the VS Code extension as per @webta.st.ic answer. In...
Read more >File not found (\.editorconfig) · Issue #252 - GitHub
Visual Studio Code, editorconfig-vscode ... The error File not found (\.editorconfig) occurs when no ".editorconfig" exists anywhere on disk ...
Read more >EditorConfig for VS Code - Visual Studio Marketplace
This plugin attempts to override user/workspace settings with settings found in .editorconfig files. No additional or vscode-specific files ...
Read more >VS Code tips — The editorconfig extension - YouTube
Today's VS Code extension: editorconfigWith the editorconfig extension, VS Code will pick up basic formatting settings—such as spaces vs ...
Read more >Using the .editorconfig in VS2019 and VSCode
editorconfig is a settings file that overrides the settings of the code editor, it might be that only those settings will work that...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@jedmao , no, the issue has been resolved by following @JimiC’s suggestion.
Thank you.
Either the extension didn’t installed correctly or you are using the
vscode-oss-dev
version (self-compiled).If you use a released
vscode
version uninstall the extension and make sure the extension folder (EditorConfig.editorconfig-version) is removed. If it’s still there, delete it.If you don’t know how to find the folder, provide the OS info on which you are using
vscode
to help you further.