editorconfig-vim
null-ls.nvim
editorconfig-vim | null-ls.nvim | |
---|---|---|
134 | 164 | |
3,104 | 3,554 | |
0.1% | - | |
5.1 | 0.0 | |
18 days ago | 9 months ago | |
Vim Script | Lua | |
GNU General Public License v3.0 or later | 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.
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.
null-ls.nvim
- cpp setting problem
-
Being a bash developer in the 21st century
you can use nvim then, it has shellcheck for diagnostics and formatting, like in vscode :)
here the link to the config: https://github.com/jose-elias-alvarez/null-ls.nvim/blob/main...
-
Linting/formatting and LSP
I use a lot of different languages generally and I'm running into issues around formatting. Is there any standard way to use LSP formatting by default and otherwise fallback to specific linter/formatting programs? I believe null-ls is the normal way of dealing with this, but since it's been archived, I'd rather not rely on it.
-
How to setup efm-langserver for pint formatter?
I've been using pint for formatting php files with null-ls.nvim. Few days ago null-ls.nvim has announced that the plugin will be archived in few months so I started migrating all my formatters and linter from null-ls to efm-langserver. I got other things such as prettier, black, isort, mypy, etc. working but can't get pint to work with php files: If I run pint via efm-langserver, everything is deleted from the buffer, and the saved file is formatted separately. How do I setup efm-langserver correctly to work with pint? Below is my config.yml for pint currently. yaml tools: pint: &pint format-command: "pint --no-interaction --quiet ${INPUT}" format-stdin: false languages: php: - <<: *pint Thank you.
- Archiving Null-Ls
- null-ls will be archived
-
Why is nobody using CoC anymore?
Because null-ls.nvim & mason.nvim together do everything I wanted CoC for
- Your favourite Neovim plugins?
-
How can I get yapf, black, and other formatters working with pylsp?
There is a good answer. I think you know lua and neovim config enough to pick things that you need. If you need a short answer, null-ls is the way.
What are some alternatives?
nvim-projectconfig - neovim projectconfig
formatter.nvim
pycodestyle - Simple Python style checker in one Python file
nvim-lspconfig - Quickstart configs for Nvim LSP
project-config.nvim - Per project config for Neovim
neoformat - :sparkles: A (Neo)vim plugin for formatting code.
tabset.nvim - A Neovim plugin to easily set tabstop, shiftwidth and expandtab settings for file types.
StyLua - An opinionated Lua code formatter
prettier - Prettier is an opinionated code formatter.
nvim-lint - An asynchronous linter plugin for Neovim complementary to the built-in Language Server Protocol support.
emacs-solidity - The official solidity-mode for EMACS
efm-langserver - General purpose Language Server