Re: [Nano-devel] patch #9772: Add color name definition to the nanorc configuration (color schemes)

[Benno Schulenberg]

Op 14-05-19 om 12:48 schreef Justin F:
> This is a better solution (to my mind) than the current situation where, 
> if you don't like the colour scheme forced on you by the supplied 
> syntaxes, you have to copy those syntaxes. Yes, it's a bit of a faff to 
> write out these rules, but it's better than to have your syntax 
> definitions drift from those used by the ones supplied by Nano.

The syntaxes supplied by nano were originally just meant as examples,
for the user to modify and extend to their taste, as you can still see
from the comment in several of those files.  But some distros started
to install and enable those syntaxes by default, and thus they have
become the de facto standard, I guess.

> I certainly know that my own definitions are significantly different from 
> those supplied with Nano either to fix deficiencies,

If you have improvements to nano's syntaxes that might be useful to
others too, please post patches.

> All feature change makes things slower, but I wouldn't consider this to be 
> too relevant to the editor itself.

True, the impact is not large.  But it is also the indirection that
puts me off.  Something like 'color green "someregex"' is direct and
simple.  But 'color comment "someregex"' requires straining on my part
to keep realizing that 'comment' here is the indirect name of a color.
I don't like it.

> Personally, I am a little surprised that centi-second differences in 
> startup time are of concern to users for that change,

I'm not looking at the absolute numbers, I only look at percentages.
If startup time can be reduced by thirty or forty percent, then that is
worth it, depending on the amount of code it takes.  Nano is dead-slow
compared to things like 'ne' and 'le' -- their snappiness is enviable.

Benno

signature.asc
Description: OpenPGP digital signature