From: Yuchen Pei <hi@ypei.me>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50500@debbugs.gnu.org
Subject: bug#50500: Add ways to copy id bookmark link in eww
Date: Fri, 10 Sep 2021 23:03:42 +1000 [thread overview]
Message-ID: <87sfycwpjl.fsf@ypei.me> (raw)
In-Reply-To: <87o890ptpf.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Yuchen Pei <hi@ypei.me> writes:
>
>> I'd like to add a functionality to copy the bookmark link to
>> the kill
>> ring when the point is on a element with an id attribute.
>>
>> For example, say I am reading
>> <http://www.gnu.org/licenses/gpl-3.0.html>, and Section 13
>> looks
>> interesting which I want to save for reference. By calling the
>> said
>> function while the point is at Section 13, the link
>> <http://www.gnu.org/licenses/gpl-3.0.html#section13> is added
>> to the
>> kill ring.
>
> Well, people put ids on all kinds of elements, but they're not
> generally
> meant to be used for navigation. (I mean, sometimes they are,
> but
> statistically speaking, they're not.)
>
> So I'm not sure that `w' in general should be doing this in eww.
> Anybody else got an opinion?
Makes sense. How about adding it as a customization variable, so
that one can customize whether `w` also includes the id bookmark
part and by default it does not. It is often useful to save more
precise positions in web page documents.
--
Best,
Yuchen
PGP Key: 47F9 D050 1E11 8879 9040 4941 2126 7E93 EF86 DFD0
<https://ypei.me/assets/ypei-pubkey.txt>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 243 bytes --]
next prev parent reply other threads:[~2021-09-10 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 6:43 bug#50500: Add ways to copy id bookmark link in eww Yuchen Pei
2021-09-10 11:15 ` Lars Ingebrigtsen
2021-09-10 13:03 ` Yuchen Pei [this message]
2021-09-10 16:08 ` Juri Linkov
2021-09-11 12:28 ` Lars Ingebrigtsen
2021-09-11 19:06 ` Juri Linkov
2022-08-25 14:49 ` Lars Ingebrigtsen
2021-09-11 12:34 ` 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=87sfycwpjl.fsf@ypei.me \
--to=hi@ypei.me \
--cc=50500@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).