From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 22244@debbugs.gnu.org
Subject: bug#22244: 25.0.50; Make eww use display-buffer to display eww buffer
Date: Sat, 26 Dec 2015 18:02:42 +0100 [thread overview]
Message-ID: <8737upm9cd.fsf@gnus.org> (raw)
In-Reply-To: <87bn9dno9q.fsf@web.de> (Michael Heerdegen's message of "Sat, 26 Dec 2015 17:54:57 +0100")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Wouldn't it be better to let eww use display-buffer instead of
> switch-to-buffer in several places (at least, when calling eww and
> eww-browse-url, probably some more)? display-buffer's behavior can be
> controlled via binding variables, while display-buffer makes the same a
> horror.
I'm not familiar with display-buffer, but by default it seems to work
like pop-to-buffer?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2015-12-26 17:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 16:54 bug#22244: 25.0.50; Make eww use display-buffer to display eww buffer Michael Heerdegen
2015-12-26 17:02 ` Lars Ingebrigtsen [this message]
2015-12-26 17:29 ` Michael Heerdegen
2015-12-26 17:45 ` Lars Ingebrigtsen
2015-12-26 18:09 ` Michael Heerdegen
2015-12-26 18:19 ` Lars Ingebrigtsen
2015-12-26 23:19 ` Michael Heerdegen
2015-12-26 23:28 ` Lars Ingebrigtsen
2016-01-09 6:01 ` Michael Heerdegen
2016-02-02 4:55 ` Lars Ingebrigtsen
2016-02-02 15:24 ` Mark Oteiza
2016-02-03 1:59 ` Lars Ingebrigtsen
2016-02-03 2:57 ` Mark Oteiza
2016-02-04 2:18 ` Lars Ingebrigtsen
2016-02-04 6:31 ` bug#22244: [PATCH] New command eww-switch-to-buffer Mark Oteiza
2016-02-04 7:02 ` Lars Ingebrigtsen
2016-02-04 13:10 ` Michael Heerdegen
2016-02-04 17:49 ` Mark Oteiza
2016-02-04 19:09 ` Michael Heerdegen
2016-02-04 16:46 ` Eli Zaretskii
2016-02-04 17:48 ` Mark Oteiza
2016-02-02 4:58 ` bug#22244: 25.0.50; Make eww use display-buffer to display eww buffer Lars Ingebrigtsen
2016-02-02 14:19 ` Michael Heerdegen
2016-02-03 2:35 ` 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
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=8737upm9cd.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=22244@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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).