From: Ted Zlatanov <tzz@lifelogs.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 23738@debbugs.gnu.org
Subject: bug#23738: [feature request] eww allow multiple buffer
Date: Tue, 31 Jan 2017 13:44:19 -0500 [thread overview]
Message-ID: <87k29bt6gs.fsf@flea> (raw)
In-Reply-To: <m37f5bnqbr.fsf@stories> (Lars Ingebrigtsen's message of "Tue, 31 Jan 2017 17:31:52 +0100")
On Tue, 31 Jan 2017 17:31:52 +0100 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> 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
LI> Yeah, I think this is a probably the best way to deal with it. That is:
LI> If you've opened a "domain-named" eww buffer (which is now the case with
LI> NEW-WINDOW), then eww will have to change the name of the buffer if you
LI> follow a link to a different domain. But perhaps just keep renaming it
LI> based on the new domain instead of reverting to <number>?
Your call, as long as the logic is consistent and clear in the code,
separately treating those three cases. Then it can be amended or even
extracted into customizable hooks etc.
Ted
next prev parent reply other threads:[~2017-01-31 18:44 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
2017-01-31 16:31 ` Lars Ingebrigtsen
2017-01-31 18:44 ` Ted Zlatanov [this message]
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=87k29bt6gs.fsf@flea \
--to=tzz@lifelogs.com \
--cc=23738@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 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).