Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <simon@josefsson.org>
Cc: ding@gnus.org
Subject: Re: more on accessing the body via split rules...
Date: 18 May 2001 23:07:29 +0200	[thread overview]
Message-ID: <iluheyi9xim.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <vaf66eycvrr.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "18 May 2001 21:16:56 +0200")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> > Right, it would make sense to me that the
> > gnus-original-article-buffer variable should be updated during
> > splitting, and set back to the previous value after splitting is
> > done.
> > 
> > how does that sound?
> 
> I think that's not the right buffer, for gnus-original-article-buffer
> is used when _displaying_ a message, not during splitting.  That is,
> if you look at the *Article* buffer then you see a munged copy of the
> contents of the original article buffer.
> 
> Maybe introduce a new variable nnmail-original-message-buffer?

Yes, g-o-a-b is definitely wrong.  How about this?

	* nnmail.el (nnmail-incoming-buffer): New variable.
	(nnmail-split-incoming): Use it.

--- nnmail.el.~6.13.~	Sun May  6 02:15:16 2001
+++ nnmail.el	Fri May 18 23:00:36 2001
@@ -450,6 +450,8 @@
 (defvar nnmail-split-tracing nil)
 (defvar nnmail-split-trace nil)
 
+(defvar nnmail-incoming-buffer " *nnmail incoming*")
+
 \f
 
 (defconst nnmail-version "nnmail 1.0"
@@ -896,7 +898,7 @@
 				nnmail-split-methods)))
     (save-excursion
       ;; Insert the incoming file.
-      (set-buffer (get-buffer-create " *nnmail incoming*"))
+      (set-buffer (get-buffer-create nnmail-incoming-buffer))
       (erase-buffer)
       (let ((coding-system-for-read nnmail-incoming-coding-system))
 	(mm-insert-file-contents incoming))



  parent reply	other threads:[~2001-05-18 21:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-18 15:15 Josh Huber
2001-05-18 15:37 ` Josh Huber
2001-05-18 16:12   ` Kai Großjohann
2001-05-18 16:33     ` Josh Huber
2001-05-18 16:56       ` Kai Großjohann
2001-05-18 18:58         ` Josh Huber
2001-05-18 19:16           ` Kai Großjohann
2001-05-18 20:35             ` Josh Huber
2001-05-18 22:44               ` Kai Großjohann
2001-05-18 21:07             ` Simon Josefsson [this message]
2001-05-18 22:43               ` Kai Großjohann
2001-05-19  8:58                 ` Simon Josefsson
2001-05-19 11:20                   ` Kai Großjohann
2001-05-21 14:08                     ` Josh Huber
2001-05-21 14:30                       ` Kai Großjohann
2001-05-21 14:34                         ` Josh Huber
2001-05-21 17:29                       ` Simon Josefsson
2001-05-21 18:15                         ` Josh Huber

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=iluheyi9xim.fsf@barbar.josefsson.org \
    --to=simon@josefsson.org \
    --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).