From: Carl Worth <cworth@cworth.org>
To: Michal Sojka <sojkam1@fel.cvut.cz>,
 Sebastian Spaeth <Sebastian@SSpaeth.de>
Subject: Re: [PATCH 1/2] Add 'cat' subcommand
In-Reply-To: <4BCD7EA0.3080505@fel.cvut.cz>
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>
Date: Wed, 21 Apr 2010 17:44:03 -0700
Message-ID: <871ve8wc30.fsf@yoom.home.cworth.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Cc: notmuch@notmuchmail.org
Precedence: list

--=-=-=
Content-Transfer-Encoding: quoted-printable

On Tue, 20 Apr 2010 12:14:56 +0200, Michal Sojka <sojkam1@fel.cvut.cz> wrot=
e:
> On 20.4.2010 09:21, David Edmondson wrote:
>  > I'm puzzled why you chose to pass a filename as the argument to 'cat'
>  > rather than a message id (id:foo@bar.com)?
>=20
> The reason is that I want be able to distinguish between several=20
> messages with the same id.

All other commands currently accept the generic search terms to specify
messages, (even a command like "notmuch reply" for which it would have
been natural to accept only a single message).

So I'd prefer to have this command behave just like all others and use
the same naming.

The question of how to unambiguously refer to a single file is
orthogonal, (and similarly applies to all commands, such as "notmuch
tag" etc.). I would recommend supporting a search syntax something like:

	filename:/complete/path/to/file

for that use case. And this should work fine whether the filenames are
actual filenames or keys into some abstract file store of some sort.

What do you think?

=2DCarl

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFLz5vT6JDdNq8qSWgRAlZrAKCk1hYWNcG6j4Wd0xDnOtgbyaCxxACghb7C
6BwEiuVp98L8uVIboJgi35o=
=DBLt
-----END PGP SIGNATURE-----
--=-=-=--