From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Jose A. Ortega Ruiz" <jao@gnu.org>
Cc: 42483@debbugs.gnu.org
Subject: bug#42483: 26.1: thing-at-point doesn't recognize org-link urls
Date: Sat, 23 Jan 2021 20:15:37 +0100 [thread overview]
Message-ID: <87r1mbtqg6.fsf@gnus.org> (raw)
In-Reply-To: <87wnw4oeaf.fsf@gnus.jao.io> (Jose A. Ortega Ruiz's message of "Fri, 22 Jan 2021 21:24:56 +0000")
"Jose A. Ortega Ruiz" <jao@gnu.org> writes:
> Another context in which something like this could be useful is
> emacs-w3m buffers, which are naturally full of links stored in text
> properties (or eww, i am guessing).
Yes, that's true -- it would certainly be nice if `(thing-at-point 'url)'
worked in eww buffers (which it currently doesn't).
> A strategy i've seen elsewhere (in the embark package) for something
> similar is to keep a list of "target finders" that are applied in turn,
> until one succeeds returning, say, '(url . "http://foo/bar"). That's
> essentially what you're suggesting above, except that one can write
> global detectors (the list is not (necessarily) buffer local)
Yup. Adding this sort of framework to thingatpt looks pretty trivial,
and sounds generally useful, so I'll take a stab at it (using eww as the
first test case).
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-01-23 19:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 3:32 bug#42483: 26.1: thing-at-point doesn't recognize org-link urls Boruch Baum
2021-01-22 19:51 ` Lars Ingebrigtsen
2021-01-22 21:24 ` Jose A. Ortega Ruiz
2021-01-23 19:15 ` Lars Ingebrigtsen [this message]
2021-01-23 19:40 ` Lars Ingebrigtsen
2022-05-09 11:41 ` Lars Ingebrigtsen
2022-06-06 13:12 ` Lars Ingebrigtsen
2021-01-23 19:42 ` jao
2021-01-25 23:51 ` Lars Ingebrigtsen
2021-01-26 0:29 ` jao
2021-01-27 1:36 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1mbtqg6.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=42483@debbugs.gnu.org \
--cc=jao@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.