From: Ted Zlatanov <tzz@lifelogs.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Mark Oteiza <mvoteiza@udel.edu>, 23738@debbugs.gnu.org
Subject: bug#23738: [feature request] eww allow multiple buffer
Date: Mon, 30 Jan 2017 14:52:58 -0500 [thread overview]
Message-ID: <87k29cpbol.fsf@lifelogs.com> (raw)
In-Reply-To: <87k29kdqsb.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 24 Jan 2017 23:41:40 +0100")
On Tue, 24 Jan 2017 23:41:40 +0100 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> Mark Oteiza <mvoteiza@udel.edu> writes:
>> What happens when I navigate to another site in the same buffer? Then
>> the buffer name is deceptive. Both s and S show the site and/or title,
>> and the header line of the eww buffer always has both, so this change seems
>> strange IMHO.
LI> Hm, yes, that's true. And changing the name of the buffer as you follow
LI> links isn't very nice, either. I think.
LI> Hm... so perhaps I should revert that change unless anybody has any
LI> other thoughts on this...
I think there are several use cases. I've given my suggestions:
1) open a new buffer directly to a hostname or "go to" a URL: use that
hostname in the buffer title
2) follow a link to the same host (or domain) in a EWW buffer: leave the
buffer title
3) follow a link to a different host (or domain) in a EWW buffer: drop
the buffer title and just make it a number or something unique
Ted
next prev parent reply other threads:[~2017-01-30 19:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 8:27 bug#23738: [feature request] eww allow multiple buffer Andreas Röhler
2016-06-10 14:03 ` Ted Zlatanov
2017-01-24 21:42 ` Lars Ingebrigtsen
2017-01-24 22:38 ` Mark Oteiza
2017-01-24 22:41 ` Lars Ingebrigtsen
2017-01-30 19:52 ` Ted Zlatanov [this message]
2017-01-31 16:31 ` Lars Ingebrigtsen
2017-01-31 18:44 ` Ted Zlatanov
2017-01-25 19:50 ` Lars Ingebrigtsen
2017-01-25 20:09 ` Noam Postavsky
2017-01-26 17:25 ` Lars Ingebrigtsen
2017-01-26 18:06 ` Mark Oteiza
2017-01-26 18:16 ` Lars Ingebrigtsen
2017-01-26 19:17 ` Mark Oteiza
2017-01-26 19:27 ` Lars Ingebrigtsen
2017-01-26 20:00 ` Mark Oteiza
2017-01-26 20:15 ` 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=87k29cpbol.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=23738@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mvoteiza@udel.edu \
/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).