all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Karl Fogel <kfogel@red-bean.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Better error reporting in Gnus splitting.
Date: Wed, 19 Jul 2006 10:27:49 -0500	[thread overview]
Message-ID: <87r70hiphm.fsf@floss.red-bean.com> (raw)
In-Reply-To: <v94pxevwn9.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Wed, 19 Jul 2006 10:14:50 +0200")

Reiner Steib <reinersteib+gmane@imap.cc> writes:
> On Wed, Jul 19 2006, Karl Fogel wrote:
>
>> Any objections if I commit this patch?
>
> I don't see a problem with it.  Anyone?
>
>> Without this patch, when splitting encounters an error (say, an
>> invalid regular expression) in the nnmail-split-fancy list, then the
>> user is simply told that there is an error, but is given no details
>> about the error's nature.  The mail gets split into the 'bogus' mail
>> group, and the user has no idea why.
>>
>> With this patch, the user is informed about the general nature of the
>> error and may then be able to track it down.  (The error report could
>> theoretically be even more informative than this, but I didn't want to
>> make a large change.)  
>
> Would you like to post this version too?

Oh, I don't have that version -- I just traced far enough in the code
to know that it's possible.  Unfortunately, I don't have time to write
it right now, hence this smaller patch (which is likely to be a subset
of the larger one anyway).

-Karl

  reply	other threads:[~2006-07-19 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-18 23:49 [PATCH] Better error reporting in Gnus splitting Karl Fogel
2006-07-19  8:08 ` Reiner Steib
2006-07-19  8:14 ` Reiner Steib
2006-07-19 15:27   ` Karl Fogel [this message]
2006-07-20  2:24 ` Karl Fogel
2006-07-20  4:37   ` Miles Bader
2006-07-20 15:28   ` Stefan Monnier

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=87r70hiphm.fsf@floss.red-bean.com \
    --to=kfogel@red-bean.com \
    --cc=emacs-devel@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.