Explore >> Select a destination
|
You are here 
|
miguelcrespo.co | ||
| | | | |
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 f... | |
| | | | |
m4xshen.dev
|
|
| | | | | Learn how to develop a Neovim plugin in Lua. Understand the structure of Neovim plugin, Lua module, and create a simple plugin. | |
| | | | |
daniel-siepmann.de
|
|
| | | | | Want to know how to write plugins for Neovim within Python? Check infos from my Talk at Vimfest Berlin 2017. | |
| | | | |
coen.needell.org
|
|
| | | 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 (... | ||
