unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Ralph Seichter <abbot@monksofcool.net>, notmuch@notmuchmail.org
Subject: Re: Unexpected output of "notmuch new --quiet"
Date: Thu, 18 Apr 2019 22:13:25 -0300	[thread overview]
Message-ID: <877ebqg5l6.fsf@tethera.net> (raw)
In-Reply-To: <87ftqfctf0.fsf@ra.horus-it.com>

Ralph Seichter <abbot@monksofcool.net> writes:

> * David Bremner:
>
>> I guess if you have a simple way of distinguishing the cases which you
>> want to consider as errrors, we can revisit the idea.
>
> Personally, I'd go with these decreasing levels of severity:
[snip]
> I don't know if this is a fit for Notmuch, but it would be great if I
> could prevent warnings and notices from being reported by using a
> command line option.
>

Just to be clear, I was referring in the question of deciding for
specific messages, which ones are serious and which ones are not. Are
there warnings that you want to suppress that are not handleable with
the new.ignore facility?

d

  reply	other threads:[~2019-04-19  1:13 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
2019-04-18 13:29     ` David Bremner
2019-04-18 13:52       ` Ralph Seichter
2019-04-19  1:13         ` David Bremner [this message]
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=877ebqg5l6.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=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).