all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Manuel Giraud via "Emacs development discussions." <emacs-devel@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: sbaugh@catern.com,  emacs-devel@gnu.org
Subject: Re: source-directory, installed Emacs, and C source
Date: Wed, 25 Oct 2023 15:20:35 +0200	[thread overview]
Message-ID: <87r0liet3w.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <83bkcmkh36.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 25 Oct 2023 15:43:41 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Manuel Giraud <manuel@ledu-giraud.fr>
>> Cc: sbaugh@catern.com,  emacs-devel@gnu.org
>> Date: Wed, 25 Oct 2023 10:41:33 +0200
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> [...]
>> 
>> > AFAIR, Emacs looks for Lisp files by scanning load-path.  So if you
>> > customize load-path to include the directories in the source tree, you
>> > should be able to tell Emacs to look for the Lisp files in another
>> > directory.  I think that's what we do when Emacs is run uninstalled,
>> > and that's why it finds the Lisp files in the source tree.
>> 
>> This works… but not always.  Here is a test I've just done:
>> 
>>      - emacs -Q
>>      - then load the following:
>> --8<---------------cut here---------------start------------->8---
>> (add-to-list 'load-path "~/emacs-repo/lisp/")
>> (dolist (dir '("vc" "use-package" "url" "textmodes" "progmodes"
>> 	       "play" "org" "nxml" "net" "mh-e" "mail" "leim"
>> 	       "language" "international" "image" "gnus" "eshell"
>> 	       "erc" "emulation" "emacs-lisp" "cedet" "calendar"
>> 	       "calc" "obsolete"))
>>   (add-to-list 'load-path (format "~/emacs-repo/lisp/%s/" dir)))
>> --8<---------------cut here---------------end--------------->8---
>
> I never said you should just prepend the source tree to the previous
> value, did I?

No you did not say that.  But then what recipe with 'load-path' did you
have in mind to always look into the source tree?

> And anyway, are you sure you emulated Spencer's use case closely
> enough?  He never described in detail which files are where, but AFAIU
> at the very least you should have removed the *.el and *.el.gz files
> from the installation directory, since that is what he does (again,
> AFAIU).

Maybe this is what he does.  But then it is not what I imagined:
personally, I don't want to remove files from the installation
directory.
-- 
Manuel Giraud



  reply	other threads:[~2023-10-25 13:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24 14:31 source-directory, installed Emacs, and C source sbaugh
2023-10-24 14:47 ` Eli Zaretskii
2023-10-24 15:13   ` Spencer Baugh
2023-10-24 16:00     ` Eli Zaretskii
2023-10-24 16:20       ` sbaugh
2023-10-24 18:34         ` Eli Zaretskii
2023-10-25  8:41           ` Manuel Giraud via Emacs development discussions.
2023-10-25 12:43             ` Eli Zaretskii
2023-10-25 13:20               ` Manuel Giraud via Emacs development discussions. [this message]
2023-10-25 13:43                 ` sbaugh
2023-10-25 13:59                   ` Eli Zaretskii
2023-10-25 14:29                     ` sbaugh
2023-10-25 16:13                       ` Eli Zaretskii
2023-10-25 18:12                         ` Manuel Giraud via Emacs development discussions.
2023-10-25 18:37                           ` Eli Zaretskii
2023-10-25 19:07                             ` Manuel Giraud via Emacs development discussions.
2023-10-25 16:59                       ` Emanuel Berg
2023-10-24 18:35         ` Emanuel Berg
2023-10-25 17:43         ` chad
2023-10-25 18:32           ` Eli Zaretskii
2023-10-25 20:30             ` chad
2023-10-26  4:57               ` Eli Zaretskii
2023-10-25 18:57           ` Manuel Giraud via Emacs development discussions.
2023-10-24 16:00 ` Manuel Giraud via Emacs development discussions.
2023-10-24 16:04   ` Eli Zaretskii
2023-10-24 18:06   ` Emanuel Berg
2023-10-24 18:48   ` Arsen Arsenović
2023-10-24 18:01 ` Manuel Giraud via Emacs development discussions.

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=87r0liet3w.fsf@ledu-giraud.fr \
    --to=emacs-devel@gnu.org \
    --cc=eliz@gnu.org \
    --cc=manuel@ledu-giraud.fr \
    --cc=sbaugh@catern.com \
    /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.