Explore >> Select a destination

You are here

 nanotipsforvim.prose.sh
A bare bones modern nvim config in < 100 lines
| | xnacly.me
Highlighting Parts of Lua as Bash | xnacly - blog
2.5 parsecs away

Travel
| | Using Treesitter in neovim to conditionally highlight code snippets
| | www.integralist.co.uk
Setting up Neovim for Rust and Go development ? Mark McDonnell
1.3 parsecs away

Travel
| | UPDATE November 2022 Not long after I wrote this post I had switched from VimScript to using Lua and also making large sets of changes and tweaks to my configuration. The source of truth is: https://github.com/integralist/nvim (which is a submodule within https://github.com/integralist/dotfiles) This post is being kept for posterity, but ultimately I would recommend you look at the above dotfiles repo instead. This is going to be a very focused post because when you're looking to get your code editor con...
| | mariocarrion.com
Neovim: migrating to lazy.nvim and go.nvim
1.4 parsecs away

Travel
| | Packer is no longer supported; time to migrate to lazy; also, I decided to stop using vim-go, replacing it with go.nvim
| | coen.needell.org
Neovim for Data Science, Part 1: Scripting
6.8 parsecs away

Travel
| Vim, "the ubiquitous text editor", has been with us since the 1980s, with new programmers discovering its arcane power every day. It was originally developed for the Atari ST under the name "Stevie" (ST Editor for VI Enthusiasts), and was later ported to Unix and OS/2 (a precursor to Windows). Originally, vim was simply an Atari port of vi1:, which in turn was the visual mode for the command line text editor ex2. It continued to use the name "Stevie" until 1993, when the name was changed to Vi iMproved (...