From: Simon Josefsson <jas@extundo.com>
Subject: C-d into nndoc and F yield bad GCC
Date: Thu, 28 Aug 2003 06:07:17 +0200 [thread overview]
Message-ID: <ilu4r02fmru.fsf@latte.josefsson.org> (raw)
If I C-d into a multipart message, e.g., to read a multipart message
with the encrypted parts, and then press F on a part, the GCC header
holds the nndoc group name. I'm using gcc-self. This doesn't work,
the GCC simply fails saying nndoc isn't writable, which is true of
course, and then I lose the GCC. I can save it to nndraft and then
move that article into my archive group, but the MML isn't translated
into MIME then. If someone wants to look into it, I think there are
several problems:
* Gcc-self in a C-d nndoc group should gcc the original group.
* When Gcc fails, there should be some way to get to the MML
translated message. Perhaps save the Gcc prepared message into
nndraft and inform the user?
(* I wouldn't have discovered this problem if the gnus-uu code were
invoked on each textual MIME part, thus rendering inlined PGP
parts. But this is a known problem.)
next reply other threads:[~2003-08-28 4:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 4:07 Simon Josefsson [this message]
2003-10-17 18:31 ` 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=ilu4r02fmru.fsf@latte.josefsson.org \
--to=jas@extundo.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).