From: Jim Porter <jporterbugs@gmail.com>
To: Tassilo Horn <tsdh@gnu.org>
Cc: 66752@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#66752: 30.0.50; [PATCH] Add support for 'thing-at-point' to 'bug-reference-mode'
Date: Sat, 4 Nov 2023 13:07:38 -0700 [thread overview]
Message-ID: <47a54242-d331-5864-7b2c-f1990034091a@gmail.com> (raw)
In-Reply-To: <87o7g9tj79.fsf@gnu.org>
On 11/4/2023 12:24 PM, Tassilo Horn wrote:
> Jim Porter <jporterbugs@gmail.com> writes:
>> (jit-lock-unregister #'bug-reference-fontify)
>> + (setq thing-at-point-provider-alist
>> + (delete '((url . bug-reference--url-at-point))
>> + thing-at-point-provider-alist))
>> + (when (equal thing-at-point-provider-alist
>> + (default-value 'thing-at-point-provider-alist))
>> + (kill-local-variable 'thing-at-point-provider-alist))
>
> Is that conventional, nuking a buffer-local value once it's back to its
> default value. Just asking out of curiosity.
I'm not sure. The only example I saw for adding to
'thing-at-provider-alist' was for EWW (a major mode). I thought, "What
if someone activated and deactivated 'bug-reference-mode' and then later
added something to the default value of 'thing-at-provider-alist'?"
I don't know if that's a case we want to support; maybe I'm just being
overly cautious. (Or maybe there should be - or already is - some
utility function that does this for us.) Eli, do you have any thoughts
on this part?
next prev parent reply other threads:[~2023-11-04 20:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 22:33 bug#66752: 30.0.50; [PATCH] Add support for 'thing-at-point' to 'bug-reference-mode' Jim Porter
2023-11-04 8:12 ` Eli Zaretskii
2023-11-04 19:24 ` Tassilo Horn
2023-11-04 20:07 ` Jim Porter [this message]
2023-11-05 5:31 ` Eli Zaretskii
2023-11-05 6:21 ` Jim Porter
2023-11-05 14:19 ` Stefan Kangas
2023-11-05 23:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-06 4:55 ` Jim Porter
2023-11-12 5:41 ` Jim Porter
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=47a54242-d331-5864-7b2c-f1990034091a@gmail.com \
--to=jporterbugs@gmail.com \
--cc=66752@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tsdh@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).