From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Changing site-lisp without installing it
Date: Thu, 03 Aug 2023 02:25:41 +0200 [thread overview]
Message-ID: <87edklkm4a.fsf@dataswamp.org> (raw)
In-Reply-To: ier4jlh9mes.fsf@janestreet.com
Spencer Baugh wrote:
> I want to start using site-lisp at my site.
site = multi-user computer system, settings in site-lisp will
be shared across users.
> 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?
Many, instead just add a file to the original path with
whatever settings you wish to enforce across the realm ...
> (Does anyone actually use site-lisp? It seems a little
> under-explored [...]
Collective settings, I don't think that idea is so useful.
Whose .emacs are we gonna base it on, the "site" boss?
Maybe one can share other stuff that makes more sense ...
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-08-03 0:25 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 [this message]
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=87edklkm4a.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--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).