helix-vim
mason.nvim
helix-vim | mason.nvim | |
---|---|---|
27 | 108 | |
869 | 6,956 | |
- | - | |
2.0 | 7.7 | |
3 months ago | 9 days ago | |
Lua | ||
- | Apache License 2.0 |
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.
helix-vim
-
Notes on Text Editing
I tried to re-learn from Vim to Helix but failed. No sure if this is a muscle memory problem or perhaps article is right about cons Kakoune-like approach for me. Even adapting with something https://github.com/LGUG2Z/helix-vim did not work. So if you like Helix it probably a good thing that you did not learn the vim at the time.
- Helix-Vim (Readme.md)
- Ask HN: Should you add a LICENSE to example configuration repos?
- Keymap and configuration questions
-
Even more hindsight on Vim, Helix and Kakoune
Not that they're inherently worse, just different - I'm perfectly happy with vim motions and relearning to type is pretty low on my list of priorities. Luckily there is a compatibility hack, not perfect but it's close enough: https://github.com/LGUG2Z/helix-vim
- What editor are you using for Rust?
-
Helix: Release 23.03 Highlights
I want to like Helix, I really, really want to. It's lean, fast, polished, purely console based so it fits my workflows perfectly... but the almost-like-vim-but-not-really key bindings are a deal breaker. I just can't make the switch.
If Helix were completely different in this regard, like Emacs is, I could handle--and I know because I use both vim and Emacs regularly pretty fluently. But Helix is way too close to the vim keybindings to discern it from a memory muscle perspective. I use vim keybindings everywhere else (zsh, all readline-based apps via a setting in ~/.inputrc, VSCode), so getting used to slight differences in just one editor is extremely hard because I can't just drop all other apps.
I recently tried this: https://github.com/LGUG2Z/helix-vim which attempts to provide vim mappings to Helix. It's funny how the description in the page describes my progression almost 100%. And while it makes things slightly better, it's still not accurate enough to make this a non-issue.
-
Helix editor 23.03 released!
https://github.com/LGUG2Z/helix-vim somebody on the internet has you covered
- How to config default VIM keys?
-
The extensible vi layer for Emacs
There is this configuration: https://github.com/LGUG2Z/helix-vim
This switches most keybinds to be vi-like.
mason.nvim
- I can't stand using VSCode so I wrote my own (it wasn't easy)
-
Using a venv with Neovim's Python LSP
I recently started coding with Neovim using kickstart.nvim as the template for my editor configuration. I downloaded the python-lsp-server package using Mason, but I was disappointed to discover that the IntelliSense on my third party dependencies didn't work. The LSP was resolving to my global Python installation, which did not have the packages from my virtual environment (venv) installed.
-
Do I need NeoVIM?
https://github.com/hrsh7th/nvim-cmp This is an autocompletion engine https://github.com/nvim-treesitter/nvim-treesitter This allows NeoVim to install parsing scripts so NeoVim can do things like code highlighting. https://github.com/williamboman/mason.nvim Not strictly necessary, but allows you to access a repo of LSP, install them, and configure them for without you actively messing about in config files. https://github.com/neovim/nvim-lspconfig Also not strictly necessary, but vastly simplifies LSP setup. https://github.com/williamboman/mason-lspconfig.nvim This lets the above two plugins talk to each other more easily.
-
Do I need a plugin manager ?
I'm using mason.nvim to install my dependencies, I've this snippet at nvim/plugin/mason.lua so after cloning my dotfiles I can just run:
-
Mason can't install gopls (or gofumpt, or goimports)
The suggestion from this thread fixed it for me. I just needed to unset GOOS and GOARCH then restart neovim.
-
Neovim documentation is pretty bad
For instance, I'm trying to install rust-analyzer in lazyvim from https://github.com/williamboman/mason.nvim. The installation instructions are:
- LazyVim
-
How do you enable semantic highlighting for Python?
I have pyright installed via mason which apparently support "semantic token highlighting" but have been having a hard time getting these colors to show up in a buffer. It seems Neovim has changed how it handles semantic highlighting a few times so there's still some conflicting information online. It's hard to know what's current and what's not. Any help would be greatly appreciated.
-
language server not installed or missing from path
Use mason to install the language servers you want.
-
Why is nobody using CoC anymore?
Because null-ls.nvim & mason.nvim together do everything I wanted CoC for
What are some alternatives?
helix - A post-modern modal text editor.
lazy-lsp.nvim - Neovim plugin to auto install LSP servers
zsh-vi-mode - 💻 A better and friendly vi(vim) mode plugin for ZSH.
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
meow - Yet another modal editing on Emacs / 猫态编辑
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.
omnisharp-vim - Vim omnicompletion (intellisense) and more for C#
emfy - A dark and sleek Emacs setup for general purpose editing and programming
formatter.nvim
dance - Make your cursors dance with Kakoune-like modal editing in VS Code.
neoformat - :sparkles: A (Neo)vim plugin for formatting code.