From: <jari.aalto@poboxes.com>
Subject: [patch] 0.37 gnus-article-edit-article fix
Date: 19 Mar 1998 10:47:58 +0200 [thread overview]
Message-ID: <tbiupb3w3l.fsf@styx.tele.nokia.fi> (raw)
[-- Attachment #1: Type: text/plain, Size: 565 bytes --]
I received a PGP message, hwere gnus buttons were added in the middle of
PGP block:
noRr110XVahfo/3MaLL2PGlJ/h8rOdZkJCPCQ1OO8BKcXg3NQWTb+RpqSbSRnbEq
[...]
win0apLYccO+tqhhzK3CIiDbgBGfQLNU9ju+nMOOm1VUfF2A/phMoQg6ucYrXFxk
But I was suprised when I entered edit mode that the buttons were
still there. I would have expected that gnus-original-article-buffer
were offered for me to edit
This patch copies gnus-original-article-buffer to the edit
buffer so that used really edits the original content.
jari
[-- Attachment #2: gnus-art.el.diff --]
[-- Type: application/octet-stream, Size: 937 bytes --]
Prereq: 1.37
===================================================================
RCS file: RCS/gnus-art.el,v
retrieving revision 1.37
retrieving revision 1.38
diff -ubw -r1.37 -r1.38
--- 1.37 1998/03/19 08:21:51
+++ 1.38 1998/03/19 08:41:53
@@ -2620,6 +2620,14 @@
(let ((winconf (current-window-configuration)))
(set-buffer gnus-article-buffer)
(gnus-article-edit-mode)
+ ;;
+ ;; Give user the original article for editing. This
+ ;; *Article* buffer may have been formatted by variaous gnus functions.
+ ;;
+ (delete-region (point-min) (point-max))
+ (unless (buffer-live-p (get-buffer gnus-original-article-buffer))
+ (error "Can't find orginal buffer: %s" gnus-original-article-buffer))
+ (insert-buffer gnus-original-article-buffer)
(gnus-set-text-properties (point-min) (point-max) nil)
(gnus-configure-windows 'edit-article)
(setq gnus-article-edit-done-function exit-func)
next reply other threads:[~1998-03-19 8:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-19 8:47 jari.aalto [this message]
1998-03-19 13:31 ` Lars Magne Ingebrigtsen
1998-03-19 15:59 ` jari.aalto
1998-03-23 13:02 ` Lars Magne Ingebrigtsen
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=tbiupb3w3l.fsf@styx.tele.nokia.fi \
--to=jari.aalto@poboxes.com \
--cc=jari.aalto@ntc.nokia.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).