dotfiles VS nvim-compe

Oh you'd still use a Git repository (e.g. like I do here), stow just takes care of creating the necessary symbolic links (and skipping those that already exist).

I experimented a bit with running rust-analyzer under Bubblewrap when using it through NeoVim's LSP integration (see here). Overall it's doable, but it's a tedious process of finding out what needs to write and where, what capabilities you need, etc. I don't see this seeing adoption unless it becomes a first-class feature of the tool in question.

You can also use Bubblewrap, but getting it up and running requires a lot more fiddling around. For example, this is what I use to isolate Zoom from the rest of my system: https://gitlab.com/yorickpeterse/dotfiles/-/blob/0a0492c78b6...

In my case I'm using Bubblewrap because Firejail was only used for Zoom, and this felt a bit of a waste considering Bubblewrap was already installed.

This is implemented using some custom Lua code.

There's no first-class API for this. I use this setup. This is OK, though I only have two abbreviations, and it does feel a bit overkill for just that.

I've been using neovim-remote for quite some time, and it works perfectly fine. Here is what I use to open NeoVim as usual outside of an existing NeoVim session, and inside the existing session whenever I run nvim from NeoVim's terminal emulator.

You can use this code I wrote for that. You then hook it up like this.

Adjust the icons LSP uses for various symbol types like this. If you leave this out, you need to adjust these lines to use the correct text/icons instead.

The documentation is there, but it's a bit lacking/confusing here and there. It's also mostly foundational work, and you still need to cobble things together (either manually or using a plugin).

With that said, you can build things quite nicely with it. For example, I have a custom linter setup, custom loclist/quickfix list formatting and populating from LSP data, and a bunch of other things; all using the foundational work coming in NeoVim 0.5.

If anybody is curious, you can find my NeoVim configuration here: https://gitlab.com/yorickpeterse/dotfiles/-/tree/master/dotf...

p.s. In case anybody wonders "why Lua?", for me this mostly comes down to this: I hate Lua, but I hate Vimscript even more.

I use https://github.com/hrsh7th/nvim-compe and https://github.com/simrat39/rust-tools.nvim along with the built in LSP and auto completion works really well. You will want treesitter and all that setup too.

I want to share my code for my migration from nvim-compe (deprecated) to nvim-cmp. Though, I would describe myself as an experienced Vimmer I am not very familiar with the whole Lua thing (although I really appreciate it and hope that Lua's first class citizen can compete with the elisp ecosystem^^).

Wrong, plain and simple. A total misconception.

compe.nvim

For autocomplete/intellisense: https://github.com/hrsh7th/nvim-compe

But nvim-compe already exists.

completion-nvim OR nvim-compe

Here's some setup idea: - packer for package manager - clangd language server - nvim-lspconfig, required for navigator.lua - navigator.lua for enchanced IDE experience. This is a like adding a sugar to coffee. - completion-nvim OR nvim-compe for enchanching autocomplete & dropdown menu suggestion. - nvim-treesitter for better syntax highlighting. - telescope.nvim for amazing extensible & configurable fuzzy finder, you can also use fzf if you want. - Any custom color scheme you want (preferably one that supports tree sitter, like aurora )