From: Lars Ingebrigtsen <larsi@gnus.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: Mark Oteiza <mvoteiza@udel.edu>, 23738@debbugs.gnu.org
Subject: bug#23738: [feature request] eww allow multiple buffer
Date: Thu, 26 Jan 2017 18:25:20 +0100 [thread overview]
Message-ID: <87lgtxzqbj.fsf@gnus.org> (raw)
In-Reply-To: <CAM-tV-9Jsw_iN2e4HXZuHOVdcfDpb5pPcX5daiL_EfFugx62+Q@mail.gmail.com> (Noam Postavsky's message of "Wed, 25 Jan 2017 15:09:24 -0500")
Noam Postavsky <npostavs@users.sourceforge.net> writes:
> There's precedence in the other direction too: when you do
> dired-find-alternate-file the buffer name changes.
Hm, yeah...
>> The fourth is to revert to the previous meaningless buffer names, i.e.,
>> *eww*<254> etc.
>
> If the buffer name will be meaningless, setting
> `list-buffers-directory' to the url so it shows up in the buffer
> listing could be useful.
Oh, nice. I didn't know about that one. I don't think it quite solves
the problem here, but eww should be setting that anyway. I'll make that
change.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2017-01-26 17:25 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 [this message]
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=87lgtxzqbj.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=23738@debbugs.gnu.org \
--cc=mvoteiza@udel.edu \
--cc=npostavs@users.sourceforge.net \
/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).