Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: gnus 5.6.11
Date: 05 Jun 1998 11:38:34 +0200	[thread overview]
Message-ID: <kigyavc1945.fsf@jagor.srce.hr> (raw)
In-Reply-To: <glmogw9usad.fsf@caffeine.mitre.org>

Justin Sheehy <justin@linus.mitre.org> writes:

> Rolf Marvin B|e Lindgren <roffe@morgoth.uio.no> writes:
> 
> > suddenly, Gnus merges all my mail, from all my mail spools, into
> > nnml+private:mail.misc.  
> 
> This is rather serious, and seems to have hit lots of people.  On
> first look, it seems that the only change that could have caused it
> is the new regexp-quoting in nnmail.el.

I introduced the new regexp-quoting (Gnus failed on Windows without
it), so I feel responsible.  Although the changes are generally fine,
I see one that's not.  Try this patch:


1998-06-05  Hrvoje Niksic  <hniksic@srce.hr>

	* nnmail.el (nnmail-get-split-group): Don't regexp-quote
 	nnmail-procmail-suffix.

--- nnmail.el.orig	Fri Jun  5 11:37:23 1998
+++ nnmail.el	Fri Jun  5 11:37:34 1998
@@ -722,7 +722,7 @@
 				      (file-name-as-directory
 				       nnmail-procmail-directory)))
 				"\\([^/]*\\)"
-				(regexp-quote nnmail-procmail-suffix) "$")
+				nnmail-procmail-suffix "$")
 			(expand-file-name file))
 	  (let ((procmail-group (substring (expand-file-name file)
 					   (match-beginning 1)


-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
By any chance, have you seen a summoned 9th order fire elemental
wandering around?  No?  Oh..  Tell me if you do.


  reply	other threads:[~1998-06-05  9:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-06-04  4:26 Rolf Marvin B|e Lindgren
1998-06-04 14:59 ` Justin Sheehy
1998-06-05  9:38   ` Hrvoje Niksic [this message]
1998-06-05 15:59     ` Justin Sheehy
1998-06-09  6:02     ` Rolf Marvin B|e Lindgren
1998-06-09 11:45       ` Hrvoje Niksic
1998-06-24  1:05     ` Lars Magne Ingebrigtsen
1998-06-04 18:44 ` Bruce Stephens

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=kigyavc1945.fsf@jagor.srce.hr \
    --to=hniksic@srce.hr \
    /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).