bug#72464: [PATCH 1/2] Document how set path to C source code for SUSE based systems

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]

* etc/PROBLEMS(Problems when reading or debugging Emacs C code):
Document how to install Emacs C source and how to set path it for SUSE
based distributions such as openSUSE and SUSE Linux Enterprise.
---
 etc/PROBLEMS | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/etc/PROBLEMS b/etc/PROBLEMS
index c1ad8321fa6..ef205da2c17 100644
--- a/etc/PROBLEMS
+++ b/etc/PROBLEMS
@@ -456,6 +456,25 @@ However, the exact directory name will depend on the system, and you
 will need to both upgrade source and debug info when your system
 upgrades or patches Emacs, and change your startup file accordingly.
 
+** SUSE based distributions (openSUSE, SUSE Linux Enterprise)
+
+On systems with distributions, you can install source and debug info
+via superuser commands like the following:
+
+    # Install Emacs source and debuginfo by using --plus-content
+    zypper --plus-content debug,source install emacs-debuginfo emacs-debugsource
+
+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
+          (car (file-expand-wildcards "/usr/src/debug/emacs-*/src")))
+
+The line above should work for all systems using zypper besides SUSE
+based ones, however it could be that you have to adjust the path to
+the sources slightly depending on the version of the distribution you
+have installed.
+
 ** Source and debuginfo for other systems
 
 If your system follows neither the Debian nor the Red Hat patterns,
-- 
2.45.2

bug#72464: [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]

* 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

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]

merge 72464 72465 72466
thanks

> Date: Sun, 4 Aug 2024 18:56:15 +0300
> From:  Björn Bidar via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> I noticed that there are no instructions how setup the path to C source
> code of Emacs for SUSE based systems. 
> These patches add the instructions and improve the instructions for Red Had based
> systems.
> 
> Björn Bidar (2):
>   Document how set path to C source code for SUSE based systems
>   Improve instructions how set path to C source code for Red Hat
> 
>  etc/PROBLEMS | 21 ++++++++++++++++++++-
>  1 file changed, 20 insertions(+), 1 deletion(-)

As explained earlier, the way you sent this created 3 separate bug
reports, so I'm now merging them together.