unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 58302@debbugs.gnu.org
Subject: bug#58302: 29.0.50; browse-url-emacs is extremely slow (and I think always has been?)
Date: Wed, 12 Oct 2022 13:03:59 +0200	[thread overview]
Message-ID: <8735bte21s.fsf@gnus.org> (raw)
In-Reply-To: <d3c5f2c00773da6c4148c4f29fe6a29e@webmail.orcon.net.nz> (Phil Sainty's message of "Wed, 12 Oct 2022 23:25:52 +1300")

Phil Sainty <psainty@orcon.net.nz> writes:

> I'm not very familiar with the ins and outs of these code paths,
> but my first impression is that we've initiated an operation which
> needs to deal with a particular URL and if we were to make a high-
> level binding to indicate that we were doing this, we could then
> cache and re-use the results of those network requests for the
> extent of that binding.

[excellent analysis elided]

I think the conclusion here is that using the file-name-handler-alist
stuff for this is the absolutely pessimal way to implement
`browse-url-emacs'.

It should be pretty easy to rewrite browse-url-emacs to just call
`url-retrieve-synchronously' explicitly, and then display the resulting
data -- and it should be much, much faster.






  reply	other threads:[~2022-10-12 11:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 11:07 bug#58302: 29.0.50; browse-url-emacs is extremely slow (and I think always has been?) Phil Sainty
2022-10-06 12:53 ` Lars Ingebrigtsen
2022-10-06 23:25   ` Phil Sainty
2022-10-07 11:48     ` Lars Ingebrigtsen
2022-10-07  2:47   ` Phil Sainty
2022-10-12 10:25     ` Phil Sainty
2022-10-12 11:03       ` Lars Ingebrigtsen [this message]
2022-10-12 11:28         ` Phil Sainty
2022-10-12 11:33           ` Lars Ingebrigtsen
2022-10-13  8:01             ` Lars Ingebrigtsen

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=8735bte21s.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=58302@debbugs.gnu.org \
    --cc=psainty@orcon.net.nz \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).