all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Spencer Baugh <sbaugh@janestreet.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Changing site-lisp without installing it
Date: Thu, 03 Aug 2023 11:58:14 -0400	[thread overview]
Message-ID: <ierv8dw86eh.fsf@janestreet.com> (raw)
In-Reply-To: 838raszqfw.fsf@gnu.org

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Spencer Baugh <sbaugh@janestreet.com>
>> 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.




  reply	other threads:[~2023-08-03 15:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 21:14 Changing site-lisp without installing it Spencer Baugh
2023-08-03  0:25 ` Emanuel Berg
2023-08-03  4:43 ` Eli Zaretskii
2023-08-03 15:58   ` Spencer Baugh [this message]
2023-08-03 16:05     ` Eli Zaretskii
2023-08-03 18:46       ` Spencer Baugh
2023-08-04  5:19         ` Eli Zaretskii
2023-08-03 16:10     ` Emanuel Berg

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=ierv8dw86eh.fsf@janestreet.com \
    --to=sbaugh@janestreet.com \
    --cc=help-gnu-emacs@gnu.org \
    /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.