unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: Stefan Monnier <monnier-CRDzTM1onBSWkKpYnGOUKg@public.gmane.org>
Cc: 20610-ubl+/3LiMTaZdePnXv/OxA@public.gmane.org
Subject: bug#20610: 25.0.50; Gnus fancy mail splitting not working anymore
Date: Tue, 19 May 2015 19:57:47 +0200	[thread overview]
Message-ID: <86oalglaas.fsf@example.com> (raw)
In-Reply-To: <jwviobojwsf.fsf-monnier+emacsbugs-mXXj517/zsQ@public.gmane.org> (Stefan Monnier's message of "Tue, 19 May 2015 13:35:24 -0400")

Stefan Monnier <monnier-CRDzTM1onBSWkKpYnGOUKg@public.gmane.org> writes:
>> While "fancy mail splitting" (section 6.4.6 of the manual) with the
>> `gnus-private' attribute of BBDB [1] works perfectly -- for years! --
>> under (Windows) Emacs 24.5 (and many previous versions), it stops
>> working when using Emacs 25.0.50 [2]... while (let's be explicit!) the
>> `.gnus' file stays strictly the same.
>
> Few!  I was afraid that at this point you'd give us the actual error
> message!

I wish I could, but there isn't:

--8<---------------cut here---------------start------------->8---
...
nnimap read 10k from mail
Reading active file via nndraft...done
Checking new news...done
...
--8<---------------cut here---------------end--------------->8---

Not even a message about splitting.

The only visible difference is that, under 24.5, it does apply the
splitting rules, and it does not under 25.0.

Now, if there is a mean to get more verbose output, or something in the
same vein, I'm (of course) willing to try...

Best regards,
  Seb





  parent reply	other threads:[~2015-05-19 17:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 12:40 bug#20610: 25.0.50; Gnus fancy mail splitting not working anymore Sebastien Vauban
2015-05-19 17:35 ` Stefan Monnier
     [not found]   ` <jwviobojwsf.fsf-monnier+emacsbugs-mXXj517/zsQ@public.gmane.org>
2015-05-19 17:57     ` Sebastien Vauban [this message]
2015-05-19 18:39       ` Stefan Monnier
2015-05-20  0:22         ` Katsumi Yamaoka
     [not found]         ` <mailman.3294.1432081389.904.bug-gnu-emacs@gnu.org>
     [not found]           ` <868uckoi50.fsf-hcDgGtZH8xNBDgjK7y7TUQ@public.gmane.org>
2015-05-21 11:51             ` Sebastien Vauban
2015-07-24 14:49             ` Sebastien Vauban
     [not found]           ` <mailman.3370.1432209128.904.bug-gnu-emacs@gnu.org>
     [not found]             ` <mailman.3370.1432209128.904.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2015-05-22 21:36               ` Sebastien Vauban
     [not found]             ` <mailman.3483.1432330630.904.bug-gnu-emacs@gnu.org>
2015-07-24 12:46               ` Sebastien Vauban
2016-10-14 10:33 ` bug#20610: 25.1.1 " Gijs Hillenius

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=86oalglaas.fsf@example.com \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=20610-ubl+/3LiMTaZdePnXv/OxA@public.gmane.org \
    --cc=monnier-CRDzTM1onBSWkKpYnGOUKg@public.gmane.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://git.savannah.gnu.org/cgit/emacs.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).