2 ms·

Genealogy of Vim (2017)

• ggm 4y ago
  Elides over Elvis,neovim and nvi but not actually wrong, just.. very tersely incomplete. (An nvi fan, but at this point, it's vim and memories of what could have been)
  • turtleyacht 4y ago
    Do you have a place for any nvi tips and tricks? Or any macros you have shared? So far I have Matt Widmann's notes: https://mattwidmann.net/notes/the-nvi-text-editor/ https://mattwidmann.net/notes/the-nvi-text-editor/ vi mail archive (not much, mirrored) Learning the vi and vim editors (O'Reilly) johnsonjh@github work on OpenVi: https://github.com/johnsonjh/OpenVi https://github.com/johnsonjh/OpenVi HN comments around OpenVi, nvi, etc: https://news.ycombinator.com/item?id=30394952 https://news.ycombinator.com/item?id=30394952
    • ggm 4y ago
      Sorry, I've got nothing. Like a lot of older vi users from the 80s, I stick to the limited repertoire I know, and don't explore the margins. VIM is very actively maintained and has a heap of stuff which I don't exploit. Arguably Vim is a better "fit" for modern s/w development, because of those enhancements. I don't use colourisation, I have minor fights around tab expansion and cut-paste buffer processing all of which are fixable, its the remembrance of how the fix propagates mainly!
      • turtleyacht 4y ago
        It's okay. Thank-you for your reply. I don't colorize either. But my focus is narrow, and I don't need to jump too much once all the tmux windows are open. Vim is nice, but maybe I like nvi's simplicity. An HN comment about nvi a couple years ago just took me on a trip that I've been on ever since: https://news.ycombinator.com/item?id=13959104 https://news.ycombinator.com/item?id=13959104 (2017)