Gnus development mailing list
 help / color / mirror / Atom feed
From: Norman Walsh <ndw@nwalsh.com>
Cc: Norman Walsh <ndw@nwalsh.com>
Subject: nnmail-split bug?
Date: Fri, 20 Nov 1998 09:50:35 -0500	[thread overview]
Message-ID: <5251-Fri20Nov1998095035-0500-ndw@nwalsh.com> (raw)

In an effort to get more complete threads, I've started to CC
myself on mail. I want these messages to go into the right
folder, regardless of what split criteria got the initial
message into its folder. So I added a header (you can see it
above, I'm sure)

  X-local-group-name: 

and I stick the name of the group that's active when I'm sending mail
onto that header.

Then I added the following rule to the beginning of my
nnmail-split-methods:

	("\\1" 
	 			"^X-local-group-name: \\(.*\\)")

Problem is, when this rule fires, gnus goes "bang".

Q1. Is there a better way to achieve what I'm after?

Q2. Here's the debug backtrace.  Any ideas how to fix it?  Is it user
    error?  This is 5.6.43 under Emacs 19.34.6 on NT.

Signaling: (args-out-of-range 685 730)
  replace-match("\\1" nil nil "\\1")
  nnmail-article-group(nnml-active-number)
  nnmail-check-duplication("<9176-Fri20Nov1998093858-0500-nwalsh@arbortext.com>" nnml-save-mail nnml-active-number)
  nnmail-process-unix-mail-format(nnml-save-mail nnml-active-number)
  nnmail-split-incoming("~/.gnus-crash-box" nnml-save-mail nil "mail.misc" nnml-active-number)
  nnmail-get-new-mail(nnml nnml-save-nov "~/Mail/" "mail.misc")
  nnml-request-scan("mail.misc" "")
  gnus-request-scan("nnml:mail.misc" (nnml ""))
  gnus-activate-group("nnml:mail.misc" scan)
  gnus-get-unread-articles(2)
  gnus-group-get-new-news(2)
  call-interactively(gnus-group-get-new-news)



             reply	other threads:[~1998-11-20 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-20 14:50 Norman Walsh [this message]
1998-11-20 15:34 ` Kai.Grossjohann

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=5251-Fri20Nov1998095035-0500-ndw@nwalsh.com \
    --to=ndw@nwalsh.com \
    /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).