Re: [Nano-devel] [RFC] is it time to break free from the Pico defaults

[Benno Schulenberg]

Op 26-11-18 om 21:47 schreef Devin Hussey:
>> From: Benno Schulenberg <address@hidden>
>> And loading all syntaxes by default is a performance killer.
> 
> real    0m0.375s
> user    0m0.262s
> sys    0m0.071s
> 
> real    0m0.602s
> user    0m0.309s
> sys    0m0.068s

I'm guessing the first is with --ignore and the second with all syntaxes
included?

> That is a very minor difference for an 8mb file

An eight *megabyte* file?!  I don't think that is a typical file that
nano is used for.  The README file would be much closer to that.

With a die("") inserted just before the last statement in src/nano.c,
then running 'time src/nano --ignore README' results in:

real    0m0,012s
user    0m0,004s
sys     0m0,008s

And 'time src/nano README' in:

real    0m0,050s
user    0m0,036s
sys     0m0,009s

Including all syntaxes makes startup four times as slow.  (Hot cache.)
That is considerable.

>> I was thinking more of:
>>
>>         set morespace
> 
> Coming from someone who studied both web and graphic design, morespace
> is kind of visually unpleasant.

Yeah, it kind of is.  That's why I've not used 'set morespace' for a
long time.  But nowadays having an extra line of text outweighs the
slight visual "crampiness".

> We should have an initial gap at the
> first line, which scrolls away as the user scrolls. I think that looks
> best.

Might be, but... *far* too complicated to make.

(If you consider making such a thing, maybe consider first using the
line of the statusbar for displaying an extra line of the buffer when
there is no status message, like joe does.)

>>         set nonewlines
> 
> Is there an option to only set nonewlines if the existing file has no
> trailing new line?

What would that accomplish?

Benno

signature.asc
Description: OpenPGP digital signature