From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: EWW debug facilities? Date: Fri, 25 Dec 2015 17:42:07 +0100 Message-ID: <87poxu1nvk.fsf@gnus.org> References: <83wps2luue.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1451061772 23591 80.91.229.3 (25 Dec 2015 16:42:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 25 Dec 2015 16:42:52 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 25 17:42:42 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 1aCVRy-0002pe-El for ged-emacs-devel@m.gmane.org; Fri, 25 Dec 2015 17:42:42 +0100 Original-Received: from localhost ([::1]:35812 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aCVRx-0007uM-Re for ged-emacs-devel@m.gmane.org; Fri, 25 Dec 2015 11:42:41 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55423) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aCVRu-0007uH-NR for emacs-devel@gnu.org; Fri, 25 Dec 2015 11:42:39 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aCVRp-0006zQ-Nv for emacs-devel@gnu.org; Fri, 25 Dec 2015 11:42:38 -0500 Original-Received: from hermes.netfonds.no ([80.91.224.195]:44975) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aCVRp-0006z7-H3; Fri, 25 Dec 2015 11:42:33 -0500 Original-Received: from 2.150.58.24.tmi.telenormobil.no ([2.150.58.24] helo=mouse) by hermes.netfonds.no with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1aCVRR-0001Er-IJ; Fri, 25 Dec 2015 17:42:09 +0100 In-Reply-To: <83wps2luue.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 25 Dec 2015 11:51:21 +0200") User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1.50 (gnu/linux) X-MailScanner-ID: 1aCVRR-0001Er-IJ MailScanner-NULL-Check: 1451666529.88063@E3r/dWhoFRKePXR1q5Hc7Q X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.224.195 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:196832 Archived-At: Eli Zaretskii 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