unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Mark Walters <markwalters1009@gmail.com>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
	notmuch@notmuchmail.org
Subject: Re: [PATCH 2/3] cli: all search mode to include msg-ids with JSON output
Date: Thu, 22 Nov 2012 19:35:10 +0000	[thread overview]
Message-ID: <87pq35jus1.fsf@qmul.ac.uk> (raw)
In-Reply-To: <87y5hty5q2.fsf@servo.finestructure.net>


Hi

On Thu, 22 Nov 2012, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
> On Fri, Nov 09 2012, Mark Walters <markwalters1009@gmail.com> wrote:
>> This adds a --output=with-ids option which gives similar output to the
>> normal search summary output but with a list of message ids
>> too. Currently this is not implemented for text format.
>
> Hey, Mark.  Very nit-picky comment here, but I'm not sure "with-ids" is
> an appropriate name for an output type.  "with-ids" sounds like a
> modifier, as opposed to a output type unto itself.

Yes that is true: I am very happy for any suggestions. Perhaps
summary-with-ids?

> But I wonder if this separate output type is really necessary.  Can the
> emacs interface just make two separate search calls to the binary when
> constructing the buffer, one with --output=summary and one with
> --output=messages?  Wouldn't that provide all the needed info?  I guess
> there would still be a race condition, especially for really long search
> results, but I wonder if the calls could actually be made in parallel at
> the same time.  Maybe that would require more work.  Sorry, just
> thinking out loud here...

As you say this doesn't fully solve the race. But more importantly there
are two races: one for * (apply tag change to all matching messages) and
one for tagging singles threads. I don't see how this would help with
the latter. In my use this is the worrying race: I archive a thread to
say I have dealt with it but I may archive a reply which arrived after I
populated the search buffer.

Best wishes

Mark

  parent reply	other threads:[~2012-11-22 19:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-09 18:58 [PATCH 0/3] Outline fix for emacs tagging race Mark Walters
2012-11-09 18:58 ` [PATCH 1/3] test: test for race when tagging from emacs search Mark Walters
2012-11-09 18:58 ` [PATCH 2/3] cli: all search mode to include msg-ids with JSON output Mark Walters
2012-11-22 16:15   ` Jameson Graef Rollins
2012-11-22 18:05     ` Michal Nazarewicz
2012-11-22 19:35     ` Mark Walters [this message]
2012-11-23  7:23       ` Jameson Graef Rollins
2012-11-23  9:01         ` Tomi Ollila
2012-11-23 20:39     ` Austin Clements
2012-11-09 18:58 ` [PATCH 3/3] emacs: make emacs use message-ids for tagging Mark Walters
2012-11-09 21:25 ` [PATCH 0/3] Outline fix for emacs tagging race Tomi Ollila
2012-11-09 23:27 ` David Bremner
2012-11-10  5:29 ` Austin Clements

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=87pq35jus1.fsf@qmul.ac.uk \
    --to=markwalters1009@gmail.com \
    --cc=jrollins@finestructure.net \
    --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).