unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Ralph Seichter <abbot@monksofcool.net>
To: notmuch@notmuchmail.org
Subject: Re: Unexpected output of "notmuch new --quiet"
Date: Thu, 18 Apr 2019 15:15:14 +0200	[thread overview]
Message-ID: <87y3471ml9.fsf@ra.horus-it.com> (raw)
In-Reply-To: <87bm14gqib.fsf@tethera.net>

* David Bremner:

> I could imagine more levels of quiet, but I don't know if it is worth
> the trouble.

I currently redirect stderr to /dev/null because the actual number of
these "ignoring non-mail file" notices is much higher, but that means I
don't get to see actual errors which is quite a disadvantage.

An option like --veryquiet or --errorsonly would be helpful, but I can
understand you asking if it would be worth the effort. For somebody like
me who uses Dovecot as a backend it would be. ;-)

> Could it maybe a wrapper script or hook invoked by notmuch new?

Ah! The post-new hook called umask and caused the output. Thanks.

-Ralph

  reply	other threads:[~2019-04-18 13:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17 20:38 Unexpected output of "notmuch new --quiet" Ralph Seichter
2019-04-17 23:29 ` David Bremner
2019-04-18 13:15   ` Ralph Seichter [this message]
2019-04-18 13:29     ` David Bremner
2019-04-18 13:52       ` Ralph Seichter
2019-04-19  1:13         ` David Bremner
2019-04-19 11:47           ` Ralph Seichter
2019-04-19 12:02             ` Ralph Seichter
2019-04-19 16:25               ` David Bremner
2019-04-19 23:35                 ` Ralph Seichter
2019-04-19  7:03         ` Daniel Kahn Gillmor
2019-04-19 13:55           ` Ralph Seichter
2019-04-19 16:02             ` Daniel Kahn Gillmor
2019-04-19 23:28               ` David Bremner
2019-04-19 23:46               ` Ralph Seichter
2019-04-20 10:45                 ` Eric
2019-04-20 13:21                   ` Ralph Seichter
2019-04-20 14:19                     ` David Bremner
2019-04-20 14:28                       ` Ralph Seichter

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=87y3471ml9.fsf@ra.horus-it.com \
    --to=abbot@monksofcool.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).