From: YUE Daian <sheepduke@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Make emacs-eww render asynchronously
Date: Wed, 20 Mar 2019 12:31:19 +0800 [thread overview]
Message-ID: <87tvfycgko.fsf@work.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <5c9132a1.1c69fb81.b855.49c7SMTPIN_ADDED_BROKEN@mx.google.com>
On 2019-03-19 11:10, Vladimir Sedach <vas@oneofus.la> wrote:
>> The emacs-w3m fetches the page asynchronously, but the rendering process
>> will freeze Emacs for a long time.
>
> Yes, this is an actual problem. Óscar Fuentes probably does not
> notice it because he must have a fast computer - if you are hacking
> elisp code it is a good idea to do it on old slow hardware. I find
> that profiler.el is not very useful for discovering things that cause
> lag and latency. In case anyone is reading this and thinking "get off
> your heirloom VAX grandpa, here is a nickel, buy a better computer,"
> there is no reason for computers with gigahertz-plus CPUs and a
> gigabyte of memory to end up in the landfill, even if they are 10+
> years old. And work on performance issues caused by sloppy code and
> bad algorithms/data structures will benefit all GNU Emacs users.
>
>> Is it a way to make emacs-w3m render pages asynchronously?
>
> The cause of the problem will not be fixed by asynchronous rendering.
> emacs-w3m code has some real problems and is doing a lot of
> unnecessary work.
>
> If you would like to contribute to emacs-w3m, the details for
> subscribing to the emacs-w3m mailing list can be found at:
> http://emacs-w3m.namazu.org/
>
> The source code repository is now at:
> https://github.com/emacs-w3m/emacs-w3m
>
>> Or should I start to use eww exclusively instead of emacs-w3m?
>
> You can do both. It is probably easier to add features and w3m-style
> rendering to eww than to fix emacs-w3m.
>
> Vladimir
Maybe you are right. IMHO emacs-w3m is not easy to hack.
Then the question would become "how to make eww fetch pages
asynchronously." ;-)
prev parent reply other threads:[~2019-03-20 4:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 4:48 Make emacs-eww render asynchronously YUE Daian
2019-03-19 15:11 ` Óscar Fuentes
2019-03-19 18:10 ` Vladimir Sedach
2019-03-19 19:13 ` Stefan Monnier
2019-03-19 19:26 ` Óscar Fuentes
2019-03-19 19:04 ` Stefan Monnier
2019-03-19 19:31 ` Óscar Fuentes
[not found] ` <87zhpqn3af.fsf@exinda.orion.oneofus.la.>
2019-03-19 19:35 ` Eli Zaretskii
2019-03-20 7:03 ` Vladimir Sedach
2019-03-20 14:04 ` Stefan Monnier
[not found] ` <5c9132a1.1c69fb81.b855.49c7SMTPIN_ADDED_BROKEN@mx.google.com>
2019-03-20 4:31 ` YUE Daian [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
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=87tvfycgko.fsf@work.i-did-not-set--mail-host-address--so-tickle-me \
--to=sheepduke@gmail.com \
--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).