From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: 42483@debbugs.gnu.org
Subject: bug#42483: 26.1: thing-at-point doesn't recognize org-link urls
Date: Fri, 22 Jan 2021 21:24:56 +0000 [thread overview]
Message-ID: <87wnw4oeaf.fsf@gnus.jao.io> (raw)
In-Reply-To: <20200723033218.deuamgvc74zskyz4@E15-2016.optimum.net>
On Fri, Jan 22 2021, Lars Ingebrigtsen wrote:
[...]
> This sounds like something that belongs in org, though, and not in
> thingatpt.el, though. Unfortunately, thing-at-point doesn't have a
> mode-based model for working... but it could grow one? That is, there
> could be a buffer-local thing-at-point-local-things, and Org could set
> that to
>
> ((url . org--org-url-at-point))
>
> or something like that.
>
> Any opinions?
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).
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)
Just an idea,
jao
--
Come to think of it, there are already a million monkeys on a million
typewriters, and Usenet is NOTHING like Shakespeare. - Blair Houghton.
next prev parent reply other threads:[~2021-01-22 21:24 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 [this message]
2021-01-23 19:15 ` Lars Ingebrigtsen
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
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=87wnw4oeaf.fsf@gnus.jao.io \
--to=jao@gnu.org \
--cc=42483@debbugs.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 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).