From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Re: eww
Date: Mon, 17 Jun 2013 19:35:50 -0400 [thread overview]
Message-ID: <m2r4g0pay1.fsf@lifelogs.com> (raw)
In-Reply-To: <m3ppvkihb2.fsf@stories.gnus.org>
On Mon, 17 Jun 2013 23:00:17 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> I spent some time doing rendering optimisations in shr today, including
LMI> the `add-face-text-properties' C-level functionality. That, combined
LMI> with various caching strategies and trying to avoid doing unnecessary
LMI> work when computing how tables should be rendered has made viewing a
LMI> typical Wikipedia page 4x faster or something.
LMI> So it's still slow, but it's getting more useful. There's still
LMI> probably bugs in there, though. Give it a whirl:
LMI> M-x eww RET google.com
You should add commentary with short instructions on making it the
default URL browse action in Gnus.
It's pretty awesome otherwise.
Ted
next prev parent reply other threads:[~2013-06-17 23:35 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 14:53 eww Lars Magne Ingebrigtsen
2013-06-16 15:21 ` eww Adam Sjøgren
2013-06-16 15:29 ` eww Lars Magne Ingebrigtsen
2013-06-16 15:46 ` eww Lars Magne Ingebrigtsen
2013-06-16 17:01 ` eww Dmitry Gutov
2013-06-16 17:06 ` eww Lars Magne Ingebrigtsen
2013-06-17 21:00 ` eww Lars Magne Ingebrigtsen
2013-06-17 23:35 ` Ted Zlatanov [this message]
2013-06-18 0:01 ` eww Lars Magne Ingebrigtsen
2013-07-09 13:20 ` eww Ted Zlatanov
2013-08-01 14:39 ` eww Lars Magne Ingebrigtsen
2013-07-09 10:23 ` eww Julien Cubizolles
2013-07-09 10:42 ` eww David Edmondson
2013-06-16 23:42 ` eww lee
2013-06-17 5:57 ` eww Lars Magne Ingebrigtsen
2013-06-17 18:46 ` eww lee
2013-06-18 2:19 ` eww Tom Tromey
2013-06-18 11:23 ` eww Lars Magne Ingebrigtsen
2013-06-18 14:34 ` eww Tom Tromey
2013-06-18 15:01 ` eww Lars Magne Ingebrigtsen
2013-06-18 15:43 ` eww Tom Tromey
2013-06-18 14:39 ` eww Tom Tromey
2013-06-18 15:14 ` eww Lars Magne Ingebrigtsen
2013-06-18 16:17 ` eww Tom Tromey
2013-06-18 19:06 ` eww Steinar Bang
2013-06-18 19:07 ` eww Stefan Monnier
2013-06-18 11:31 ` eww Lars Magne Ingebrigtsen
2013-06-18 14:42 ` eww Tom Tromey
2013-06-18 15:04 ` eww Lars Magne Ingebrigtsen
2013-06-18 19:13 ` eww Stefan Monnier
2013-06-18 19:17 ` eww Eli Zaretskii
2013-06-18 20:21 ` eww Stefan Monnier
2013-06-18 23:34 ` eww James Cloos
2013-06-19 2:50 ` eww Eli Zaretskii
2013-06-19 4:49 ` eww Stefan Monnier
2013-06-18 23:03 ` eww Xue Fuqiao
2013-06-19 3:03 ` eww Eli Zaretskii
2013-06-18 19:27 ` eww Tom Tromey
2013-06-18 23:40 ` eww Juri Linkov
2013-06-19 0:51 ` eww Stefan Monnier
2013-06-19 1:08 ` eww Russ Allbery
2013-06-19 10:14 ` eww Rasmus
2013-06-19 10:34 ` eww Christopher Schmidt
2013-06-25 7:43 ` eww lee
2013-06-25 9:05 ` eww Tassilo Horn
2013-06-25 13:27 ` eww Steinar Bang
2013-06-27 9:05 ` eww lee
2013-06-18 11:32 ` eww joakim
2013-06-18 12:16 ` eww Andreas Schwab
2013-06-18 13:57 ` eww Lars Magne Ingebrigtsen
2013-06-18 14:01 ` eww joakim
2013-06-19 10:21 ` eww Ivan Kanis
2013-06-19 11:52 ` eww Steinar Bang
2013-06-19 12:14 ` eww Ivan Kanis
2013-08-01 11:59 ` eww John Williams
2013-08-02 0:20 ` eww John Williams
2013-08-02 0:27 ` eww Lars Magne Ingebrigtsen
2013-08-02 19:48 ` eww Richard Stallman
2013-08-03 11:30 ` eww Lars Magne 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2r4g0pay1.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).