From: Ivan Shmakov <ivan@siamics.net>
To: 16211@debbugs.gnu.org
Subject: bug#16211: eww should support multiple *eww* buffers
Date: Wed, 19 Nov 2014 08:36:37 +0000 [thread overview]
Message-ID: <87k32r7fje.fsf@violet.siamics.net> (raw)
In-Reply-To: <87d28j8z67.fsf@violet.siamics.net> (Ivan Shmakov's message of "Wed, 19 Nov 2014 06:47:12 +0000")
One another issue, – the following plist-put does nothing, as
it’s evaluated while still in the url.el “data buffer” (for
which eww-data is most likely nil):
208 (defun eww-render (status url &optional point buffer)
…
212 (let* ((headers (eww-parse-headers))
…
223 (data-buffer (current-buffer)))
224 (unwind-protect
225 (progn
226 (plist-put eww-data :title "")
The plist-put calls down that progn are evaluated after
eww-display-*, and thus after either eww-setup-buffer or some
other set-buffer. The eww-use-external-browser-for-content-type
case I’m unsure about, though.
--
FSF associate member #7257 http://boycottsystemd.org/ … 3013 B6A0 230E 334A
next prev parent reply other threads:[~2014-11-19 8:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 11:24 bug#16211: eww should support multiple *eww* buffers Ivan Shmakov
2013-12-21 20:22 ` Ted Zlatanov
2013-12-21 21:51 ` Ivan Shmakov
2013-12-22 22:36 ` Ted Zlatanov
2014-07-06 19:05 ` Ivan Shmakov
2014-11-04 16:42 ` Ted Zlatanov
2013-12-23 3:21 ` Stefan Monnier
2013-12-23 13:11 ` Ted Zlatanov
2013-12-23 18:19 ` Ivan Shmakov
2013-12-23 19:01 ` Glenn Morris
2013-12-24 8:05 ` Lars Ingebrigtsen
2013-12-24 8:49 ` Ivan Shmakov
2014-11-10 21:18 ` Lars Magne Ingebrigtsen
2014-11-19 6:47 ` Ivan Shmakov
2014-11-19 8:36 ` Ivan Shmakov [this message]
2014-11-19 17:41 ` Lars Magne Ingebrigtsen
2014-11-30 9:59 ` bug#19225: eww-render: runs eww-after-render-hook in the (temporary) data buffer Ivan Shmakov
2014-11-30 10:45 ` Ivan Shmakov
2014-12-01 17:56 ` Lars Magne Ingebrigtsen
2014-11-19 17:38 ` bug#16211: eww should support multiple *eww* buffers 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
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=87k32r7fje.fsf@violet.siamics.net \
--to=ivan@siamics.net \
--cc=16211@debbugs.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).