From: Dario <piombo.dario@gmail.com>
To: David Bremner <david@tethera.net>
Cc: notmuch@notmuchmail.org
Subject: Re: Consider following XDG base directory specification
Date: Mon, 24 Oct 2022 15:39:46 +0200 [thread overview]
Message-ID: <20221024133946.x3rbmlshw3mfjzkk@dario-arch3> (raw)
In-Reply-To: <87v8o9wjp5.fsf@tethera.net>
Thanks for replying thank you very much for pointing me in the right
direction. I guess I didn't RTFM properly. Environment variables are
good enough for me.
Keep up the good work.
On 2022-10-24 08:21:42-0300, David Bremner wrote:
> Dario <piombo.dario@gmail.com> writes:
>
> > I apologize in advance if the issue has already been raised by somebody else
> > but I couldn't find anything on the bug tracker and furthermore I'm one of
> > those freaks who prefer a de-cluttered home directory. ;-)
> >
> > Instead of saving config file in $HOME/.notmuch-config,
> > ${XDG_CONFIG_HOME:-$HOME/notmuch}/notmuch-config (notmuchrc is a nice name too)
> > should be used for unix-based operating systems according to the XDG Base Directory Specification.
> >
>
> See
>
> https://notmuchmail.org/doc/latest/man1/notmuch-config.html#configuration
>
> > As well as keeping the home directory clean, the semantic separation of config,
> > runtime data, cache data and user-local software by the spec is helpful to users
> > and other tools (e.g. backup software).
> >
> > In terms of migration, I would suggest using the xdg-compilant config location
> > if it exists and falling back to the current default location.
>
> The priority of configurations is unlikely to change at this point. Too
> much potential for breakage for too little gain.
>
> d
>
prev parent reply other threads:[~2022-10-24 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 9:09 Consider following XDG base directory specification Dario
2022-10-24 11:21 ` David Bremner
2022-10-24 13:39 ` Dario [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221024133946.x3rbmlshw3mfjzkk@dario-arch3 \
--to=piombo.dario@gmail.com \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).