From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: useful things with nnselect
Date: Fri, 11 Sep 2020 09:25:33 +0100 [thread overview]
Message-ID: <87een890ua.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87mu1x5gjj.fsf@ust.hk>
On Friday, 11 Sep 2020 at 08:00, Andrew Cohen wrote:
> The only thing that is slow is retrieving a huge number of headers and
> processing them (e.g. threading) to create the summary buffer.
This makes sense. Thank you.
--
Eric S Fraga via Emacs 28.0.50 & org 9.3.7 on Debian bullseye/sid
prev parent reply other threads:[~2020-09-11 8:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 1:41 Andrew Cohen
2020-09-09 3:05 ` Eric Abrahamsen
2020-09-09 3:26 ` Andrew Cohen
2020-09-09 18:12 ` Eric Abrahamsen
2020-09-09 6:23 ` Eric S Fraga
2020-09-09 6:41 ` Andrew Cohen
2020-09-09 11:31 ` Eric S Fraga
2020-09-11 0:00 ` Andrew Cohen
2020-09-11 8:25 ` Eric S Fraga [this message]
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=87een890ua.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).