From: Jim Porter <jporterbugs@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Adding custom providers for thingatpt.el (was: [PATCH] Add support for 'thing-at-point' to get URL at point)
Date: Mon, 20 May 2024 13:32:30 -0700 [thread overview]
Message-ID: <9a9eb3b1-9a48-4868-fb80-7a7b23c535e3@gmail.com> (raw)
In-Reply-To: <87seycrci8.fsf@localhost>
On 5/20/2024 3:41 AM, Ihor Radchenko wrote:
> Jim Porter <jporterbugs@gmail.com> writes:
>
>> + (when (boundp 'forward-thing-provider-alist)
>> + (setq-local forward-thing-provider-alist
>> + (cons '(url . org-next-link)
>> + forward-thing-provider-alist)))
>
> According to the docstring, functions in `forward-thing-provider-alist'
> should accept a single argument - the number of "things" to skip
> forward/backward. But it is not what `org-next-link' expects.
In a twist, it turns out *this* patch for Org-mode was correct, and my
prior patch for thingatpt.el was wrong. In short, 'forward-thing' now
calls the functions in 'forward-thing-provider-alist' with a BACKWARD
flag, rather than an integer N. That's because 'forward-thing' needs to
account for the case where you have multiple providers for the same
"thing", and so it needs to go one at a time checking all the providers
for the best match (read: the one that moves point by the smallest
non-zero amount).
I've now pushed the thingatpt fix to the Emacs master branch.
next prev parent reply other threads:[~2024-05-20 20:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 19:45 [PATCH] Add support for 'thing-at-point' to get URL at point Jim Porter
2023-11-06 19:56 ` Jim Porter
2023-11-06 20:11 ` Adding custom providers for thingatpt.el (was: [PATCH] Add support for 'thing-at-point' to get URL at point) Ihor Radchenko
2023-11-06 20:53 ` Jim Porter
2024-02-05 15:07 ` Ihor Radchenko
2024-02-05 22:44 ` Jim Porter
2024-02-05 22:56 ` Ihor Radchenko
2024-02-06 12:26 ` Eli Zaretskii
2024-02-06 12:38 ` Ihor Radchenko
2024-02-06 12:47 ` Eli Zaretskii
2024-04-12 12:41 ` Ihor Radchenko
2024-04-12 22:30 ` Jim Porter
2024-04-29 4:26 ` Jim Porter
2024-04-29 18:14 ` Ihor Radchenko
2024-04-30 4:42 ` Jim Porter
2024-04-30 11:39 ` Ihor Radchenko
2024-04-30 18:27 ` Jim Porter
2024-04-30 21:10 ` [External] : " Drew Adams
2024-05-07 1:08 ` Jim Porter
2024-05-07 1:52 ` Drew Adams
2024-05-07 12:20 ` Eli Zaretskii
2024-05-07 15:16 ` Drew Adams
2024-05-07 16:10 ` Jim Porter
2024-05-07 18:01 ` Eli Zaretskii
2024-05-18 8:26 ` Eli Zaretskii
2024-05-20 1:34 ` Jim Porter
2024-05-20 2:33 ` Jim Porter
2024-05-20 10:41 ` Ihor Radchenko
2024-05-20 20:32 ` Jim Porter [this message]
2024-05-25 14:09 ` Ihor Radchenko
2024-05-26 5:33 ` Jim Porter
2024-05-26 12:56 ` Ihor Radchenko
2024-05-26 17:03 ` Jim Porter
2024-05-21 10:32 ` Adding custom providers for thingatpt.el Max Nikulin
2024-05-21 16:24 ` Jim Porter
2024-05-22 13:30 ` Max Nikulin
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9a9eb3b1-9a48-4868-fb80-7a7b23c535e3@gmail.com \
--to=jporterbugs@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.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/org-mode.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).