The vi family

(lpar.ath0.com)

20 points | by hggh 7 days ago ago

4 comments

  • be_erik 7 minutes ago

    The history and endurance of vi is impressive. I never thought I would be using the same editor today that I started using in the mid 90s because it was more l33t.

    The comments about LLM contributed code seems like a specific axe to grind that otherwise detracts from a nice history lesson.

  • casey2 a few seconds ago

    Sam isn't graphical there is sam and samterm which sends commands to sam. sam itself is an ed style line editor, where the concept of a line is replaced with a dot. vis allows multiple dots.

    It's worth noting that a lot of the text editing done in the vi family are just calls to ed with different ways of doing selections.

  • openmarkand 7 days ago

    I'm vim poweruser since around 2009. When I use VSCodium (not that much today) I obviously use Vim emulation.

    When I use a different editor, there will be lots of jjkk or ,w (I nmap ,w to :w). Habits die hard.

    Now I switched to neovim due to the amount of good features I like with it. I use exclusively mini.nvim modules that are awesome.

  • saidnooneever 7 days ago

    cool stuff, for a bunch i didnt realise they were really distinct versions!

    Use Helix now as the first one that stuck in my fingers though. before that it was always try a lil while and forget it (back to nano...).

    Helix i think is like 'user friendly vi' or maybe 'no config vi'. dont need any plugins or weird stuff. everything essential works out of the box (for me)