From: Tim Landscheidt <tim@tim-landscheidt.de>
To: info-gnus-english@gnu.org
Subject: How to copy "raw", but decoded article body to a new buffer?
Date: Sat, 23 Nov 2019 11:35:15 +0000 [thread overview]
Message-ID: <87mucmbzbg.fsf@passepartout.tim-landscheidt.de> (raw)
Hi,
(for example) cron sends me programs' outputs with the head-
ers:
| MIME-Version: 1.0
| Content-Type: text/plain; charset=UTF-8
I want to copy the output to a new buffer and then do some
stuff there.
O b (gnus-summary-save-article-body-file) will a) save the
article body "washed", i. e. for example word-wrapped &
Co. and b) prepend "X-Gnus-Coding-System: -*- coding: utf-8;
-*-" (?).
C-o (gnus-summary-save-article-mail) will a) save the head-
ers as well and b) not decode the body (which is probably
not a problem for "text/plain; charset=UTF-8", but still).
(O f (gnus-summary-save-article-file) seems to be doing the
same as O b, o (gnus-summary-save-article) the same as C-o.)
Both commands have the disadvantage of saving the article to
a file which I have to then visit, edit, save, delete in-
stead of just creating a new buffer.
How can I copy the "raw", but decoded article body to a new
buffer?
TIA,
Tim
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next reply other threads:[~2019-11-23 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 11:35 Tim Landscheidt [this message]
2019-11-23 12:08 ` Lars Ingebrigtsen
2019-11-24 15:59 ` Tim Landscheidt
2019-11-24 21:19 ` Štěpán Němec
2019-11-24 22:29 ` Tim Landscheidt
2019-12-02 8:08 ` Tim Landscheidt
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=87mucmbzbg.fsf@passepartout.tim-landscheidt.de \
--to=tim@tim-landscheidt.de \
--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).