From: Michal Sojka <sojkam1@fel.cvut.cz>
To: David Edmondson <dme@dme.org>, Sebastian Spaeth <Sebastian@SSpaeth.de>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH 1/2] Add 'cat' subcommand
Date: Tue, 20 Apr 2010 13:13:36 +0200 [thread overview]
Message-ID: <87y6ginzq7.fsf@steelpick.2x.cz> (raw)
In-Reply-To: <87iq7m75tz.fsf@ut.hh.sledj.net>
On Tue, 20 Apr 2010, David Edmondson wrote:
> On Tue, 20 Apr 2010 12:14:56 +0200, Michal Sojka <sojkam1@fel.cvut.cz> 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)?
> >
> > The reason is that I want be able to distinguish between several
> > messages with the same id.
>
> It strikes me that notmuch is not well suited to this in general. For
> example, how would you find the filenames for the two messages with the
> same message id?
Currently, it is probably not possible but I can imagine that "notmuch
show" will output all file names associated with the message id and user
could select between them if he needs.
M.
next prev parent reply other threads:[~2010-04-20 11:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 7:16 [PATCH 1/2] Add 'cat' subcommand Michal Sojka
2010-04-20 7:16 ` [PATCH 2/2] emacs: Access raw messages through cat subcommand Michal Sojka
2010-04-20 7:21 ` [PATCH 1/2] Add 'cat' subcommand David Edmondson
2010-04-20 8:09 ` Sebastian Spaeth
2010-04-20 10:14 ` Michal Sojka
2010-04-20 10:53 ` David Edmondson
2010-04-20 11:13 ` Michal Sojka [this message]
2010-04-20 11:30 ` David Edmondson
2010-04-20 13:32 ` Jameson Rollins
2010-04-22 0:44 ` Carl Worth
2010-04-22 2:37 ` Dirk Hohndel
2010-04-22 3:13 ` Anthony Towns
2010-04-22 6:57 ` Michal Sojka
2010-04-22 6:38 ` Michal Sojka
2010-04-23 19:07 ` Carl Worth
-- strict thread matches above, loose matches on Subject: below --
2010-10-22 9:28 [PATCH 0/2] Notmuch cat v2 Michal Sojka
2010-10-22 9:28 ` [PATCH 1/2] Add 'cat' subcommand Michal Sojka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y6ginzq7.fsf@steelpick.2x.cz \
--to=sojkam1@fel.cvut.cz \
--cc=Sebastian@SSpaeth.de \
--cc=dme@dme.org \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).