From: Eli Zaretskii <eliz@gnu.org>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: 72466@debbugs.gnu.org
Subject: bug#72466: [PATCH 2/2] Improve instructions how set path to C source code for Red Hat
Date: Sun, 04 Aug 2024 19:15:48 +0300 [thread overview]
Message-ID: <86ttg0qn63.fsf@gnu.org> (raw)
In-Reply-To: <87frrkb7oj.fsf@> (bug-gnu-emacs@gnu.org)
> Date: Sun, 4 Aug 2024 16:17:25 +0300
> From: Björn Bidar via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> * etc/PROBLEMS(Problems when reading or debugging Emacs C code):
> Improve instruction how to set path to C source code for Red Hat
> based systems.
> ---
> etc/PROBLEMS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/etc/PROBLEMS b/etc/PROBLEMS
> index ef205da2c17..a642ebce570 100644
> --- a/etc/PROBLEMS
> +++ b/etc/PROBLEMS
> @@ -450,7 +450,7 @@ To get describe-function and similar commands to work, you can then
> add something like the following to your startup file:
>
> (setq find-function-C-source-directory
> - "/usr/src/debug/emacs-27.1-1.fc31.x86_64/src/")
> + (car (file-expand-wildcards "/usr/src/debug/emacs-*/src")))
Thanks, but I'd rather not confuse users with Lisp, and neither would
I assume that the first directory in the wildcard expansion will
necessarily be the one belonging to the running Emacs.
What exactly is wrong with the text as written? It explains where did
27.1 came from:
Once you have installed the source package, for example at
/home/myself/deb-src/emacs-27.1, add the following line to your
startup file: ^^^^^^^^^^
If you think 27.1 is too old, we could change that to 30 or something.
But other than that, I think the text is fine as it is.
next parent reply other threads:[~2024-08-04 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87frrkb7oj.fsf@>
2024-08-04 16:15 ` Eli Zaretskii [this message]
2024-08-04 16:45 ` bug#72466: [PATCH 2/2] Improve instructions how set path to C source code for Red Hat Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-04 13:17 Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86ttg0qn63.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72466@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
/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).