Re: Bug#628018: [PATCH] notmuch-mutt utility for notmuch/contrib/

diff --git a/9d/d5330d7d1111c6d0245d0d5442b214825308f0 b/9d/d5330d7d1111c6d0245d0d5442b214825308f0
new file mode 100644 (file)
index 0000000..e5e5f03
--- /dev/null
+++ b/9d/d5330d7d1111c6d0245d0d5442b214825308f0
@@ -0,0 +1,95 @@
+Return-Path: <zack@upsilon.cc>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 4B09A431FBD\r
+       for <notmuch@notmuchmail.org>; Mon, 26 Mar 2012 08:29:04 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id rD5pZ1GKChrc for <notmuch@notmuchmail.org>;\r
+       Mon, 26 Mar 2012 08:29:03 -0700 (PDT)\r
+Received: from upsilon.hackadomia.org (upsilon.hackadomia.org\r
+ [91.121.245.170])     by olra.theworths.org (Postfix) with ESMTP id 9553A431FAE\r
+       for <notmuch@notmuchmail.org>; Mon, 26 Mar 2012 08:29:03 -0700 (PDT)\r
+Received: from usha.takhisis.invalid (zack.inria.fr [128.93.60.82])\r
+       by upsilon.hackadomia.org (Postfix) with ESMTPSA id A4D1D1012D\r
+       for <notmuch@notmuchmail.org>; Mon, 26 Mar 2012 17:29:02 +0200 (CEST)\r
+Received: by usha.takhisis.invalid (Postfix, from userid 1000)\r
+       id 846DD681650; Mon, 26 Mar 2012 17:29:02 +0200 (CEST)\r
+Date: Mon, 26 Mar 2012 17:29:02 +0200\r
+From: Stefano Zacchiroli <zack@upsilon.cc>\r
+To: notmuch@notmuchmail.org\r
+Subject: Re: Bug#628018: [PATCH] notmuch-mutt utility for notmuch/contrib/\r
+Message-ID: <20120326152902.GA11610@upsilon.cc>\r
+References: <87ehsfr6lb.fsf@zancas.localnet>\r
+       <m2aa33o81v.fsf@guru.guru-group.fi>\r
+       <87d37zl7qe.fsf@servo.finestructure.net>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=iso-8859-1\r
+Content-Disposition: inline\r
+Content-Transfer-Encoding: 8bit\r
+In-Reply-To: <87d37zl7qe.fsf@servo.finestructure.net>\r
+User-Agent: Mutt/1.5.21 (2010-09-15)\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 26 Mar 2012 15:29:04 -0000\r
+\r
+On Mon, Mar 26, 2012 at 08:09:13AM -0700, Jameson Graef Rollins wrote:\r
+> > Another thing is this .cache hardcoding. Should this be resolved\r
+> > first by using $XDG_CACHE_HOME, (then *MAYBE* $XDG_CONFIG_HOME/.cache)\r
+> > and finally $HOME/.cache\r
+> \r
+> These are good points.  I agree that since ~/.cache is an XDG standard\r
+> we should resolve the appropriate environment variables.\r
+\r
+Heya, thanks for your feedback. I agree as well!\r
+\r
+But while it's trivial to make notmuch-mutt itself support\r
+$XDG_CACHE_HOME, it is less so for the Mutt configuration snippet\r
+(i.e. the notmuch-mutt.rc file which is part of my submission). AFAICT\r
+the <change-folder-readonly> function does not support variable\r
+expansions, not to mention default values while doing so. As a result, I\r
+can easily support $XDG_CACHE_HOME for, say, the history file, but I\r
+don't know how to make mutt look in some $XDG_CACHE_HOME derived\r
+directory. (Yes, I'm excluding hackish solutions like have mutt look\r
+always in the same dir, and make that dir a "moving" symlink that will\r
+be changed by notmuch-mutt upon execution. That seems to defeat the\r
+benefits of the XDG specification, at least partly.)\r
+\r
+Bottom line: I'll be happy to properly support $XDG_CACHE_HOME, but I'm\r
+in need on suggestions of how to do so for the Mutt configuration part.\r
+\r
+> If notmuch-mutt is accepted into notmuch upstream then it really becomes\r
+> a part of notmuch and isn't really "public" anymore (at least in the\r
+> sense that you're using).  So I don't really see any problem with having\r
+> it use ~/.cache/notmuch.\r
+\r
+My thought exactly.\r
+\r
+The proposal of documenting how people should use ~/.cache/notmuch is\r
+great, but I was hoping it can be overlooked for contrib stuff that has\r
+been vetted by you folks.\r
+\r
+Thanks for your help (and for notmuch!)\r
+Cheers.\r
+-- \r
+Stefano Zacchiroli     zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .\r
+Maître de conférences   ......   http://upsilon.cc/zack   ......   . . o\r
+Debian Project Leader    .......   @zack on identi.ca   .......    o o o\r
+« the first rule of tautology club is the first rule of tautology club »\r