Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: info-gnus-english@gnu.org
Subject: Re: slow saving of scores when leaving a virtual (nnml+) group
Date: Sun, 09 Jul 2023 07:23:17 +0200	[thread overview]
Message-ID: <871qhhfyka.fsf@web.de> (raw)
In-Reply-To: <87h6qepz01.fsf@ucl.ac.uk>

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> > And - is it worth the time to pretty print this data at all?
>
> This is what I was wondering.  The pretty printing could be saved for
> when somebody wishes to edit the scores, at which point a little delay
> is not intrusive (or as intrusive).  Most of the time, I just want the
> scores updated quickly so I can go on to the next group.

And you did not just turn on `gnus-adaptive-pretty-print' by accident?

Michael.



  reply	other threads:[~2023-07-09  5:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 11:45 Eric S Fraga
2023-07-06 15:43 ` Eric Abrahamsen
2023-07-07  7:05   ` Eric S Fraga
2023-07-07 15:41     ` Eric Abrahamsen
2023-07-08  8:52       ` Eric S Fraga
2023-07-08  1:22   ` Michael Heerdegen
2023-07-08  8:51     ` Eric S Fraga
2023-07-09  5:23       ` Michael Heerdegen [this message]
2023-07-10 15:41         ` Eric S Fraga
2023-07-11  2:56           ` Michael Heerdegen
2023-07-11  9:18             ` Eric S Fraga
2023-07-12  0:48               ` Michael Heerdegen
2023-07-12 10:08                 ` Eric S Fraga
2023-07-13  0:18                   ` Michael Heerdegen
2023-07-13 12:14                     ` Eric S Fraga
2023-07-13 23:56                       ` Michael Heerdegen
2023-07-14 11:05                         ` Eric S Fraga
2023-07-16  2:55                           ` Michael Heerdegen
2023-07-17  7:32                             ` Eric S Fraga
2023-07-18  6:16                               ` Michael Heerdegen

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=871qhhfyka.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=info-gnus-english@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 NNTP newsgroup(s).