darkplus.nvim
editorconfig-vim
Our great sponsors
| darkplus.nvim | editorconfig-vim | |
|---|---|---|
| 4 | 134 | |
| 109 | 3,104 | |
| 7.3% | 0.5% | |
| 7.7 | 4.5 | |
| about 1 month ago | 15 days ago | |
| Lua | Vim Script | |
| GNU General Public License v3.0 only | 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.
darkplus.nvim
-
Lualine wrong background color when changing theme
I just changed my theme to darkplus.nvim and my lualine status bar now has the wrong background color:
-
VSCode default highlight theme in neovim
Darkplus
-
Neovim: Plugins to get started
Github: lunarvim/darkplus.nvim
-
Codicons shifted down a bit
Here's the colorscheme I'm using: https://github.com/LunarVim/darkplus.nvim
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?
neovim-codicons - The icon font for Visual Studio Code
nvim-projectconfig - neovim projectconfig
wezterm - A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
pycodestyle - Simple Python style checker in one Python file
nvim - My neovim config
project-config.nvim - Per project config for Neovim
vscode-codicons - The icon font for Visual Studio Code
tabset.nvim - A Neovim plugin to easily set tabstop, shiftwidth and expandtab settings for file types.
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
prettier - Prettier is an opinionated code formatter.
nvim-lspconfig - Quickstart configs for Nvim LSP
emacs-solidity - The official solidity-mode for EMACS