Gnus development mailing list
 help / color / mirror / Atom feed
From: Matt Pharr <mmp@Graphics.Stanford.EDU>
Cc: bugs@gnus.org
Subject: Re: yipes! forwarding bug in p0.34
Date: 15 Oct 1998 14:34:12 -700	[thread overview]
Message-ID: <kh0d87tzezv.fsf@lux.Stanford.EDU> (raw)
In-Reply-To: Matt Pharr's message of "13 Oct 1998 09:23:19 -700"


I wrote:
> I just noticed that when forwarding a message in pgnus 0.34, the *mail*
> buffer that comes up has the contents of whatever messages I've already
> forwarded appended to the end of it.  Has anyone else noticed this?

Well that was an easy one to fix.

*** lisp/gnus-msg.el~        Sat Oct 10 17:32:03 1998
--- lisp/gnus-msg.el Thu Oct 15 14:29:51 1998
***************
*** 620,625 ****
--- 620,626 ----
        (set-buffer gnus-original-article-buffer)
        (setq text (buffer-string)))
        (set-buffer (gnus-get-buffer-create " *Gnus forward*"))
+       (erase-buffer)
        (insert text)
        (run-hooks 'gnus-article-decode-hook)
        (let ((message-included-forward-headers

*** lisp/ChangeLog~  Sat Oct 10 17:32:01 1998
--- lisp/ChangeLog   Thu Oct 15 14:31:00 1998
***************
*** 1,3 ****
--- 1,8 ----
+ 1998-10-15  Matt Pharr  <mmp@graphics.stanford.edu>
+ 
+       * gnus-msg.el (gnus-summary-mail-forward): Erase contents of old
+       forward buffer first.
+ 
  Sun Oct 11 02:28:40 1998  Lars Magne Ingebrigtsen  <larsi@menja.ifi.uio.no>
  
        * gnus.el: Pterodactyl Gnus v0.34 is released.

-matt
--
Matt Pharr                                   mmp@graphics.stanford.edu
<URL:http://graphics.stanford.edu/~mmp>


      reply	other threads:[~1998-10-15 21:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-13 16:23 Matt Pharr
1998-10-15 21:34 ` Matt Pharr [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=kh0d87tzezv.fsf@lux.Stanford.EDU \
    --to=mmp@graphics.stanford.edu \
    --cc=bugs@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).