all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: EWW debug facilities?
Date: Fri, 25 Dec 2015 17:42:07 +0100	[thread overview]
Message-ID: <87poxu1nvk.fsf@gnus.org> (raw)
In-Reply-To: <83wps2luue.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 25 Dec 2015 11:51:21 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> How do you debug EWW, when it fails to do something?

I just use the normal Emacs debugging facilities (mainly edebug).

> Perhaps I'm missing something, but there doesn't seem to be any debug
> or log facilities in eww.el.  When something goes wrong, it's useful
> to see a detailed log of the URLs EWW tried to fetch, including the
> results, and perhaps also the related logs from the url*.el APIs it
> invokes.  That should allow finding the offending code, which can then
> be debugged by traditional means.

I have a feeling that you think eww is way more complicated than it is.
:-) eww fetches a single HTML page, renders it, and then fetches any
images the HTML may have included.

The HTML can be viewed with the `v' command, and the URL it fetched you
already know.

I haven't seen the need for logging anything.  

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2015-12-25 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-25  9:51 EWW debug facilities? Eli Zaretskii
2015-12-25 16:42 ` Lars Ingebrigtsen [this message]
2015-12-25 17:01   ` Eli Zaretskii
2015-12-25 17:26     ` Lars Ingebrigtsen
2015-12-25 19:42       ` Eli Zaretskii
2015-12-25 19:45         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87poxu1nvk.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=eliz@gnu.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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.