[haiku-development] Re: Vim episodes. IV. It is ready to breathe...
- From: Henri Vettenranta <henri.vettenranta@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Tue, 12 May 2009 02:33:11 +0300
On Friday 08 May 2009 12:09:13 Axel Dörfler wrote:
>
> I actually wasn't aware that there are apps that let you end up in
> vim without you knowing it - adding "nano" additionally would not
> solve this, though, so removing vim would be the better option for
> those apps (and eventually making sure EDITOR is set by default).
EDITOR surely needs to be set to such a value that people clueless about
vi do not accidentally end up in it. If nano is in the install, it is in
my opinion the best choice, even if it is one that I personally hate
(but people like me can just edit UserSetupEnvironment or temporarily
set EDITOR if on someone else's machine).
I don't see how not including vi helps in that, though. If some software
hardcodes vi instead of using EDITOR, it's so broken I don't see a
reason to assume it actually checks the return value to see if the
command actually exists, so pretty likely you'll get unexpected results
even then.
Ex is also specified in POSIX, and is used by some scripts. A proper
ex/vi installation shouldn't take more than a few hundred kilobytes at
most, which should be a reasonable price to pay for increased POSIX-
compliance. In case vim-tiny can't do it, I'm pretty sure nvi or elvis
can. Only building the ex parts and leaving vi out, even if possible,
will probably not reduce the binary in any significant amount.
About Cream that someone suggested, I wonder if anyone's tested whether
that works with vim-tiny, or does it require a larger build?
--
Henri Vettenranta
HeTo
Other related posts:
