Gnus development mailing list
 help / color / mirror / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: emacs-devel@gnu.org, asjo@koldfront.dk
Cc: ding@gnus.org
Subject: Re: Rendering regression in Gnus with gnus-treat-from-gravatar
Date: Sat, 11 Apr 2020 16:15:04 +0200	[thread overview]
Message-ID: <m2zhbip0rb.fsf@gmail.com> (raw)
In-Reply-To: <877dym5fes.fsf@tullinup.koldfront.dk> ("Adam =?utf-8?B?U2o=?= =?utf-8?B?w4PCuGdyZW4=?= via \"Emacs development discussions."'s message of "Sat, 11 Apr 2020 15:18:51 +0200")

>>>>> On Sat, 11 Apr 2020 15:18:51 +0200, "Adam Sjøgren via \"Emacs development discussions." <emacs-devel@gnu.org> said:

    Adam> A recent change in Emacs has made rendering of articles in Gnus on my
    Adam> machine noticably slower: uncolored headers flash before the article is
    Adam> shown in the final rendering.

    Adam> I have bisected the problem, and this seems to be the cause:

    Adam>   421eeff243af683bf0b7c6d9181650a1c6900f9b is the first bad commit
    Adam>   commit 421eeff243af683bf0b7c6d9181650a1c6900f9b
    Adam>   Author: Philip K <philip@warpmail.net>
    Adam>   Date:   Tue Mar 17 15:29:53 2020 +0100

    Adam>       Add support for multiple Gravatar services

    Adam>       Now supports Libravatar and Unicornify, next to Gravatar (Bug#39965).

The new version doesnʼt do any more gravatar lookups than the old one,
but it does by default do some DNS lookups. Is it better if you
customize 'gravatar-service' to one of the other options? If so, Iʼll
have to pay some attention to Philip K's caching patch for this
feature.

Robert



       reply	other threads:[~2020-04-11 14:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <877dym5fes.fsf@tullinup.koldfront.dk>
2020-04-11 14:15 ` Robert Pluim [this message]
2020-04-11 15:16   ` Adam Sjøgren
2020-04-11 16:53     ` Robert Pluim
2020-04-14 13:14       ` Robert Pluim
2020-04-14 15:46         ` Eli Zaretskii
2020-04-14 17:32         ` Adam Sjøgren
2020-04-15  8:15           ` Robert Pluim
2020-04-15  9:41             ` Eli Zaretskii
2020-04-15 10:13               ` Robert Pluim
2020-04-15 11:38                 ` Eli Zaretskii
2020-04-15 11:55                   ` Robert Pluim
2020-04-15 12:01                     ` Eli Zaretskii
2020-04-15 13:54                       ` Robert Pluim
2020-04-15 14:12                         ` Eli Zaretskii
2020-04-15 14:20                           ` Robert Pluim
2020-04-22 14:25       ` Tassilo Horn
2020-04-22 14:39         ` Tassilo Horn
2020-04-22 14:56           ` Robert Pluim
2020-04-22 17:32             ` Tassilo Horn
2020-04-22 14:59         ` Robert Pluim
2020-04-22 17:01           ` Tassilo Horn
2020-04-22 17:23             ` Robert Pluim

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=m2zhbip0rb.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=asjo@koldfront.dk \
    --cc=ding@gnus.org \
    --cc=emacs-devel@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).