From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: help-gnu-emacs@gnu.org
Subject: Re: Read/process mbox file in Gnus
Date: Mon, 09 Nov 2020 13:40:10 +0000 [thread overview]
Message-ID: <87sg9iir7p.fsf@ucl.ac.uk> (raw)
In-Reply-To: CANc-5Uz49wU_Rw-mi6+dXichiD-BL6cRdgB82ArSUY4QOZ67UQ@mail.gmail.com
On Friday, 6 Nov 2020 at 12:40, Skip Montanaro wrote:
> I was out riding around (new bike day <https://flic.kr/p/2k3WWdr> 😀) and
Nice! :-)
> it occurred to me that the way I am using mbox files is just as a
> transmission tool. [...] I'm going to guess Gnus saves metadata in
> ~/.newsrc.eld. It's not clear how well it would take to me pulling the
> rug out from under it by replacing the previous u.mbox file with a
> completely new one without also somehow performing careful surgery on
> its metadata (assuming I also use it as my normal mail reader).
I would not recommend playing around with .newsrc.eld directly.
However, I'm not sure you need to. If you use the u.mbox file as a
"source", i.e. it's emptied by gnus when read, say into an nnml group,
there won't be any inconsistency. Likewise, your destination mbox files
could be places where you save articles (e.g. using
gnus-summary-save-article, bound to o in the summary view) to and these
will also not be files that gnus will try to keep track of. Whether
they are empty or not when you ask gnus to save an article to such a
file will not matter as it appends to the file.
Note, you'll want to customize gnus-default-article-saver to use your
desired format (gnus-summary-save-in-mail likely).
--
Eric S Fraga via Emacs 28.0.50 & org 9.4 on Debian bullseye/sid
next prev parent reply other threads:[~2020-11-09 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 16:58 Read/process mbox file in Gnus Skip Montanaro
2020-11-06 1:45 ` Eric Abrahamsen
2020-11-06 10:44 ` Robert Pluim
2020-11-06 12:19 ` Eric S Fraga
2020-11-06 13:09 ` Skip Montanaro
2020-11-06 13:27 ` Eric S Fraga
2020-11-06 16:27 ` Eric Abrahamsen
2020-11-06 18:40 ` Skip Montanaro
2020-11-09 13:40 ` Eric S Fraga [this message]
2020-11-06 15:34 ` Colin Baxter
2020-11-06 16:22 ` Robert Pluim
2020-11-06 18:03 ` Colin Baxter
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sg9iir7p.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).