From: Jelle Licht <jlicht@fsfe.org>
To: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>,
"Guix Help" <help-guix@gnu.org>
Subject: Re: Guix System definition with a .emacs.d filled
Date: Sat, 17 Apr 2021 00:16:57 +0200 [thread overview]
Message-ID: <86y2dhkh7q.fsf@fsfe.org> (raw)
In-Reply-To: <c43f1b8fb8b00eacf72e20cc07e3d836ffb230bf.camel@korwin-zmijowski.fr>
Hello,
Jérémy Korwin-Zmijowski <jeremy@korwin-zmijowski.fr> writes:
> Dear Guixters,
>
> Maybe I am asking too much to Guix haha. Maybe I don't.
>
> So. Here is what I intend to do :
>
> I want to write a Guix System definition that puts a .emacs.d directory
> inside /root which is "usable". I don't feel the need to create a
> regular user (I don't fear too much damages inside a disposable VM
> context).
> So I tried two options :
>
> First, using an extra-special-file
>
> (extra-special-file "/root/.emacs.d"
> (local-file "emacs.d" #:recursive? #t))
>
> But the resulting .emacs.d is put into the store and is not writable.
I ran into a similar issue some time ago, with the same dillema.
The 'solution' that works well enough for me:
the `emacs-no-littering' package, with
(setq no-littering-etc-directory "/tmp/emacs/etc")
no-littering-var-directory "/tmp/emacs/var"))
HTH!
- Jelle
next prev parent reply other threads:[~2021-04-16 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 22:30 Guix System definition with a .emacs.d filled Jérémy Korwin-Zmijowski
2021-04-16 14:06 ` Joshua Branson
2021-04-16 21:04 ` Jérémy Korwin-Zmijowski
2021-04-17 13:53 ` Joshua Branson
2021-04-16 22:16 ` Jelle Licht [this message]
2021-04-17 8:35 ` Jérémy Korwin-Zmijowski
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86y2dhkh7q.fsf@fsfe.org \
--to=jlicht@fsfe.org \
--cc=help-guix@gnu.org \
--cc=jeremy@korwin-zmijowski.fr \
/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).