From: Eshel Yaron via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 71117@debbugs.gnu.org,
"Andreas Röhler" <andreas.roehler@easy-emacs.de>,
"Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Subject: bug#71117: 30.0.50; output of describe-function
Date: Thu, 23 May 2024 22:23:35 +0200 [thread overview]
Message-ID: <m1fru8b7lk.fsf@dazzs-mbp.kpn> (raw)
In-Reply-To: <86h6eolail.fsf@mail.linkov.net> (Juri Linkov's message of "Thu, 23 May 2024 20:20:27 +0300")
Juri Linkov <juri@linkov.net> writes:
>>> Except there is a bug that prevents 's' from handling some C variables, e.g.:
>>>
>>> 0. emacs -Q
>>> 1. C-h v minibuffer-allow-text-properties RET
>>> 2. s
>>>
>>> fails with
>>>
>>> (error "Don’t know where ‘minibuffer-allow-text-properties’ is defined")
>>>
>>> So still need to use 'TAB RET' to navigate to C source.
>>
>> That bothered me too. Does this patch help?
>
> Thanks, now there is no such problem anymore.
Nice, pushed the fix to master.
Regarding the general issue of jumping to function/variable source,
I find C-x F and friends (enabled by find-function-setup-keys) quite
convenient.
Best,
Eshel
prev parent reply other threads:[~2024-05-23 20:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 13:53 bug#71117: 30.0.50; output of describe-function Andreas Röhler
2024-05-22 14:10 ` Eli Zaretskii
2024-05-22 17:46 ` Kévin Le Gouguec
2024-05-22 18:24 ` Eli Zaretskii
2024-05-22 22:22 ` Kévin Le Gouguec
2024-05-23 5:25 ` Eli Zaretskii
2024-05-28 17:44 ` Andrea Corallo
2024-05-28 18:20 ` Eli Zaretskii
2024-05-28 19:42 ` Andrea Corallo
2024-05-28 22:04 ` Kévin Le Gouguec
2024-05-28 22:25 ` Andrea Corallo
2024-05-29 11:25 ` Eli Zaretskii
2024-05-29 15:17 ` Andrea Corallo
2024-05-29 15:54 ` Eli Zaretskii
2024-05-29 16:04 ` Andrea Corallo
2024-05-29 11:38 ` Eli Zaretskii
2024-05-23 6:28 ` Juri Linkov
2024-05-23 11:51 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-23 17:20 ` Juri Linkov
2024-05-23 20:23 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=m1fru8b7lk.fsf@dazzs-mbp.kpn \
--to=bug-gnu-emacs@gnu.org \
--cc=71117@debbugs.gnu.org \
--cc=andreas.roehler@easy-emacs.de \
--cc=juri@linkov.net \
--cc=kevin.legouguec@gmail.com \
--cc=me@eshelyaron.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).