Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Buffer has a running process when reporting spam to gmane
Date: Fri, 25 Sep 2009 15:58:35 -0500	[thread overview]
Message-ID: <87skeaivwk.fsf@lifelogs.com> (raw)
In-Reply-To: <87ws3qdqzz.fsf@sphax.lybrafox.lan>

On Wed, 23 Sep 2009 10:06:40 +0200 hobbes@poukram.net (Rémi Letot) wrote: 

RL> I use gnus and gmane to read many mailing lists, and report spam
RL> whenever I can. I use gnus as packaged in emacs-snapshot on debian,
RL> which tracks emacs development (latest snapshot from 09/09/2009).

RL> Now I have experienced a small problem for some weeks : whenever I mark
RL> messages as spam in gnus, I have error messages when I quit the group:

RL> Buffer has a running process; kill it? (y or n) 

RL> The number of messages is equal to the number of marked messages. I
RL> answer "n" (multiple times if needed) and apparently the messages are
RL> correctly reported to gmane as shown in the messages buffer:

RL> Exiting summary buffer and applying spam rules
RL> Registering 1 specific articles as spam using backend spam-use-gmane
RL> Reporting article 198 to spam.gmane.org...
RL> Buffer has a running process; kill it? (y or n) 
RL> 1 spam messages were registered by backend spam-use-gmane.

RL> I can't remember when that behaviour started, but don't hesitate to ask
RL> for more information if needed.

I think this may be coming from the function
spam-report-url-ping-plain.  Does anyone know why it doesn't use
`url-retrieve' but instead implements its own version?  Looks like
Reiner did some work on it last, but the original code is vintage Lars :)

Ted




  reply	other threads:[~2009-09-25 20:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23  8:06 Rémi Letot
2009-09-25 20:58 ` Ted Zlatanov [this message]
2009-09-28 15:42   ` Rémi Letot
2009-09-28 19:06     ` Reiner Steib
2009-09-29 19:01       ` Rémi Letot
2009-09-30  2:22         ` Manoj Srivastava

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=87skeaivwk.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.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.
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).