From: "Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 72464@debbugs.gnu.org
Subject: bug#72464: [PATCH 2/2] Improve instructions how set path to C source code for Red Hat
Date: Sun, 4 Aug 2024 16:17:25 +0300 [thread overview]
Message-ID: <8463.11869552068$1722788829@news.gmane.org> (raw)
In-Reply-To: <87ikwgb7p3.fsf@>
* 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")))
However, the exact directory name will depend on the system, and you
will need to both upgrade source and debug info when your system
--
2.45.2
next prev parent reply other threads:[~2024-08-04 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ikwgb7p3.fsf@>
2024-08-04 13:09 ` bug#72464: [PATCH 1/2] Document how set path to C source code for SUSE based systems 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 [this message]
2024-08-04 16:29 ` bug#72464: [PATCH 0/2] Add instructions how setup path to C source code for SUSE based systems and improve Red Hat ones Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='8463.11869552068$1722788829@news.gmane.org' \
--to=bug-gnu-emacs@gnu.org \
--cc=72464@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.