From: Tim Landscheidt <tim@tim-landscheidt.de>
To: help-gnu-emacs@gnu.org
Subject: Multiple summary buffers (was: Gnus: caching message headers?)
Date: Mon, 07 Sep 2020 23:48:37 +0000 [thread overview]
Message-ID: <87y2lldu7e.fsf_-_@passepartout.tim-landscheidt.de> (raw)
In-Reply-To: 874ko9sgcn.fsf@ericabrahamsen.net
Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
> […]
> There's currently no way around this, as Gnus only lets you have one
> active Summary buffer at a time, which means all the old data is dumped
> every time you switch groups. In the back of my head I have some ideas
> for removing this restriction, but it will take a long time to get
> there.
> […]
Just to clarify: I've been using several *Summary* buffers
(for /different/ groups) all the time. Is this not supposed
to work? Or did you mean "Gnus only lets you have one ac-
tive Summary buffer per group at a time?"
Tim
next prev parent reply other threads:[~2020-09-07 23:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 15:23 Gnus: caching message headers? Gregory Heytings via Users list for the GNU Emacs text editor
2020-09-07 16:26 ` Eric Abrahamsen
2020-09-07 17:10 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-09-07 17:37 ` Eric Abrahamsen
2020-09-07 17:49 ` wgreenhouse
2020-09-08 13:19 ` Eric S Fraga
2020-09-08 13:37 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-09-08 14:34 ` Stefan Monnier
2020-09-08 17:29 ` Eric Abrahamsen
2020-09-08 21:52 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-09-08 22:33 ` Stefan Monnier
2020-09-08 16:12 ` wgreenhouse
2020-09-08 20:39 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-09-07 17:50 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-09-07 17:53 ` Eric Abrahamsen
2020-09-07 23:48 ` Tim Landscheidt [this message]
2020-09-08 0:22 ` Multiple summary buffers Eric Abrahamsen
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=87y2lldu7e.fsf_-_@passepartout.tim-landscheidt.de \
--to=tim@tim-landscheidt.de \
--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).