From: Jameson Graef Rollins <jrollins@finestructure.net>
To: David Bremner <david@tethera.net>,
Justus Winter <4winter@informatik.uni-hamburg.de>,
notmuch mailing list <notmuch@notmuchmail.org>
Subject: Re: RFC: use the XDG Base Directory Specification for configuration data
Date: Wed, 21 Dec 2011 11:35:37 -0800 [thread overview]
Message-ID: <87hb0tsoom.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87ty4utai7.fsf@zancas.localnet>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
On Wed, 21 Dec 2011 07:44:16 -0400, David Bremner <david@tethera.net> wrote:
> On Wed, 21 Dec 2011 12:19:38 +0100, Justus Winter <4winter@informatik.uni-hamburg.de> wrote:
> > I'd like to propose to store notmuchs configuration in
> > $XDG_CONFIG_HOME/notmuch/config as suggested in the XDG Base Directory
> > Specification [0].
>
> Can you use NOTMUCH_CONFIG to achieve what you want?
I think the suggestion is to just look in
$XDG_CONFIG_HOME/notmuch/config (and maybe ~/.config/notmuch/config)
after ~/.notmuch-config if NOTMUCH_CONFIG isn't set. I think that's
totally reasonable.
> On my machine all of the programs (except nottoomuch ;) ) that use
> ~/.config are gui based, and a bunch of them store binary blobs (or not
> plain text anyway) there. It might be irrational, but I don't really
> want notmuch to be associated with that crowd ;).
It's not all gui applications. I see multiple non-gui apps storing
their config in there. I would personally love it if everything
respected that standard. It would clear up my home directory
significantly.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2011-12-21 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 11:19 RFC: use the XDG Base Directory Specification for configuration data Justus Winter
2011-12-21 11:44 ` David Bremner
2011-12-21 19:35 ` Jameson Graef Rollins [this message]
2012-01-12 17:19 ` Pieter Praet
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=87hb0tsoom.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=4winter@informatik.uni-hamburg.de \
--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).