Re: [Nano-devel] proposal to add support for the XDG base directory spec

[Benno Schulenberg]

Op  4-10-2017 om 00:12 schreef Brand Huntsman:
> On Tue, 3 Oct 2017 21:25:17 +0200 Benno Schulenberg <address@hidden>
> wrote:
> > On second thought: nano shouldn't put those files in a single dir, because
> > it might give the user the impression that filepos_history and
> > search_history are config files too, and are meant to be edited. They
> > aren't.  So they should probably go into $XDG_CACHE_HOME, right?
>
> Binary config files aren't meant to be edited by the user either, doesn't mean
> they should go in cache. Anything in cache is likely to not get backed up as
> it can easily be recreated by re-downloading or re-generating. Many users
> might want nano's history files to be backed up.

Where should they go then?  In $XDG_DATA_HOME?  That's where Poedit keeps
its translation memory, and Rhythmbox its database and playlists, so that
makes some sense.  But the XDG spec seems to want that when you use
$XDG_DATA_HOME, you also have to look in $XDG_DATA_DIRS when that first
one doesn't give any result.  But that doesn't make any sense to me,
because the default for the latter is "/usr/local/share/:/usr/share/",
which will not be user-writable -- so this makes me think that those
DATA things are meant for read-only files?

Also, would the next step be that people will ask that nano should not
simply read /etc/nanorc but first check whether /etc/xdg/nano/nanorc
exists and then read that one instead?

Benno