1 Return-Path: <scott@mostlylinux.ca>
\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 2F7B9431FAF
\r
6 for <notmuch@notmuchmail.org>; Mon, 26 Mar 2012 12:03:40 -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 XupYxb611B9r for <notmuch@notmuchmail.org>;
\r
16 Mon, 26 Mar 2012 12:03:39 -0700 (PDT)
\r
17 Received: from aguila.mostlylinux.ca (aguila.ca [184.71.238.186])
\r
18 by olra.theworths.org (Postfix) with ESMTP id 67B4D431FAE
\r
19 for <notmuch@notmuchmail.org>; Mon, 26 Mar 2012 12:03:39 -0700 (PDT)
\r
20 Received: from mostlylinux.ca (unknown [10.0.0.128])
\r
21 by aguila.mostlylinux.ca (Postfix) with ESMTPSA id B4C3918C807B;
\r
22 Mon, 26 Mar 2012 13:03:37 -0600 (MDT)
\r
23 Date: Mon, 26 Mar 2012 13:03:32 -0600
\r
24 From: Scott Barker <scott@mostlylinux.ca>
\r
25 To: Stefano Zacchiroli <zack@upsilon.cc>
\r
26 Subject: Re: Bug#628018: [PATCH] notmuch-mutt utility for notmuch/contrib/
\r
27 Message-ID: <20120326190332.GE6677@aguila.ca>
\r
28 References: <87ehsfr6lb.fsf@zancas.localnet>
\r
29 <m2aa33o81v.fsf@guru.guru-group.fi>
\r
30 <87d37zl7qe.fsf@servo.finestructure.net>
\r
31 <20120326152902.GA11610@upsilon.cc>
\r
33 Content-Type: text/plain; charset=iso-8859-1
\r
34 Content-Disposition: inline
\r
35 Content-Transfer-Encoding: 8bit
\r
36 In-Reply-To: <20120326152902.GA11610@upsilon.cc>
\r
37 User-Agent: Mutt/1.5.21 (2010-09-15)
\r
38 Cc: notmuch@notmuchmail.org
\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 19:03:40 -0000
\r
53 FYI, I use the following in my .muttrc, which includes an expansion of $HOME
\r
54 in <change-folder-readonly>, and it works fine:
\r
56 macro index / "<shell-escape>mutt-notmuch --prompt search<enter><change-folder-readonly>$HOME/.cache/mutt_results<enter>" "notmuch search"
\r
58 On Mon, Mar 26, 2012 at 05:29:02PM +0200, Stefano Zacchiroli wrote:
\r
59 > On Mon, Mar 26, 2012 at 08:09:13AM -0700, Jameson Graef Rollins wrote:
\r
60 > > > Another thing is this .cache hardcoding. Should this be resolved
\r
61 > > > first by using $XDG_CACHE_HOME, (then *MAYBE* $XDG_CONFIG_HOME/.cache)
\r
62 > > > and finally $HOME/.cache
\r
64 > > These are good points. I agree that since ~/.cache is an XDG standard
\r
65 > > we should resolve the appropriate environment variables.
\r
67 > Heya, thanks for your feedback. I agree as well!
\r
69 > But while it's trivial to make notmuch-mutt itself support
\r
70 > $XDG_CACHE_HOME, it is less so for the Mutt configuration snippet
\r
71 > (i.e. the notmuch-mutt.rc file which is part of my submission). AFAICT
\r
72 > the <change-folder-readonly> function does not support variable
\r
73 > expansions, not to mention default values while doing so. As a result, I
\r
74 > can easily support $XDG_CACHE_HOME for, say, the history file, but I
\r
75 > don't know how to make mutt look in some $XDG_CACHE_HOME derived
\r
76 > directory. (Yes, I'm excluding hackish solutions like have mutt look
\r
77 > always in the same dir, and make that dir a "moving" symlink that will
\r
78 > be changed by notmuch-mutt upon execution. That seems to defeat the
\r
79 > benefits of the XDG specification, at least partly.)
\r
81 > Bottom line: I'll be happy to properly support $XDG_CACHE_HOME, but I'm
\r
82 > in need on suggestions of how to do so for the Mutt configuration part.
\r
84 > > If notmuch-mutt is accepted into notmuch upstream then it really becomes
\r
85 > > a part of notmuch and isn't really "public" anymore (at least in the
\r
86 > > sense that you're using). So I don't really see any problem with having
\r
87 > > it use ~/.cache/notmuch.
\r
89 > My thought exactly.
\r
91 > The proposal of documenting how people should use ~/.cache/notmuch is
\r
92 > great, but I was hoping it can be overlooked for contrib stuff that has
\r
93 > been vetted by you folks.
\r
95 > Thanks for your help (and for notmuch!)
\r
98 > Stefano Zacchiroli zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .
\r
99 > Maître de conférences ...... http://upsilon.cc/zack ...... . . o
\r
100 > Debian Project Leader ....... @zack on identi.ca ....... o o o
\r
101 > « the first rule of tautology club is the first rule of tautology club »
\r
102 > _______________________________________________
\r
103 > notmuch mailing list
\r
104 > notmuch@notmuchmail.org
\r
105 > http://notmuchmail.org/mailman/listinfo/notmuch
\r
110 scott@mostlylinux.ca
\r
111 http://www.mostlylinux.ca
\r