Re: source-directory, installed Emacs, and C source

[Spencer Baugh <sbaugh@janestreet.com>]

Eli Zaretskii <eliz@gnu.org> writes:
>> From: sbaugh@catern.com
>> Date: Tue, 24 Oct 2023 10:31:49 -0400
>> 
>> - Jumping to a newer function definition is not a problem.
>> 
>>   So we can do it for Lisp too.  We can do that by having Emacs jump to
>>   Lisp source files from source-directory, too, if they exist.
>>   (Possibly as an option off by default, if people would prefer that)
>> 
>>   This would be a great improvement for users who keep source-directory
>>   around (since now Emacs jumps straight to your source repo, allowing
>>   easy modifications, and also you can skip installing Lisp source files
>>   with Emacs) and status quo for users that don't keep source-directory
>>   around.
>> 
>> Thoughts?
>> 
>> I'm interested in implementing one of these two options, since I want to
>> be able to reliably jump to function definitions from an installed
>> Emacs.  I don't care which of the two we go with.
>
> Why would the Lisp sources not be available where Emacs installs them,
> i.e. in the /usr/share tree?

If the user ./configure'd Emacs to not install them because they prefer
to jump to source-directory instead.  That's what I meant by:

>This would be a great improvement for users who keep source-directory
>around (since now Emacs jumps straight to your source repo, allowing
>easy modifications, and also you can skip installing Lisp source files
>with Emacs)