Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Norman Walsh <ndw@nwalsh.com>
Cc: ding@gnus.org
Subject: Re: Debugging split errors
Date: Sat, 13 Jul 2019 15:13:14 +0200	[thread overview]
Message-ID: <m3y312oz6d.fsf@gnus.org> (raw)
In-Reply-To: <m2sgrbvtud.fsf@nwalsh.com> (Norman Walsh's message of "Fri, 12 Jul 2019 16:14:18 -0500")

Norman Walsh <ndw@nwalsh.com> writes:

> Are there any debugging or trace flags I can turn on to get some
> feedback about what happened?

There aren't really, unfortunately...  You can set
`nnmail-split-tracing' and that'll put stuff in `nnmail-split-trace, but
that's not really that easy to deal with...

Hm...  I think having a real trace log on the splitting would be
generally useful, so I think I'll just add that.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2019-07-13 13:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12 21:14 Norman Walsh
2019-07-13 13:13 ` Lars Ingebrigtsen [this message]
2019-07-13 13:24   ` Lars Ingebrigtsen
2019-07-13 17:15     ` Eric S Fraga

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3y312oz6d.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@gnus.org \
    --cc=ndw@nwalsh.com \
    /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.
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 NNTP newsgroup(s).