Git git git git git

Re:Git git git git git by smellf on Tuesday September 26, 2017 @03:43PM (#15341914)

Think about all the keystrokes you'd save if you just typed "vi" instead.

[ Parent | on HN ]

Re:Git git git git git by kellyjprice on Tuesday September 26, 2017 @03:44PM (#15341918)

That's a habit I may never break. There's been enough times that vi was actually vi.

[ Parent | on HN ]

Re:Git git git git git by Gaelan on Tuesday September 26, 2017 @05:08PM (#15342533)

What kind of evil system ships with both vi and vim?

[ Parent | on HN ]

Re:Git git git git git by sverige on Tuesday September 26, 2017 @08:49PM (#15344007)

OpenBSD comes standard with vi. Vim is a package.

[ Parent | on HN ]

Re:Git git git git git by simias on Wednesday September 27, 2017 @02:42AM (#15345410)

It ships nvi, as do the other BSDs. I think it's reasonable, BSDs have a stronger divide between the base system and third party packages, I'm not sure it would make a lot of sense to maintain vim as part of the former.

Besides on my FreeBSD system /usr/bin/vi is around 400kB while on my Debian machine /usr/bin/vim.basic is 2.4MB. It's not much these days but on embedded platform it could still make a significant difference.

[ Parent | on HN ]

Re:Git git git git git by sverige on Wednesday September 27, 2017 @10:07AM (#15347898)

Yep, and "nex/nvi are intended as bug-for-bug compatible replacements for the original Fourth Berkeley Software Distribution (4BSD) ex and vi programs."

[ Parent | on HN ]

Re:Git git git git git by smellf on Thursday September 28, 2017 @01:46PM (#15359256)

Debian is the same way. But as soon as you open a file with vi on a fresh install, you know it isn't vim, so you close the editor, install vim, and then the vi command opens vim.

[ Parent | on HN ]