GNU bug report logs -
#72466
[PATCH 2/2] Improve instructions how set path to C source code for Red Hat
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 72466 in the body.
You can then email your comments to 72466 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#72466
; Package
emacs
.
(Sun, 04 Aug 2024 16:00:04 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Björn Bidar <bjorn.bidar <at> thaodan.de>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sun, 04 Aug 2024 16:00:04 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
* 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
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#72466
; Package
emacs
.
(Sun, 04 Aug 2024 16:17:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 72466 <at> debbugs.gnu.org (full text, mbox):
> 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 <at> 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.
bug closed, send any further explanations to
72466 <at> debbugs.gnu.org and Björn Bidar <bjorn.bidar <at> thaodan.de>
Request was from
Björn Bidar <bjorn.bidar <at> thaodan.de>
to
control <at> debbugs.gnu.org
.
(Sun, 04 Aug 2024 16:25:02 GMT)
Full text and
rfc822 format available.
Forcibly Merged 72464 72465 72466.
Request was from
Eli Zaretskii <eliz <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Sun, 04 Aug 2024 16:44:03 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#72466
; Package
emacs
.
(Sun, 04 Aug 2024 16:47:01 GMT)
Full text and
rfc822 format available.
Message #15 received at 72466 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
>> 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 <at> 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.
There's only one Emacs package in Fedora as well as in (open)SUSE
the source expanded in that wildcard is to 99% the one that the user
runs, especially for user that would be confused with lisp.
> 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.
I don't have a problem with 27.1 I just thought there would be a more
streamlined way of setting the patch to the C source code rather than
one that the user to update to each time they update.
Did not alter fixed versions and reopened.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 05 Aug 2024 11:55:02 GMT)
Full text and
rfc822 format available.
Removed tag(s) patch.
Request was from
Andrea Corallo <andcor03 <at> e132096.mail-host-address-is-not-set>
to
control <at> debbugs.gnu.org
.
(Mon, 05 Aug 2024 11:55:02 GMT)
Full text and
rfc822 format available.
Reply sent
to
Stefan Kangas <stefankangas <at> gmail.com>
:
You have taken responsibility.
(Sun, 23 Feb 2025 05:50:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Björn Bidar <bjorn.bidar <at> thaodan.de>
:
bug acknowledged by developer.
(Sun, 23 Feb 2025 05:50:02 GMT)
Full text and
rfc822 format available.
Message #24 received at 72466-done <at> debbugs.gnu.org (full text, mbox):
Björn Bidar <bjorn.bidar <at> thaodan.de> writes:
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
>>> 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 <at> 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.
>
> There's only one Emacs package in Fedora as well as in (open)SUSE
> the source expanded in that wildcard is to 99% the one that the user
> runs, especially for user that would be confused with lisp.
>
>> 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.
>
> I don't have a problem with 27.1 I just thought there would be a more
> streamlined way of setting the patch to the C source code rather than
> one that the user to update to each time they update.
I agree with Eli that the current text is fine, and I see that another
patch was installed here. So I'm closing this bug report now.
Reply sent
to
Stefan Kangas <stefankangas <at> gmail.com>
:
You have taken responsibility.
(Sun, 23 Feb 2025 05:50:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Björn Bidar <bjorn.bidar <at> thaodan.de>
:
bug acknowledged by developer.
(Sun, 23 Feb 2025 05:50:02 GMT)
Full text and
rfc822 format available.
Reply sent
to
Stefan Kangas <stefankangas <at> gmail.com>
:
You have taken responsibility.
(Sun, 23 Feb 2025 05:50:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Björn Bidar <bjorn.bidar <at> thaodan.de>
:
bug acknowledged by developer.
(Sun, 23 Feb 2025 05:50:03 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#72466
; Package
emacs
.
(Sun, 23 Feb 2025 21:13:02 GMT)
Full text and
rfc822 format available.
Message #37 received at 72466-done <at> debbugs.gnu.org (full text, mbox):
Fine by me.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 24 Mar 2025 11:24:09 GMT)
Full text and
rfc822 format available.
This bug report was last modified 90 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.