From: Adrian Perez de Castro <aperez@igalia.com>
To: notmuch@notmuchmail.org
Subject: Re: [PATCH] Support for printing file paths in new command
Date: Mon, 23 Nov 2009 01:53:39 +0100 [thread overview]
Message-ID: <20091123015339.79e51228@hikari> (raw)
In-Reply-To: <87r5rqks0m.fsf@yoom.home.cworth.org>
[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]
On Mon, 23 Nov 2009 01:24:09 +0100, Carl wrote:
> On Sat, 21 Nov 2009 01:17:18 +0100, Adrian Perez <aperez@igalia.com> wrote:
> > For very large mail boxes, it is desirable to know which files are being
> > processed e.g. when a crash occurs to know which one was the cause. Also,
> > it may be interesting to have a better idea of how the operation is
> > progressing when processing mailboxes with big messages.
> >
> > This patch adds support for printing messages as they are processed by
> > "notmuch new":
>
> Hey, that's pretty nice.
Thanks!
As a small improvement, I will send another patch in a while, which will
avoid sending ANSI escapes when output is not a terminal, and print one
file path per line in that case.
> I've pushed this now, (and I'm almost tempted to make it the
> default...).
IMHO it would be nice to have the messages-per-second information as
well in verbose mode before making it the default. I think I could cook
up a patch for that, but printing messages-per-second would mean calling
gettimeofday() for each processed file. Do you think that will be
acceptable from a performance POV? (Of course using silent mode would
still only call it once per second).
Regards,
--
Adrian Perez de Castro <aperez@igalia.com>
Igalia - Free Software Engineering
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-11-23 0:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 0:17 [PATCH] Support for printing file paths in new command Adrian Perez
2009-11-23 0:10 ` Adrian Perez
2009-11-23 0:24 ` Carl Worth
2009-11-23 0:53 ` Adrian Perez de Castro [this message]
2009-11-23 5:00 ` Carl Worth
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=20091123015339.79e51228@hikari \
--to=aperez@igalia.com \
--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).