From: Oliver Scholz <alkibiades@gmx.de>
Subject: Re: Holy Wars redux: w3 vs. emacs-w3m
Date: Tue, 05 Nov 2002 00:00:03 +0100 [thread overview]
Message-ID: <ur8e12bye.fsf@ID-87814.user.dfncis.de> (raw)
In-Reply-To: uwunt2cjv.fsf@ID-87814.user.dfncis.de
I wrote:
>>> I really wish it would be more actively developed, because
>>> actually it is my favourite browser. And yes, I know emacs-w3m
>>> and I use it as a last resort, when Emacs/W3 fails to render a
>>> page. I am not happy with this, though.
And then I wrote:
> [Actually on my system Emacs/W3 is not reliable only in cases, where
> emacs-w3m is not reliable, too: in dealing with images and some
> advanced css stuff (Come to think about it, I doubt that emacs-w3m
> even tries to address the latter). So the main disadvantage is that
> Emacs/w3 is slow. Very slow, to be sure.]
I realize now that theese statements may seem a bit contradictory. I
should add that in the former case I was talking about the CVS version
of Emacs/W3 which I used until recently on my old work station and
which indeed failed to render some pages (http://www.perseus.tufts.edu
being my main source of grief -- or maybe url.el is to blame
here?). The latest released version (which I use now) works
o.k. AFAICS.
Large pages can get even a new computer on its knees, though. :-(
Oliver
--
14 Brumaire an 211 de la Révolution
Liberté, Egalité, Fraternité!
next prev parent reply other threads:[~2002-11-04 23:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1036345624.19554.help-gnu-emacs@gnu.org>
2002-11-03 17:55 ` Holy Wars redux: w3 vs. emacs-w3m Adam P.
2002-11-03 18:38 ` Henrik Enberg
2002-11-04 15:19 ` Oliver Scholz
2002-11-04 19:46 ` A. Lucien Meyers
2002-11-04 20:32 ` Henrik Enberg
2002-11-04 22:30 ` Oliver Scholz
2002-11-04 23:00 ` Oliver Scholz [this message]
2002-11-05 5:02 ` Michael J. Barillier
[not found] ` <mailman.1036473338.10358.help-gnu-emacs@gnu.org>
2002-11-05 15:47 ` Jay Belanger
2002-11-05 0:41 ` mr.sparkle
2002-11-05 13:20 ` Sacha Chua
2002-11-03 17:33 Michael J. Barillier
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=ur8e12bye.fsf@ID-87814.user.dfncis.de \
--to=alkibiades@gmx.de \
/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).