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 14:46:00 -0400 [thread overview]
Message-ID: <ierr0ok7ymv.fsf@janestreet.com> (raw)
In-Reply-To: 83wmycw1pi.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Spencer Baugh <sbaugh@janestreet.com>
>> Date: Thu, 03 Aug 2023 11:58:14 -0400
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > 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?
>
> Yes.
>
>> Don't you need root to change that one? Isn't that inconvenient?
>
> On my systems, I have the root privileges, so this isn't inconvenient.
> Why don't you on your systems? I understand that you are the de-facto
> administrator, since you set up things for your users?
I do, yes.
> Anyway, what's inconvenient in using the system-wide site-lisp? If
> access rights is the issue, Tramp should solve that cleanly, I think.
It just seems less convenient to have to use TRAMP to edit the files.
Doing everything in ~/.emacs.d avoids the access rights issue; it's not
shared, but that's fine since there's only one user in your case (I
assume?). For my personal configuration on my personal machines, I
generally try to configure things in ~ as much as possible, since all
system-wide configuration has the hassle of access rights.
Thanks for sharing your workflow though, it's interesting to hear that
site-lisp works well for this.
Do you install packages into site-lisp, too? Or, what in general do you
put in site-lisp?
Do you use site-start.el? default.el? I definitely hope to use those,
too.
next prev parent reply other threads:[~2023-08-03 18:46 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
2023-08-03 16:05 ` Eli Zaretskii
2023-08-03 18:46 ` Spencer Baugh [this message]
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=ierr0ok7ymv.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.