From: Mark Oteiza <mvoteiza@udel.edu>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 23738@debbugs.gnu.org
Subject: bug#23738: [feature request] eww allow multiple buffer
Date: Thu, 26 Jan 2017 13:06:11 -0500 [thread overview]
Message-ID: <20170126180611.GA7965@holos.localdomain> (raw)
In-Reply-To: <8737g6ly1c.fsf@gnus.org>
On 25/01/17 at 08:50pm, Lars Ingebrigtsen wrote:
> 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.
>
> On the other hand, we also have other buffers that have names that
> may become misleading after a while. For instance:
>
> (buffer-name) -> "*unsent wide reply to Mark Oteiza*"
>
> Even if I remove you from the headers, the buffer doesn't change name.
> :-) So there's precedence.
>
> Another option is to say that if the user has called eww in
> open-in-a-new-window-mode, then all further RETs in the buffer should
> also pop to new windows... Then the buffer name would always be
> correct.
>
> The third option is to always rename the buffer in these cases.
>
> The fourth is to revert to the previous meaningless buffer names, i.e.,
> *eww*<254> etc.
>
> Opinions?
I don't think I've ever used message-mode's buffer name to tell which
email it is, looking at the subject is easier. I certainly have never
used eww's buffer names to tell what website they are on, seeing how the
urls or titles are presented plainly in 3 different ways.
IMO The original report doesn't make sense. The buffer names have
nothing to do with being able to use and manipulate multiple eww
buffers.
I'd just revert. Alternatively, it looks trivial to make customizeable.
next prev parent reply other threads:[~2017-01-26 18:06 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
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 [this message]
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=20170126180611.GA7965@holos.localdomain \
--to=mvoteiza@udel.edu \
--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).