DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:sender:in-reply-to:references:date
	:x-google-sender-auth:message-id:subject:from:to:cc:content-type
	:content-transfer-encoding;
	b=W+KedokSecZ8xUU08hBrRls8KZgoR8NtUaV+xpszkhNmqZhZuqq/E+mAw+8a9B8cTX
	i1rf4Vd6jo9tBkO516XLqMDM79jLove8gEx460GsvLuCfuskgU5G3SL3Qpk9reVpVva2
	jdl+X0y83809WEFsgqWDiXpfKnHWTRVst6V4c=
MIME-Version: 1.0
Sender: anthony.j.towns@gmail.com
In-Reply-To: <m3d3xsyzyn.fsf@x200.gr8dns.org>
References: <1271747793-17507-1-git-send-email-sojkam1@fel.cvut.cz>
	<87pr1u7fnu.fsf@ut.hh.sledj.net> <87fx2qmtok.fsf@SSpaeth.de>
	<4BCD7EA0.3080505@fel.cvut.cz> <871ve8wc30.fsf@yoom.home.cworth.org>
	<m3d3xsyzyn.fsf@x200.gr8dns.org>
Date: Thu, 22 Apr 2010 13:13:39 +1000
Message-ID: <w2w87b3a4191004212013r8d410ca6u5c0651d3ee74aa7@mail.gmail.com>
Subject: Re: [PATCH 1/2] Add 'cat' subcommand
From: Anthony Towns <aj@erisian.com.au>
To: Dirk Hohndel <hohndel@infradead.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: notmuch@notmuchmail.org
Precedence: list

On Thu, Apr 22, 2010 at 12:37, Dirk Hohndel <hohndel@infradead.org> wrote:
> On Wed, 21 Apr 2010 17:44:03 -0700, Carl Worth <cworth@cworth.org> wrote:
>> So I'd prefer to have this command behave just like all others and use
>> the same naming.
>> =A0 =A0 =A0 filename:/complete/path/to/file

Would "notmuch cat" be any different to "notmuch show" in this case?
What happens if you say "notmuch cat something" and multiple messages
match (eg, an id: for a mail that you both sent (Mail/.sent/cur/12345)
and received (Mail/.Lists.notmuch/cur/12346))?

Maybe notmuch show should be able to deal with all these things, and
notmuch cat could be an alias for something like:

    notmuch show --format=3Dmbox --show-duplicate-files $SPEC

?

> should we extend this to something generic that allows remote
> specifications?
> URI:file/path/to/local/file
> URI:ssh/user@host/path/to/file
> URI:git/user@host/path/to/file

You could already do that by using FUSE filesystems to mount your
remote mail dirs under those paths, without having to teach notmuch
about those protocols, as long as you still have the Xapian database
local.

If the Xapian database is remote, you need to invoke "ssh $USER@$HOST
notmuch" (or similar) instead of "notmuch", but the "cat" patch should
be enough to make that work right.

Otherwise, wouldn't you be better off just having this be something
for the database::path setting in .notmuch-config? So you say:

   [database]
   path=3D/home/aj/Mail

or

   [database]
   path=3D/home/aj/Mail/.git
   format=3Dgit

or

   [database]
   # multiple backends
   path=3D/home/aj/Mail
   path=3Dgit:///home/aj/OldMail.git

and have filename: just serve as a unique id that the database knows
how to convert to the contents of the file?

At most (afaics) maybe you'd want to say something like:

    [database]
    path=3D/home/aj/Mail
    path.old=3Dgit:///home/aj/OldMail.git

so that any filename starting with "old/" has the "old/" trimmed and
gets passed to the git backend, while the rest go to the default file
backend.

Cheers,
aj

--=20
Anthony Towns <aj@erisian.com.au>