From: "Steven L. Baur" <steve@miranova.com>
Subject: [sgnus 0.16] Can't decrypt encrypted MIME mail
Date: Sun, 26 Nov 1995 17:28:35 -0800 [thread overview]
Message-ID: <199511270128.RAA25854@miranova.com> (raw)
This appears to be a fairly old one, dating back probably to before my
time, and should affect both Emacsen.
There is a problem with mailcrypt and reading PGP encrypted messages
that are inside of MIME messages. NOTE: This is apparently not
mailcrypt's fault.
The fix for this case is trivial, the function changed is not called
by anything else in Gnus, however it is a global entry point (as
evidenced by its usage in mailcrypt).
===================================================================
RCS file: RCS/ChangeLog,v
retrieving revision 1.4
diff -u -r1.4 ChangeLog
--- 1.4 1995/11/26 22:57:02
+++ ChangeLog 1995/11/27 00:57:10
@@ -1,5 +1,8 @@
Sun Nov 26 14:46:55 1995 Steven L. Baur <steve@diana.miranova.com>
+ * gnus.el (gnus-summary-edit-article): force read of articles
+ that Gnus thinks are pseudos.
+
* gnus.el (gnus-no-server): typo prevented entry to gnus
Sun Nov 26 15:15:29 1995 Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
===================================================================
RCS file: RCS/gnus.el,v
retrieving revision 1.5
diff -u -r1.5 gnus.el
--- 1.5 1995/11/27 00:37:03
+++ gnus.el 1995/11/27 00:37:45
@@ -10344,7 +10344,7 @@
(when (and (not force)
(gnus-group-read-only-p))
(error "The current newsgroup does not support article editing."))
- (gnus-summary-select-article t)
+ (gnus-summary-select-article t t t)
(gnus-configure-windows 'article)
(select-window (get-buffer-window gnus-article-buffer))
(gnus-message 6 "C-c C-c to end edits")
--
steve@miranova.com baur
reply other threads:[~1995-11-27 1:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199511270128.RAA25854@miranova.com \
--to=steve@miranova.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).