nano-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: packaging nano with a skeleton nanorc file


From: Kamil Dudka
Subject: Re: packaging nano with a skeleton nanorc file
Date: Tue, 15 Sep 2020 18:23:07 +0200

On Tuesday, September 15, 2020 9:55:09 AM CEST Benno Schulenberg wrote:
> Op 14-09-2020 om 12:56 schreef Kamil Dudka:
> > Syntax highlighting is not the only uncommented line in /etc/nanorc on
> > Fedora.> 
> > It also sets the spell checker program:
> >     https://bugzilla.redhat.com/681000
> 
> Since version 4.6 'hunspell' is the default internal spell checker:
> 
>   https://git.savannah.gnu.org/cgit/nano.git/commit/?id=4d77e0ad

Thank you for pointing it out!

Should not we update sample.nanorc to reflect it?

https://git.savannah.gnu.org/cgit/nano.git/tree/doc/sample.nanorc.in?id=8586efda#n158

> (This uses 'hunspell' to create a list of misspelled words and then lets the
> user correct each of them in turn.  Setting 'speller' uses the given
> program as an external checker: the correcting is done in that program too.
>  I notice, though, that 'hunspell' touches the temporary file even when
> zero changes were made, resulting that nano marks the buffer as "Modified".
>  :|  For example, 'aspell' doesn't do this.)
> 
> > I do not think we want to discourage users from configuring anything
> > globally. We should just give them an option to skip the global
> > configuration if needed.
> The only mechanism we have for that is -f: 'nano -f /home/user/somefile'
> will not read /etc/nanorc nor /home/user/.nanorc, but just the indicated
> file.  So, if the user wants the global /etc/nanorc to always be skipped,
> they could do:
> 
>   alias nano="/bin/nano -f /home/user/.nanorc"

So it is possible in the end, although not really intuitive.

Kamil

> Benno





reply via email to

[Prev in Thread] Current Thread [Next in Thread]