From: Stefano Zacchiroli <zack@upsilon.cc>
To: notmuch@notmuchmail.org
Subject: Re: Bug#628018: [PATCH] notmuch-mutt utility for notmuch/contrib/
Date: Mon, 26 Mar 2012 17:29:02 +0200 [thread overview]
Message-ID: <20120326152902.GA11610@upsilon.cc> (raw)
In-Reply-To: <87d37zl7qe.fsf@servo.finestructure.net>
On Mon, Mar 26, 2012 at 08:09:13AM -0700, Jameson Graef Rollins wrote:
> > Another thing is this .cache hardcoding. Should this be resolved
> > first by using $XDG_CACHE_HOME, (then *MAYBE* $XDG_CONFIG_HOME/.cache)
> > and finally $HOME/.cache
>
> These are good points. I agree that since ~/.cache is an XDG standard
> we should resolve the appropriate environment variables.
Heya, thanks for your feedback. I agree as well!
But while it's trivial to make notmuch-mutt itself support
$XDG_CACHE_HOME, it is less so for the Mutt configuration snippet
(i.e. the notmuch-mutt.rc file which is part of my submission). AFAICT
the <change-folder-readonly> function does not support variable
expansions, not to mention default values while doing so. As a result, I
can easily support $XDG_CACHE_HOME for, say, the history file, but I
don't know how to make mutt look in some $XDG_CACHE_HOME derived
directory. (Yes, I'm excluding hackish solutions like have mutt look
always in the same dir, and make that dir a "moving" symlink that will
be changed by notmuch-mutt upon execution. That seems to defeat the
benefits of the XDG specification, at least partly.)
Bottom line: I'll be happy to properly support $XDG_CACHE_HOME, but I'm
in need on suggestions of how to do so for the Mutt configuration part.
> If notmuch-mutt is accepted into notmuch upstream then it really becomes
> a part of notmuch and isn't really "public" anymore (at least in the
> sense that you're using). So I don't really see any problem with having
> it use ~/.cache/notmuch.
My thought exactly.
The proposal of documenting how people should use ~/.cache/notmuch is
great, but I was hoping it can be overlooked for contrib stuff that has
been vetted by you folks.
Thanks for your help (and for notmuch!)
Cheers.
--
Stefano Zacchiroli zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .
Maître de conférences ...... http://upsilon.cc/zack ...... . . o
Debian Project Leader ....... @zack on identi.ca ....... o o o
« the first rule of tautology club is the first rule of tautology club »
next prev parent reply other threads:[~2012-03-26 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 10:32 [Stefano Zacchiroli] Bug#628018: [PATCH] mutt-notmuch in notmuch contrib David Bremner
2012-03-26 10:37 ` [Stefano Zacchiroli] Bug#628018: [PATCH] notmuch-mutt utility for notmuch/contrib/ David Bremner
2012-03-26 12:34 ` Tomi Ollila
2012-03-26 15:09 ` Jameson Graef Rollins
2012-03-26 15:29 ` Stefano Zacchiroli [this message]
2012-03-26 18:52 ` Stefano Zacchiroli
2012-03-26 19:03 ` Scott Barker
2012-03-26 21:15 ` Stefano Zacchiroli
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=20120326152902.GA11610@upsilon.cc \
--to=zack@upsilon.cc \
--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).