From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Christoph Groth <christoph@grothesque.org>
Cc: info-gnus-english@gnu.org
Subject: Re: Reply to attached message
Date: Tue, 20 Jul 2021 14:51:04 -0700 [thread overview]
Message-ID: <87o8awodrr.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87im141xlj.fsf@drac> (Christoph Groth's message of "Tue, 20 Jul 2021 23:31:20 +0200")
Christoph Groth <christoph@grothesque.org> writes:
> Eric Abrahamsen wrote:
>
>> Christoph Groth <christoph@grothesque.org> writes:
>
>> > I wonder if there is a way in Gnus to reply to a message that has
>> > been forwarded as a MIME attachment.
>>
>> How does the message appear in the Gnus message? What happens when you
>> hit "K v" (gnus-article-view-part) on it?
>
> It appears inline with colored headers, so Gnus does recognize it as
> a message. But I cannot find a convenient way to open the attached
> message in a separate message buffer so that message commands would work
> on it.
Huh, so it inlines by default. What's the MIME type on the attachment?
Since people can already "K i" to explicitly inline, it seems like it
would make sense to have "K v" put the message in a separate buffer in
`gnus-article-mode'.
> Here is one way that does work, but it is a bit clumsy:
>
> (1) Save the attachment to a file.
>
> (2) Create a group from that file (G f).
>
> (3) Open that group and reply to the message.
Yes, that was going to be my original suggestion, but it's not a great
solution and I figured you'd already done that!
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2021-07-20 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 21:10 Christoph Groth
2021-07-20 21:17 ` Eric Abrahamsen
2021-07-20 21:31 ` Christoph Groth
2021-07-20 21:51 ` Eric Abrahamsen [this message]
2021-07-20 23:12 ` Dan Christensen
2021-07-22 21:33 ` Christoph Groth
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=87o8awodrr.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=christoph@grothesque.org \
--cc=info-gnus-english@gnu.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).