Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: [BUG & FIX] `nnmail-get-new-mail' fetches too much
Date: 29 Apr 2001 08:38:06 -0400	[thread overview]
Message-ID: <2ng0er6fv5.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <y9lzod00x8y.fsf@informatik.uni-tuebingen.de> (sperber@informatik.uni-tuebingen.de's message of "29 Apr 2001 13:19:09 +0200")

sperber@informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes:

> Here's a longstanding bug in Gnus, still present in Oort 0.02:
> 
> I have a group nnml:cvs with associated spool file
> ~/incoming/cvs.spool.  I also have a spool file called
> ~/incoming/freebsd-ports-cvs.spool with no associated group.
> 
> Getting new mail for nnml:cvs also slurps the freebsd-ports-cvs.spool
> file into a non-existent nnml group because they share a suffix.
> 
> Bad juju.  Here's a fix.
> 
> 2001-04-29  Michael Sperber [Mr. Preprocessor]  <sperber@informatik.uni-tuebingen.de>
> 
> 	* nnmail.el (nnmail-get-new-mail): Make the generated predicate
> 	more strict to avoid reading in spurious spools.
> --- lisp/nnmail.el.orig	Fri Apr 13 17:57:45 2001
> +++ lisp/nnmail.el	Sun Apr 29 13:13:30 2001
> @@ -1568,9 +1568,10 @@
>  				  `(lambda (file)
>  				     (string-match
>  				      ,(concat
> +					"^"
>  					(regexp-quote (concat group suffix))
>  					"$")
> -				      file)))))))
> +				      (file-name-nondirectory file))))))))
>  	(when nnmail-fetched-sources
>  	  (if (member source nnmail-fetched-sources)
>  	      (setq source nil)

Thanks for the report.  I fix it by using string-equal instead.

ShengHuo


      reply	other threads:[~2001-04-29 12:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-29 11:19 Michael Sperber [Mr. Preprocessor]
2001-04-29 12:38 ` ShengHuo ZHU [this message]

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=2ng0er6fv5.fsf@tiger.jia.vnet \
    --to=zsh@cs.rochester.edu \
    /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).