all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Rodrigo Morales <moralesrodrigo1100@gmail.com>, help-guix@gnu.org
Subject: Re: Newbie: Why using "guix edit" opens read-only files in /gnu/store?
Date: Sat, 24 Jun 2023 20:50:25 -0700	[thread overview]
Message-ID: <87sfag19q6.fsf@wireframe> (raw)
In-Reply-To: <CAGxMbPbF8OQeWmO8_04wuGq_7aEfHBqq6w93Fp1L-BRYQJpQzQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 897 bytes --]

On 2023-06-25, Rodrigo Morales wrote:
> From what I understand, no file in `/gnu/store' can be edited by any
> user. My question is: Isn't the purpose of `guix edit' edit package
> definitions? Then, why when `guix edit <<package>>' is executed, a file
> under /gnu/store is shown? For the record, I just executed `guix edit
> emacs' and the file
> /gnu/store/nxy09dxmm23krdgszgww2v80v8bkcll5-guix-module-union/share/guile/site/3.0/gnu/packages/emacs.scm
> was opened.

It is certainly confusing, and has come a few times. It would be more
ideal to copy that file somewhere where it can be edited than trying to
edit the file in the store directly.

It is still useful when building from git, as described in:

  https://guix.gnu.org/en/manual/devel/en/guix.html#Building-from-Git

Then this should work more-or-less as one might expect:

  ./pre-inst-env guix edit PACKAGE


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

      reply	other threads:[~2023-06-25  3:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-25  3:14 Newbie: Why using "guix edit" opens read-only files in /gnu/store? Rodrigo Morales
2023-06-25  3:50 ` Vagrant Cascadian [this message]

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=87sfag19q6.fsf@wireframe \
    --to=vagrant@debian.org \
    --cc=help-guix@gnu.org \
    --cc=moralesrodrigo1100@gmail.com \
    /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/guix.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.