1 Return-Path: <zack@upsilon.cc>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 4B09A431FBD
\r
6 for <notmuch@notmuchmail.org>; Mon, 26 Mar 2012 08:29:04 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id rD5pZ1GKChrc for <notmuch@notmuchmail.org>;
\r
16 Mon, 26 Mar 2012 08:29:03 -0700 (PDT)
\r
17 Received: from upsilon.hackadomia.org (upsilon.hackadomia.org
\r
18 [91.121.245.170]) by olra.theworths.org (Postfix) with ESMTP id 9553A431FAE
\r
19 for <notmuch@notmuchmail.org>; Mon, 26 Mar 2012 08:29:03 -0700 (PDT)
\r
20 Received: from usha.takhisis.invalid (zack.inria.fr [128.93.60.82])
\r
21 by upsilon.hackadomia.org (Postfix) with ESMTPSA id A4D1D1012D
\r
22 for <notmuch@notmuchmail.org>; Mon, 26 Mar 2012 17:29:02 +0200 (CEST)
\r
23 Received: by usha.takhisis.invalid (Postfix, from userid 1000)
\r
24 id 846DD681650; Mon, 26 Mar 2012 17:29:02 +0200 (CEST)
\r
25 Date: Mon, 26 Mar 2012 17:29:02 +0200
\r
26 From: Stefano Zacchiroli <zack@upsilon.cc>
\r
27 To: notmuch@notmuchmail.org
\r
28 Subject: Re: Bug#628018: [PATCH] notmuch-mutt utility for notmuch/contrib/
\r
29 Message-ID: <20120326152902.GA11610@upsilon.cc>
\r
30 References: <87ehsfr6lb.fsf@zancas.localnet>
\r
31 <m2aa33o81v.fsf@guru.guru-group.fi>
\r
32 <87d37zl7qe.fsf@servo.finestructure.net>
\r
34 Content-Type: text/plain; charset=iso-8859-1
\r
35 Content-Disposition: inline
\r
36 Content-Transfer-Encoding: 8bit
\r
37 In-Reply-To: <87d37zl7qe.fsf@servo.finestructure.net>
\r
38 User-Agent: Mutt/1.5.21 (2010-09-15)
\r
39 X-BeenThere: notmuch@notmuchmail.org
\r
40 X-Mailman-Version: 2.1.13
\r
42 List-Id: "Use and development of the notmuch mail system."
\r
43 <notmuch.notmuchmail.org>
\r
44 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
45 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
46 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
47 List-Post: <mailto:notmuch@notmuchmail.org>
\r
48 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
49 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
50 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
51 X-List-Received-Date: Mon, 26 Mar 2012 15:29:04 -0000
\r
53 On Mon, Mar 26, 2012 at 08:09:13AM -0700, Jameson Graef Rollins wrote:
\r
54 > > Another thing is this .cache hardcoding. Should this be resolved
\r
55 > > first by using $XDG_CACHE_HOME, (then *MAYBE* $XDG_CONFIG_HOME/.cache)
\r
56 > > and finally $HOME/.cache
\r
58 > These are good points. I agree that since ~/.cache is an XDG standard
\r
59 > we should resolve the appropriate environment variables.
\r
61 Heya, thanks for your feedback. I agree as well!
\r
63 But while it's trivial to make notmuch-mutt itself support
\r
64 $XDG_CACHE_HOME, it is less so for the Mutt configuration snippet
\r
65 (i.e. the notmuch-mutt.rc file which is part of my submission). AFAICT
\r
66 the <change-folder-readonly> function does not support variable
\r
67 expansions, not to mention default values while doing so. As a result, I
\r
68 can easily support $XDG_CACHE_HOME for, say, the history file, but I
\r
69 don't know how to make mutt look in some $XDG_CACHE_HOME derived
\r
70 directory. (Yes, I'm excluding hackish solutions like have mutt look
\r
71 always in the same dir, and make that dir a "moving" symlink that will
\r
72 be changed by notmuch-mutt upon execution. That seems to defeat the
\r
73 benefits of the XDG specification, at least partly.)
\r
75 Bottom line: I'll be happy to properly support $XDG_CACHE_HOME, but I'm
\r
76 in need on suggestions of how to do so for the Mutt configuration part.
\r
78 > If notmuch-mutt is accepted into notmuch upstream then it really becomes
\r
79 > a part of notmuch and isn't really "public" anymore (at least in the
\r
80 > sense that you're using). So I don't really see any problem with having
\r
81 > it use ~/.cache/notmuch.
\r
85 The proposal of documenting how people should use ~/.cache/notmuch is
\r
86 great, but I was hoping it can be overlooked for contrib stuff that has
\r
87 been vetted by you folks.
\r
89 Thanks for your help (and for notmuch!)
\r
92 Stefano Zacchiroli zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .
\r
93 Maître de conférences ...... http://upsilon.cc/zack ...... . . o
\r
94 Debian Project Leader ....... @zack on identi.ca ....... o o o
\r
95 « the first rule of tautology club is the first rule of tautology club »
\r