From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: EWW debug facilities? Date: Fri, 25 Dec 2015 19:01:02 +0200 Message-ID: <83io3mlay9.fsf@gnu.org> References: <83wps2luue.fsf@gnu.org> <87poxu1nvk.fsf@gnus.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1451062864 6396 80.91.229.3 (25 Dec 2015 17:01:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 25 Dec 2015 17:01:04 +0000 (UTC) Cc: emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 25 18:01:00 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aCVjf-0004Fb-Aa for ged-emacs-devel@m.gmane.org; Fri, 25 Dec 2015 18:00:59 +0100 Original-Received: from localhost ([::1]:35894 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aCVje-0002oi-DH for ged-emacs-devel@m.gmane.org; Fri, 25 Dec 2015 12:00:58 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58443) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aCVj6-00026U-Vt for emacs-devel@gnu.org; Fri, 25 Dec 2015 12:00:27 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aCVj3-0002xN-0W for emacs-devel@gnu.org; Fri, 25 Dec 2015 12:00:24 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:52296) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aCVj2-0002xA-UK; Fri, 25 Dec 2015 12:00:20 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3875 helo=HOME-C4E4A596F7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aCVj1-0003bF-5u; Fri, 25 Dec 2015 12:00:20 -0500 In-reply-to: <87poxu1nvk.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 25 Dec 2015 17:42:07 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:196833 Archived-At: > From: Lars Ingebrigtsen > Cc: emacs-devel@gnu.org > Date: Fri, 25 Dec 2015 17:42:07 +0100 > > > 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. E.g., how would one go about finding out why bug#22234 happens? What does it try to fetch? > The HTML can be viewed with the `v' command, and the URL it fetched you > already know. I know about 'v', but it doesn't help when I get a blank page ;-) How do I know what URL it fetched when I type RET or click on a link? The link doesn't have to be a simple URL reference, it could be very complex, and involve multiple redirections.