VulcanSphere to [email protected] • edit-22 years agoRIP Bram Moolenaar, the author of vim text editorgroups.google.commessage-square60fedilinkarrow-up1990cross-posted to: [email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected]
arrow-up1990external-linkRIP Bram Moolenaar, the author of vim text editorgroups.google.comVulcanSphere to [email protected] • edit-22 years agomessage-square60fedilinkcross-posted to: [email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected]
minus-square@[email protected]linkfedilinkEnglish4•2 years agoOr we could all just move to nano and be less frustrated.
minus-square@[email protected]linkfedilinkEnglish20•2 years agoI started with nano, learnt vim and now using neovim.
minus-square@[email protected]linkfedilinkEnglish2•2 years agoI am waiting for neovim 1.0, using vim until there.
minus-square@[email protected]linkfedilinkEnglish4•2 years 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.
minus-square@[email protected]linkfedilinkEnglish42•2 years agoNa, it’s just that a memorial post is a time to pause the editor wars, if only for a moment, and pay respect.
minus-square@[email protected]linkfedilinkEnglish11•2 years agoNah I’ll pass on that, nano feels dirty.
minus-square@[email protected]linkfedilinkEnglish5•2 years agoI’m rarely as frustrated as when something opens with nano when I’m expecting Vim.
minus-squarePanjalinkfedilinkEnglish3•2 years agoI mean it was on a response with a link detailing the single threaded nature of vim development… I don’t think it was inappropriate
Or we could all just move to nano and be less frustrated.
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.
Damn people here really hate nano 😂
Na, it’s just that a memorial post is a time to pause the editor wars, if only for a moment, and pay respect.
Nah I’ll pass on that, nano feels dirty.
I’m rarely as frustrated as when something opens with
nanowhen I’m expectingVim.I mean it was on a response with a link detailing the single threaded nature of vim development… I don’t think it was inappropriate