Op 02-02-2020 om 14:14 schreef Jonas Smedegaard: > in Debian I would argue that it makes sense for the default shipped master > configfile to include 'include "/etc/nano/*.nanorc"' (and also ship an > empty dir/file as needed if nano chokes on a include directive pointing > to a missing dir/file). Reason being that there are arguably not one > but two "machine admins" below /etc on Debian systems: Debian and the > sysadmin. It makes sense for the sysadmin to be able to tinker with > config snippets without tampering with the master config file, so that > if the master config file later needs updating by the package, that can > happen automatically without consulting the sysadmin how to deal with a > locally forked changed file.
I see. However, the files in include statements can only contain color syntaxes, not any option settings. And in my opinion the machine admin should not "burden" the user with extra syntaxes, because the admin is unlikely to know which syntaxes the users want and need. On the one hand it is nice that Debian does an 'include /usr/share/nano/*.nanorc' in nano's main config file, so that some files have syntax coloring by default. But on the other hand this unnecessarily burdens and slows nano down for users that don't need any coloring, or want it only for a few specific file types. It would have been better if Debian would have chosen not to install an /etc/nanorc at all, but would instead have included the contents of that file as /etc/skel/.nanorc, so that it gets copied into each user's home directory at account creation, and the user can edit it and strip from it anything that is unneeded or unwanted. Benno
signature.asc
Description: OpenPGP digital signature
