From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: source-directory, installed Emacs, and C source Date: Tue, 24 Oct 2023 21:34:44 +0300 Message-ID: <831qdjlvi3.fsf@gnu.org> References: <875y2wrt0q.fsf@catern.com> <83cyx4krfm.fsf@gnu.org> <837cncko34.fsf@gnu.org> <87y1fsq9ef.fsf@catern.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13865"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: sbaugh@catern.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 24 20:35:46 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qvMFm-0003IW-4m for ged-emacs-devel@m.gmane-mx.org; Tue, 24 Oct 2023 20:35:46 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qvMEy-0002th-Tf; Tue, 24 Oct 2023 14:34:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qvMEv-0002sf-2t for emacs-devel@gnu.org; Tue, 24 Oct 2023 14:34:53 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qvMEu-0001mP-Ls; Tue, 24 Oct 2023 14:34:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=TndoyrL/VzYVQX4s5/aOo0UZJ2gb0TSWwr/WPwKDeUw=; b=ra1Kz3Lo/06o nUnz+juxeJwBCiFREehmOXhjtqcfLNWzychl1Uc4TFbckQKcWYEmXeqAs4J/YA7eFswW8AsUFp86I uIn5mEZOr1RZCMiKnpUZf2a7OhQ6BxRA0iTPDcmi8QPy2GGAwlUOnTCveQ2bB99TbCMQrtyGImUxm blIC8sxOapZ+LhE6xKeiq0EKrYU+QV6yl2unOaHrm2uEZOMzHVbd90PmX9H1Q+1o9ZclJuOiRontF t5aK7rj0e/C0Zrl8mLOuDgoX1uyHHkqiiehhmzztUn3KRA8oUWpxA4bo5AREyrFW8TN5z3qDp3QVf 4V0LJNHTruMbwujDc7OcgA==; In-Reply-To: <87y1fsq9ef.fsf@catern.com> (sbaugh@catern.com) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:311816 Archived-At: > From: sbaugh@catern.com > Date: Tue, 24 Oct 2023 12:20:56 -0400 > > Eli Zaretskii writes: > > > > Emacs is supposed to be installed _with_ Lisp files. It is important > > to let users modify the Lisp files when they need. So I'm not sure we > > want to support an installation where Lisp files are not available. > > Yes, to be clear, I'm talking about a case where the Lisp files are in > source-directory, not where they don't exist at all. If the Lisp files > are in source-directory and stay around there, then perhaps they don't > need to be copied to /usr/share. > > But if we want to always copy them to /usr/share, that's fine, it's not > necessary to support skipping that. > > My suggestion, then, is that we should allow customizing Emacs to prefer > jumping to source-directory over jumping to the installed copies of the > Lisp files. 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.