Vigex
editorconfig-vim
Our great sponsors
| Vigex | editorconfig-vim | |
|---|---|---|
| 1 | 134 | |
| 33 | 3,104 | |
| - | 0.5% | |
| 0.0 | 4.5 | |
| about 2 years ago | 12 days ago | |
| JavaScript | Vim Script | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Vigex
-
Introducing Vigex - PRO Regex Builder 🔥
The build process is quite long, so you can check the entire build process of Vigex on GitHub.
editorconfig-vim
-
Most basic code formatting
These are tools that you need to add. But the most elemental code formatting is not here, it is in the widely supported .editorconfig file.
-
Taking the Language Server Protocol one step further
Hello,
Maybe you should check this project:
https://editorconfig.org/
Regards,
- How to config indentation per project?
-
How We Started Managing BSA Delivery Processes on GitHub
editorconfigchecker. A linter that checks files for compliance with editorconfig rules. Another linter that helps maintain consistency in the format of all files.
-
Ask HN: What work/office purchase transformed your life?
Oh, yeah, we had that issue too and solved it pretty successfully with `.editorconfig` (shareable between VScode and IntelliJ, https://editorconfig.org/) combined with `prettier`.
Each IDE is configured to:
- Not reformat code on its own
- Ignore whitespace
- Run `prettier` as a pre-commit hook
Those settings are saved to `.editorconfig` where possible, or to each IDE's repo-specific folder (e.g. `.idea`).
Then in theory each developer can use whatever IDE they want, whatever whitespace settings they want (tabs vs spaces), and the end code committed to the repo is still the same.
-
Rider - Formatting across projects
I am aware of .editorconfig, and one day that may be the correct answer but the specification does not support every element of the styles of both oss and css.
-
Is there any reason to keep the editorconfig plugin installed?
Does this mean I can completely get rid of this plugin?: https://github.com/editorconfig/editorconfig-vim
-
Is there really no support for editorconfig, yet?
[1] https://editorconfig.org
- How do you handle code formatting in a team?
-
Announcing C# Dev Kit for Visual Studio Code
I dunno who downvoted your question, but I believe you can use .editorconfig to set that up for you.
What are some alternatives?
support - Your go-to guides for understanding Hashnode a little better.
nvim-projectconfig - neovim projectconfig
pycodestyle - Simple Python style checker in one Python file
project-config.nvim - Per project config for Neovim
tabset.nvim - A Neovim plugin to easily set tabstop, shiftwidth and expandtab settings for file types.
prettier - Prettier is an opinionated code formatter.
emacs-solidity - The official solidity-mode for EMACS
reviewdog - 🐶 Automated code review tool integrated with any code analysis tools regardless of programming language
vue-ts - Vite + Vue + TypeScript template
Qodana - 📝 Source repository of Qodana Help
npm.nvim - Npm plugin to make vim user works with npm easier
vim-sleuth - sleuth.vim: Heuristically set buffer options