Date: Mon, 26 Mar 2012 17:29:02 +0200
From: Stefano Zacchiroli <zack@upsilon.cc>
To: notmuch@notmuchmail.org
Subject: Re: Bug#628018: [PATCH] notmuch-mutt utility for notmuch/contrib/
Message-ID: <20120326152902.GA11610@upsilon.cc>
References: <87ehsfr6lb.fsf@zancas.localnet>
	<m2aa33o81v.fsf@guru.guru-group.fi>
	<87d37zl7qe.fsf@servo.finestructure.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <87d37zl7qe.fsf@servo.finestructure.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Precedence: list

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 ť