unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eshel Yaron via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: sbaugh@janestreet.com, 69462@debbugs.gnu.org
Subject: bug#69462: 29.2.50; describe-function should support finding references
Date: Sat, 05 Oct 2024 09:20:11 +0200	[thread overview]
Message-ID: <m1frpbhv84.fsf@dazzs-mbp.home> (raw)
In-Reply-To: <c5ef9788-5a33-4341-af3f-14d363aaba64@gutov.dev> (Dmitry Gutov's message of "Thu, 3 Oct 2024 22:20:32 +0300")

Dmitry Gutov <dmitry@gutov.dev> writes:

> On 03/10/2024 10:14, Eshel Yaron wrote:
>> Looks nice!  What's somewhat nonideal is that the ELisp-specific Xref
>> setup lingers in the Help buffer even if it is reused for other purposes
>> (like dictionary words when dictionary-display-definition-function is
>> set to dictionary-display-definition-in-help-buffer).
>> Perhaps help-setup-xref should kill the local variables that
>> help-fns--setup-xref-backend now sets?
>
> Thanks, good idea, pushed as bde00266db4.

Great, I pushed a small fix for this change in 9f54f24e94d, and I
submitted a patch in bug#73637 that generalizes this kind of clean up.


Best,

Eshel





  reply	other threads:[~2024-10-05  7:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28 17:31 bug#69462: 29.2.50; describe-function should support finding references Spencer Baugh
2024-09-27 23:01 ` Dmitry Gutov
2024-10-03  0:07   ` Dmitry Gutov
2024-10-03  7:14     ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-03 19:20       ` Dmitry Gutov
2024-10-05  7:20         ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-10-05 11:59           ` Dmitry Gutov
2024-10-03 19:17     ` Dmitry Gutov

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=m1frpbhv84.fsf@dazzs-mbp.home \
    --to=bug-gnu-emacs@gnu.org \
    --cc=69462@debbugs.gnu.org \
    --cc=dmitry@gutov.dev \
    --cc=me@eshelyaron.com \
    --cc=sbaugh@janestreet.com \
    /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).