* Associating module symbols with defining files
@ 2024-06-11 18:00 Spencer Baugh
2024-06-12 7:57 ` Eli Zaretskii
0 siblings, 1 reply; 3+ messages in thread
From: Spencer Baugh @ 2024-06-11 18:00 UTC (permalink / raw)
To: emacs-devel
It's currently impossible to associate a symbol defined by a module with
the source file which actually defined that symbol.
If this were possible, things like help-view-source would be able to
jump to the source code for a module-defined function. Under the hood,
ultimately we want symbol-file to return a correct filename for these
symbols.
Instead, currently, every symbol defined by a module is "defined" by the
module .so. So jumping to source just jumps to the (compiled) .so,
which is fairly useless.
Could this be fixed?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Associating module symbols with defining files
2024-06-11 18:00 Associating module symbols with defining files Spencer Baugh
@ 2024-06-12 7:57 ` Eli Zaretskii
2024-06-12 15:23 ` Spencer Baugh
0 siblings, 1 reply; 3+ messages in thread
From: Eli Zaretskii @ 2024-06-12 7:57 UTC (permalink / raw)
To: Spencer Baugh; +Cc: emacs-devel
> From: Spencer Baugh <sbaugh@janestreet.com>
> Date: Tue, 11 Jun 2024 14:00:33 -0400
>
>
> It's currently impossible to associate a symbol defined by a module with
> the source file which actually defined that symbol.
>
> If this were possible, things like help-view-source would be able to
> jump to the source code for a module-defined function. Under the hood,
> ultimately we want symbol-file to return a correct filename for these
> symbols.
>
> Instead, currently, every symbol defined by a module is "defined" by the
> module .so. So jumping to source just jumps to the (compiled) .so,
> which is fairly useless.
>
> Could this be fixed?
Maybe. But please submit a feature-request bug report with all the
details and a reproducer, so that we could track this issue.
Thanks.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Associating module symbols with defining files
2024-06-12 7:57 ` Eli Zaretskii
@ 2024-06-12 15:23 ` Spencer Baugh
0 siblings, 0 replies; 3+ messages in thread
From: Spencer Baugh @ 2024-06-12 15:23 UTC (permalink / raw)
To: emacs-devel
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Spencer Baugh <sbaugh@janestreet.com>
>> Date: Tue, 11 Jun 2024 14:00:33 -0400
>>
>>
>> It's currently impossible to associate a symbol defined by a module with
>> the source file which actually defined that symbol.
>>
>> If this were possible, things like help-view-source would be able to
>> jump to the source code for a module-defined function. Under the hood,
>> ultimately we want symbol-file to return a correct filename for these
>> symbols.
>>
>> Instead, currently, every symbol defined by a module is "defined" by the
>> module .so. So jumping to source just jumps to the (compiled) .so,
>> which is fairly useless.
>>
>> Could this be fixed?
>
> Maybe. But please submit a feature-request bug report with all the
> details and a reproducer, so that we could track this issue.
>
> Thanks.
Sure, filed bug#71522
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=71522
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-06-12 15:23 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-06-11 18:00 Associating module symbols with defining files Spencer Baugh
2024-06-12 7:57 ` Eli Zaretskii
2024-06-12 15:23 ` Spencer Baugh
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).