From: Ivan Shmakov <ivan@siamics.net>
To: 16211@debbugs.gnu.org
Cc: Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#16211: eww should support multiple *eww* buffers
Date: Tue, 24 Dec 2013 08:49:47 +0000 [thread overview]
Message-ID: <871u12tyz8.fsf@violet.siamics.net> (raw)
In-Reply-To: <87a9fqy8q9.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Tue, 24 Dec 2013 09:05:34 +0100")
>>>>> Lars Ingebrigtsen <larsi@gnus.org> writes:
>>>>> Ted Zlatanov <tzz@lifelogs.com> writes:
>> I was talking about "tabs" and "windows" specifically, which imply a
>> collection of eww buffers should be somehow associated. Anyhow, as
>> I said, I'm in favor of this as well, I just didn't want to assume
>> this direction was desirable.
> I'm not sure I quite see the value in grouping eww buffers in tabs,
> but it should be possible to just rename an eww buffer and create new
> ones with `M-x eww'. That's almost possible now, perhaps? The eww
> buffer uses only buffer-local variables (or is supposed to), so
> things should, like work.
> But I haven't tried doing that at all, so the likelihood of that
> working is probably zero. >"? But it should be fixable.
The problem is that trying to M-x eww, or to follow a link, in
such a renamed buffer, results in the target document still
being rendered in the *eww* buffer.
As I’ve already mentioned [1, 2], it happens because
url-retrieve (as called by M-x eww and M-x eww-reload) calls its
callback (which is eww-render in these cases) /not/ in the
original buffer, but instead in a buffer holding the data
fetched from the URI specified. Which makes it necessary to
pass the original buffer (the one from which M-x eww is called)
to eww-render (through the ‘cbargs’ argument to url-retrieve.)
Then, eww-render may pass the buffer to eww-setup-buffer, either
via a dynamically-bound variable, or as an argument.
(Alternatively, eww-render may switch to the buffer by itself.)
[1] http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16211#5
[2] http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16211#11
--
FSF associate member #7257
next prev parent reply other threads:[~2013-12-24 8:49 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 [this message]
2014-11-10 21:18 ` Lars Magne Ingebrigtsen
2014-11-19 6:47 ` Ivan Shmakov
2014-11-19 8:36 ` Ivan Shmakov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871u12tyz8.fsf@violet.siamics.net \
--to=ivan@siamics.net \
--cc=16211@debbugs.gnu.org \
--cc=larsi@gnus.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.