[haiku-development] Re: Final Set*UIColor Patch, Version 3e

  • From: Adrien Destugues <pulkomandy@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Sun, 22 Nov 2015 20:41:37 +0100

On Sun, Nov 22, 2015 at 08:36:44PM +0100, Jérôme Duval wrote:

2015-11-22 20:28 GMT+01:00 Adrien Destugues <pulkomandy@xxxxxxxxx>:
On Sun, Nov 22, 2015 at 11:57:46AM -0600, looncraz wrote:
* Also, why does the commit editor behave so badly? It is really hard to
correct typos in the commits from within Haiku.

And I forgot to reply about this: the current default editor is Nano,
which has been broken for years, and still is. There was a vote years
ago to remove vi from the image (despite it being required by POSIX) and
ship with Nano as the default editor). It seems no one uses it (or
everyone lives with the bugs, which I would find surprising). If no one
actually uses Nano, I would suggest we switch to vi or Pe (with lpe),
both of which work fine.

I think the story was that Vim takes 10MB we needed to fit on a CD,
while Nano makes it in 350KB... Pe isn't a command line editor, or is
it?

At the time this was discussed we had a smaller port of vi (not vim, IIRC)
in-tree. Our current vim package includes not only vim, but a lot of
syntax files, the GUI enabled gvim, etc. It could be split if needed.

As for Pe, there is the lpe wrapper which allows to use it as the
default $EDITOR. I mention it because from my looking at other people
screen during BeGeistert, it seems to be a popular choice of editor. Why
insist on Nano, then? But you are right, it is not fully command line
and cannot be used through ssh, for example.

--
Adrien.

Other related posts:

  1. Home
  2. haiku-development
  3. Archive
  4. 11-2015