From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Spencer Baugh Newsgroups: gmane.emacs.help Subject: Re: Changing site-lisp without installing it Date: Thu, 03 Aug 2023 11:58:14 -0400 Message-ID: References: <838raszqfw.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10296"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: help-gnu-emacs@gnu.org Cancel-Lock: sha1:f/5W3PGYT2f3B8zjR6LbvgvPFc4= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Thu Aug 03 17:58:59 2023 Return-path: Envelope-to: geh-help-gnu-emacs@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 1qRaj5-0002UM-0z for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 03 Aug 2023 17:58:59 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qRaie-0004S5-6v; Thu, 03 Aug 2023 11:58:32 -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 1qRaiY-0004Kd-0Y for help-gnu-emacs@gnu.org; Thu, 03 Aug 2023 11:58:27 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qRaiW-00073K-4G for help-gnu-emacs@gnu.org; Thu, 03 Aug 2023 11:58:25 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1qRaiU-0001jM-CY for help-gnu-emacs@gnu.org; Thu, 03 Aug 2023 17:58:22 +0200 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=geh-help-gnu-emacs@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:144570 Archived-At: Eli Zaretskii writes: >> From: Spencer Baugh >> Date: Wed, 02 Aug 2023 17:14:51 -0400 >> >> >> I want to start using site-lisp at my site. But I'm not sure how to >> hack on changed versions of the site-lisp, without installing it. >> >> What would be ideal for me is this: >> >> - There is a normal, installed Emacs, with a site-lisp directory. My >> users run this and get the installed site-lisp directory. All normal. >> >> - I run this same Emacs binary in some way, I don't know how, to make it >> use a replacement site-lisp directory, instead of the installed one, >> so that I can hack on the site-lisp, without having to build a new >> Emacs or change the actual installed site-lisp directory. >> >> Now that I say all this, I guess the obvious thing to do is simply pass >> >> --no-site-lisp --directory my/local/changed/site-lisp >> >> and then hack away. >> >> But will that behave correctly? Are there any footguns there? >> >> (Does anyone actually use site-lisp? It seems a little under-explored, >> but I think it will be really useful at my site, so that people can >> easily run "emacs -q" to get an emacs with only the site configuration >> which should help with debugging their problems) > > I use site-lisp, if by that you mean the site-lisp directory that is > put on load-path. The system-wide one in /usr/share/emacs/site-lisp? Don't you need root to change that one? Isn't that inconvenient? That's the one I mean, anyway. > I don't really understand what is it that you are trying to > accomplish, but one aspect that might be relevant is that there are 2 > site-lisp: one is specific to the Emacs version, the other one is not > (so is visible to all Emacs versions). Ah, yes, that is relevant. But I expect to compile a new Emacs binary with a different --prefix each time I change site-lisp anyway, so each site-lisp will be specific to an individual Emacs binary.