Return-Path: <scott@mostlylinux.ca>
X-Original-To: notmuch@notmuchmail.org
Delivered-To: notmuch@notmuchmail.org
Received: from localhost (localhost [127.0.0.1])
	by olra.theworths.org (Postfix) with ESMTP id 2F7B9431FAF
	for <notmuch@notmuchmail.org>; Mon, 26 Mar 2012 12:03:40 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
	autolearn=disabled
Received: from olra.theworths.org ([127.0.0.1])
	by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XupYxb611B9r for <notmuch@notmuchmail.org>;
	Mon, 26 Mar 2012 12:03:39 -0700 (PDT)
Received: from aguila.mostlylinux.ca (aguila.ca [184.71.238.186])
	by olra.theworths.org (Postfix) with ESMTP id 67B4D431FAE
	for <notmuch@notmuchmail.org>; Mon, 26 Mar 2012 12:03:39 -0700 (PDT)
Received: from mostlylinux.ca (unknown [10.0.0.128])
	by aguila.mostlylinux.ca (Postfix) with ESMTPSA id B4C3918C807B;
	Mon, 26 Mar 2012 13:03:37 -0600 (MDT)
Date: Mon, 26 Mar 2012 13:03:32 -0600
From: Scott Barker <scott@mostlylinux.ca>
To: Stefano Zacchiroli <zack@upsilon.cc>
Subject: Re: Bug#628018: [PATCH] notmuch-mutt utility for notmuch/contrib/
Message-ID: <20120326190332.GE6677@aguila.ca>
References: <87ehsfr6lb.fsf@zancas.localnet>
	<m2aa33o81v.fsf@guru.guru-group.fi>
	<87d37zl7qe.fsf@servo.finestructure.net>
	<20120326152902.GA11610@upsilon.cc>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20120326152902.GA11610@upsilon.cc>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: notmuch@notmuchmail.org
X-BeenThere: notmuch@notmuchmail.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: "Use and development of the notmuch mail system."
	<notmuch.notmuchmail.org>
List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
List-Archive: <http://notmuchmail.org/pipermail/notmuch>
List-Post: <mailto:notmuch@notmuchmail.org>
List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2012 19:03:40 -0000

FYI, I use the following in my .muttrc, which includes an expansion of $HOME
in <change-folder-readonly>, and it works fine:

  macro index / "<shell-escape>mutt-notmuch --prompt search<enter><change-folder-readonly>$HOME/.cache/mutt_results<enter>" "notmuch search"

On Mon, Mar 26, 2012 at 05:29:02PM +0200, Stefano Zacchiroli wrote:
> 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 »
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch

-- 
Scott Barker
Linux Consultant
scott@mostlylinux.ca
http://www.mostlylinux.ca