From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: coding in some mails is wired
Date: Tue, 25 Jul 2023 19:46:07 +0200 [thread overview]
Message-ID: <87351brijk.fsf@mat.ucm.es> (raw)
In-Reply-To: <87lef4jf8a.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]
>>> "RP" == Robert Pluim <rpluim@gmail.com> writes:
>>>>>> On Tue, 25 Jul 2023 14:28:32 +0200, Uwe Brauer <oub@mat.ucm.es> said:
Uwe> If I sent you this message or a similar, in which format? A simple
Uwe> forward would not do, right?
> If you save it to an mbox file, and then tar and gzip it before
> attaching, that should preserve the headers.
Ok gnus offers:
,----
| gnus-default-article-saver is a variable defined in ‘gnus-art.el’.
|
| Its value is ‘gnus-summary-save-in-file’
| Original value was
| ‘gnus-summary-save-in-rmail’
|
| A function to save articles in your favorite format.
| The function will be called by way of the ‘gnus-summary-save-article’
| command, and friends such as ‘gnus-summary-save-article-rmail’.
|
| Gnus provides the following functions:
|
| * gnus-summary-save-in-rmail (Rmail format)
| * gnus-summary-save-in-mail (Unix mail format)
| * gnus-summary-save-in-folder (MH folder)
| * gnus-summary-save-in-file (article format)
| * gnus-summary-save-body-in-file (article body)
| * gnus-summary-save-in-vm (use VM’s folder format)
| * gnus-summary-write-to-file (article format -- overwrite)
| * gnus-summary-write-body-to-file (article body -- overwrite)
| * gnus-summary-save-in-pipe (article format)
`----
Is gnus-summary-save-in-mail better than gnus-summary-save-in-folder?
> Robert
--
Warning: Content may be disturbing to some audiences
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military.
I support the NATO membership of the Ukraine.
I support the EU membership of the Ukraine.
https://addons.thunderbird.net/en-US/thunderbird/addon/gmail-conversation-view/
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2023-07-25 17:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 7:49 Uwe Brauer
2023-07-25 9:57 ` Robert Pluim
2023-07-25 12:28 ` Uwe Brauer
2023-07-25 13:24 ` Robert Pluim
2023-07-25 17:46 ` Uwe Brauer [this message]
2023-07-25 20:49 ` Robert Pluim
2023-07-26 9:03 ` Uwe Brauer
2023-07-26 9:19 ` Eric S Fraga
2023-07-26 10:07 ` Robert Pluim
2023-07-26 10:21 ` Eric S Fraga
2023-07-26 12:16 ` Uwe Brauer
2023-07-26 12:58 ` Robert Pluim
2023-07-26 16:59 ` Uwe Brauer
2023-07-27 7:15 ` Robert Pluim
2023-07-29 5:55 ` Uwe Brauer
2023-07-25 16:21 ` Andreas Schwab
2023-07-25 17:46 ` Uwe Brauer
2023-07-25 17:50 ` Uwe Brauer
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=87351brijk.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=ding@gnus.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).