Re: [PATCH] Add Haskell syntax highlighting

[Kamil Dudka]

On Saturday, September 12, 2020 7:37:02 PM CEST Benno Schulenberg wrote:
> Op 11-09-2020 om 11:58 schreef Kamil Dudka:
> > On Friday, September 11, 2020 11:27:39 AM CEST Benno Schulenberg wrote:
> >> It is unfortunate that /etc/nanorc exists and that several distros
> >> uncomment the "include /usr/share/nano/*.nanorc".  It would have been
> >> better if they used a skeleton .nanorc so that each user can trim the
> >> includes without inheriting everything from /etc/nanorc.
> > 
> > Each approach has its pros and cons.  The problem of ~/.nanorc is that it
> > is usually not manipulated directly by package managers.  So any updates
> > would need to go to /etc/skel/.nanorc, which would only take an effect for
> > newly created user accounts.  If we enabled syntax highlighting this way
> > in Fedora, I am afraid that some users would still not be aware that nano
> > ever supports syntax highlighting.
> 
> True.  But if users choose to do rolling upgrades from one version of an
> operating system to the next, without reinstalling, then this probably
> means they are rather attached to their configurations and setting, and
> do not want them to change in any way.  Thus they might become aware of
> new features of programs only when they have to install the OS on a new
> machine.  There is no harm in that.

Fair enough.  The problem is that nano has been packaged this way since 2015.  
If we moved the line `include "/usr/share/nano/*.nanorc"` from /etc/nanorc
to /etc/skel/.nanorc , we would disable syntax highlighting exactly for the
users that do not want to change anything.  Do you have any idea how to make 
the transition any smoother?

I am not sure whether it was mentioned here but nano is going to be used
as the default editor in Fedora 33:

    https://fedoraproject.org/wiki/Changes/UseNanoByDefault

So Fedora users are going to be more sensitive to unexpected changes in nano 
from now on.

Kamil