Gnus development mailing list
 help / color / mirror / Atom feed
From: sperber@informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor])
Subject: [BUG & FIX] `nnmail-get-new-mail' fetches too much
Date: 29 Apr 2001 13:19:09 +0200	[thread overview]
Message-ID: <y9lzod00x8y.fsf@informatik.uni-tuebingen.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 395 bytes --]


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.


[-- Attachment #2: Type: text/plain, Size: 202 bytes --]

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.

[-- Attachment #3: Type: text/plain, Size: 422 bytes --]

--- 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)

[-- Attachment #4: Type: text/plain, Size: 72 bytes --]



-- 
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla

             reply	other threads:[~2001-04-29 11:19 UTC|newest]

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

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=y9lzod00x8y.fsf@informatik.uni-tuebingen.de \
    --to=sperber@informatik.uni-tuebingen.de \
    /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).