From: Sergiu Ivanov <sivanov@colimite.fr>
To: SeerLite <seerlite@disroot.org>
Cc: help-guix@gnu.org, Gottfried <gottfried@posteo.de>
Subject: Re: open config.scm with sudo and gedit or emacs
Date: Sun, 12 Mar 2023 12:00:36 +0100 [thread overview]
Message-ID: <875yb6rzww.fsf@colimite.fr> (raw)
In-Reply-To: <298ACF68-632F-4B47-8B91-B785573E1123@disroot.org>
Hi SeerLite,
SeerLite <seerlite@disroot.org> [2023-03-12T00:42:42+0100]:
> On March 11, 2023 2:05:01 PM GMT-03:00, Sergiu Ivanov <sivanov@colimite.fr> wrote:
>>Gottfried <gottfried@posteo.de> [2023-03-11T11:33:33+0100]:
>>>
>>> because of my limited knowledge
>>> when opening my config.scm file with sudo
>>> I can do it only with nano
>>
>>The strategy I personally prefer is to edit a file in my home directory
>>and then sudo cp to /etc/config.scm.
>>
>>More concretely, I store my system configuration in
>>~/.config/guix/system-config.scm. I edit it with Emacs, as I would edit
>>any other normal file. When I am done editing, I do what essentially is
>>
>>sudo cp ~/.config/guix/system-config.scm /etc/config.scm
>
> Why not use the configuration from ~/.config directly? Why copy at all? I do
>
> sudo guix system reconfigure ~/.config/guix/system-config.scm
You are right, it's probably even better.
I prefer keeping my system config in /etc/config.scm because this is
what everyone seems to do, but that's probably a bad reason, supported
by unreliable data :D
-
Sergiu
next prev parent reply other threads:[~2023-03-12 11:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 10:33 open config.scm with sudo and gedit or emacs Gottfried
2023-03-11 10:57 ` Thanos Apollo
2023-03-11 11:03 ` Bruno Victal
2023-03-11 17:05 ` Sergiu Ivanov
2023-03-11 18:58 ` Kyle
2023-03-11 23:42 ` SeerLite
2023-03-12 7:07 ` Boris A. Dekshteyn
2023-03-12 9:33 ` SeerLite
2023-03-12 11:00 ` Sergiu Ivanov [this message]
2023-03-12 18:13 ` Luis Felipe
2023-03-12 19:05 ` Sergiu Ivanov
2023-03-12 13:27 ` Felix Lechner via
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=875yb6rzww.fsf@colimite.fr \
--to=sivanov@colimite.fr \
--cc=gottfried@posteo.de \
--cc=help-guix@gnu.org \
--cc=seerlite@disroot.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).