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: Easy configuration of a site-lisp directory Date: Tue, 10 Aug 2021 14:55:42 +0300 Message-ID: <835ywdh5tt.fsf@gnu.org> References: <87y29cj65y.fsf@posteo.net> <87czqna77n.fsf@dick> <878s1ba1nl.fsf@dick> <4324d238-261f-946d-eb6b-a98bea3a1157@gmail.com> <83eeb2h7v4.fsf@gnu.org> <024825b3-fa33-a852-5115-1ee56ae47041@gmail.com> <838s1ah2mw.fsf@gnu.org> <9bcf4a54-6457-7365-8364-0986364ecc6a@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39851"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Aug 10 13:57:15 2021 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 1mDQNd-000A35-Cc for ged-emacs-devel@m.gmane-mx.org; Tue, 10 Aug 2021 13:57:13 +0200 Original-Received: from localhost ([::1]:44636 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mDQNb-0004nR-Jc for ged-emacs-devel@m.gmane-mx.org; Tue, 10 Aug 2021 07:57:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48300) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mDQM1-00027g-TE for emacs-devel@gnu.org; Tue, 10 Aug 2021 07:55:33 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:45798) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mDQM1-00007a-MN; Tue, 10 Aug 2021 07:55:33 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2542 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mDQM1-0008HO-83; Tue, 10 Aug 2021 07:55:33 -0400 In-Reply-To: <9bcf4a54-6457-7365-8364-0986364ecc6a@gmail.com> (message from =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel on Mon, 9 Aug 2021 18:14:46 -0400) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:272267 Archived-At: > Cc: emacs-devel@gnu.org > From: Clément Pit-Claudel > Date: Mon, 9 Aug 2021 18:14:46 -0400 > > > Why is that a problem for you? M-. takes you to the code you are > > actually running, > > No, I'm running from .elc files, am I not? Not from .el.gz ones. You are also running native machine code, not the C source files. And yet you want M-. to show you the C source code, not the disassembly of the machine instructions. Same with *.el.gz files: they are the exact _source_code_ of what you are running. > > whereas the files in Git could have been modified > > meanwhile, and are no longer the code your installed Emacs runs. > > Yep, that's precisely why I wrote "Though the .el files could be out of sync with the .el.gz files, presumably." But the same issue exists with the C files, which could be out of date as well. In the case of C sources there's no alternative if you install from the Git checkout (as opposed to from a source tree produced by unpacking the tarball). At the time, some people argued for installing the C sources at "make install" time, which I think would be taking things too far. Especially as installing allows you to delete the source tree, in which case there would be no TAGS to support M-. anyway. > > . run 'etags' to produce TAGS that names the *.el files in the Git > > checkout where you want to go > > > > . configure Xref to use etags for ELisp files (instead of the > > built-in ELisp backend) > > Thanks. Is there a way to do that only for Emacs source files, not for all ELisp files? The beauty of TAGS is that you control what will be in it: by specifying the file names to be submitted to the 'etags' program. Only what you submit to it will be in TAGS.