From: Michael Heerdegen <michael_heerdegen@web.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Bookmarks in EWW
Date: Thu, 26 Mar 2020 23:33:58 +0100 [thread overview]
Message-ID: <87v9mqeofd.fsf@web.de> (raw)
In-Reply-To: <bfcb7ca2-9c16-43ca-adc6-e4e1201eaa62@default> (Drew Adams's message of "Thu, 26 Mar 2020 07:02:05 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> So no, I don't think such things apply "in a uniform way for
> all implementations" of a make-record function. They're only
> for EWW.
Ok, noted ;-)
> (BTW, there's nothing about "sessions" in the Bookmark+ code,
> AFAIK; I haven't understood that part either, of your and
> Marcin's messages.)
A session in a browser is a page loaded in some tab or window, at least
it's the term used in w3m and eww AFAIK. If you open a link or a
different page in a different buffer, leaving the old buffer untouched,
you open it in a new session.
> 'Nuff said. I'm not pushing anyone to use code similar to what
> I offered. My point is that those particular features were
> added specifically for use with EWW - they're not Bookmark+
> features used for any other kinds of bookmarks.
Ok, all is well. For my part, I don't doubt the usefulness of what you
suggest, I just don't have the time to create a bigger patch because I
just stumbled in here too... so I want to offer a minimum of features
for now, anyone can extend it later.
Michael.
next prev parent reply other threads:[~2020-03-26 22:33 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 11:26 Bookmarks in EWW Marcin Borkowski
2020-03-23 14:56 ` Drew Adams
2020-03-25 11:48 ` Marcin Borkowski
2020-03-23 20:41 ` Michael Heerdegen
2020-03-24 14:46 ` Stefan Monnier
2020-03-25 3:05 ` Michael Heerdegen
2020-03-25 3:45 ` `declare-function' docu (was: Re: Bookmarks in EWW) Emanuel Berg via Users list for the GNU Emacs text editor
2020-03-28 17:59 ` `declare-function' docu Bruno Félix Rezende Ribeiro
2020-03-28 18:38 ` Drew Adams
2020-04-09 12:30 ` Bruno Félix Rezende Ribeiro
2020-04-09 15:47 ` Drew Adams
2020-03-28 21:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-03-25 14:06 ` Bookmarks in EWW Stefan Monnier
2020-03-26 1:09 ` Michael Heerdegen
2020-03-26 4:07 ` Stefan Monnier
2020-03-27 2:07 ` Michael Heerdegen
2020-03-27 3:44 ` Stefan Monnier
2020-03-28 2:31 ` Michael Heerdegen
2020-03-28 2:55 ` Stefan Monnier
2020-04-19 3:42 ` Michael Heerdegen
2020-04-19 13:18 ` Stefan Monnier
2020-04-20 3:17 ` Michael Heerdegen
2020-04-20 13:24 ` Stefan Monnier
2020-04-21 0:59 ` Michael Heerdegen
2020-04-29 22:53 ` Michael Heerdegen
2020-04-30 1:25 ` Stefan Monnier
2020-04-30 2:08 ` Michael Heerdegen
2020-04-30 3:08 ` Stefan Monnier
2020-04-30 20:09 ` Michael Heerdegen
2020-04-27 2:43 ` Michael Heerdegen
2020-03-27 4:32 ` buffer-localness (was: Re: Bookmarks in EWW) Emanuel Berg via Users list for the GNU Emacs text editor
2020-03-25 21:48 ` Bookmarks in EWW Drew Adams
2020-03-26 2:29 ` Michael Heerdegen
2020-03-26 3:21 ` Drew Adams
2020-03-26 3:53 ` Michael Heerdegen
2020-03-26 14:02 ` Drew Adams
2020-03-26 22:33 ` Michael Heerdegen [this message]
2020-03-26 8:41 ` Marcin Borkowski
2020-03-25 11:49 ` Marcin Borkowski
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=87v9mqeofd.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
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).