unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Spencer Baugh <sbaugh@janestreet.com>
To: help-gnu-emacs@gnu.org
Subject: Changing site-lisp without installing it
Date: Wed, 02 Aug 2023 17:14:51 -0400	[thread overview]
Message-ID: <ier4jlh9mes.fsf@janestreet.com> (raw)


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)




             reply	other threads:[~2023-08-02 21:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 21:14 Spencer Baugh [this message]
2023-08-03  0:25 ` Changing site-lisp without installing it Emanuel Berg
2023-08-03  4:43 ` Eli Zaretskii
2023-08-03 15:58   ` Spencer Baugh
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ier4jlh9mes.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).