Explore >> Select a destination
|
You are here 
|
icyphox.sh | ||
| | | | |
github.com
|
|
| | | | | Tabnine Client for Neovim. Contribute to codota/tabnine-nvim development by creating an account on GitHub. | |
| | | | |
vinitkumar.me
|
|
| | | | | The blog guides users through a smooth transition from Vim to Neovim, highlighting Neovim's improved performance, enhanced features, and better extensibility. It details the migration process, emphasizing the compatibility between Vim and Neovim configurations. The author's Neovim Lua-based configuration is provided, featuring a curated set of plugins, key mappings, and settings for a more modular and organized setup. The blog concludes by acknowledging the advantages of Neovim's init.lua configuration for those interested in exploring its features and flexibility. | |
| | | | |
ncona.com
|
|
| | | | | I've known about neovim for a long time, but I've never tried it out. My goal for this article is to try to replicate my current vim configuration: File explorer Grep Fuzzy file finder Syntax highlight .vimrc configuration If Neovim is as good as people say, I should be able to do that, and it should run faster. Installation Neovim is already packaged for most OS. Sadly, the version included in Ubuntu is too old for most plugins out there. For this reason, we'll have to build from source. Install prerequisites: 1 sudo apt-get install ninja-build gettext cmake unzip curl | |
| | | | |
ericlathrop.com
|
|
| | | I've finally gotten around to migrating to neovim. When it comes to tech, I don't always migrate to the new shiny thing because sometimes it's buggy or turns out to be the wrong choice. I'm especially conservative with respect to the tools I use daily. I can't afford the time spent on them not working. | ||
