From: Bob Newell <bobnewell@bobnewell.net>
To: ding@gnus.org
Subject: Re: Saving all the messages in a summary buffer
Date: Fri, 25 Aug 2017 14:33:37 -1000 [thread overview]
Message-ID: <8760db5fry.fsf@bobnewell.net> (raw)
In-Reply-To: <500B2168-35EE-4409-BF52-3298CDAE17A4@verizon.net> (Dave Goldberg's message of "Thu, 24 Aug 2017 21:39:51 -0400")
> Isn't there still a save article to mbox function that respects the
> process mark? Sorry, I'm on vacation with only my phone for email so
> can't check myself.
O m will save process marked articles to an mbox file, prompting for the
filename, and then clearing the process marks.
It's not exactly ideal as it saves everything, every shred of every
header, but I thank the originator of this thread. This is a feature
I've long searched for, and I even started to code my own, but happily
there is no need.
Finding things in Gnus isn't always easy!
--
Bob Newell
Honolulu, Hawai`i
* Via Gnus/BBDB/Org/Emacs/Linux *
next prev parent reply other threads:[~2017-08-26 0:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 21:09 Norman Walsh
2017-08-24 14:57 ` Steinar Bang
2017-08-25 1:39 ` Dave Goldberg
2017-08-26 0:33 ` Bob Newell [this message]
2017-08-26 2:19 ` Bob Newell
2017-08-30 17:07 ` Norman Walsh
2017-08-30 19:53 ` Bob Newell
2017-08-26 0:13 ` Harry Putnam
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=8760db5fry.fsf@bobnewell.net \
--to=bobnewell@bobnewell.net \
--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).