VulcanSphere@kbin.social to Technology@lemmy.world · edit-21 year agoRIP Bram Moolenaar, the author of vim text editorgroups.google.comexternal-linkmessage-square60fedilinkarrow-up1997arrow-down113file-textcross-posted to: linux@lemmy.mllibre@hexbear.nettechnology@beehaw.orglinux@kbin.socialvim@lemmy.sdf.orglinux@lemmy.mlopensource@lemmy.mlfoss@beehaw.org
arrow-up1984arrow-down1external-linkRIP Bram Moolenaar, the author of vim text editorgroups.google.comVulcanSphere@kbin.social to Technology@lemmy.world · edit-21 year agomessage-square60fedilinkfile-textcross-posted to: linux@lemmy.mllibre@hexbear.nettechnology@beehaw.orglinux@kbin.socialvim@lemmy.sdf.orglinux@lemmy.mlopensource@lemmy.mlfoss@beehaw.org
minus-squaretun@lemmy.worldlinkfedilinkEnglisharrow-up21·1 year agoI started with nano, learnt vim and now using neovim.
minus-squarelawrence@lemmy.worldlinkfedilinkEnglisharrow-up2·1 year agoI am waiting for neovim 1.0, using vim until there.
minus-squaretun@lemmy.worldlinkfedilinkEnglisharrow-up4·1 year agoNeovim is stable even though it is still using minor version number. The eco system booms after 0.5 (lua support, lsp and treesitter) and after lazy.nvim.
I started with nano, learnt vim and now using neovim.
I am waiting for neovim 1.0, using vim until there.
Neovim is stable even though it is still using minor version number.
The eco system booms after 0.5 (lua support, lsp and treesitter) and after lazy.nvim.