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 14:17:36 -0500 [thread overview]
Message-ID: <20170126191736.GA10021@holos.localdomain> (raw)
In-Reply-To: <87vat1vg8t.fsf@gnus.org>
On 26/01/17 at 07:16pm, Lars Ingebrigtsen wrote:
> Mark Oteiza <mvoteiza@udel.edu> writes:
>
> > 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 think there's value in being able to type `C-x b fsf RET' to go the
> buffer that has the FSF web page, or whatever. Especially for people
> with disabilities.
Unless you navigated to the FSF page from duckduckgo or any other host.
next prev parent reply other threads:[~2017-01-26 19:17 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
2017-01-26 18:16 ` Lars Ingebrigtsen
2017-01-26 19:17 ` Mark Oteiza [this message]
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=20170126191736.GA10021@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).