From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: 22587@debbugs.gnu.org, myglc2 <myglc2@gmail.com>
Subject: bug#22587: ‘guix edit’ & ‘M-x guix-edit' typo, rename, & mode change
Date: Mon, 08 Feb 2016 16:30:39 +0100 [thread overview]
Message-ID: <878u2vfcdc.fsf@gnu.org> (raw)
In-Reply-To: <87oabrr460.fsf@gmail.com> (Alex Kost's message of "Mon, 08 Feb 2016 11:34:47 +0300")
Alex Kost <alezost@gmail.com> skribis:
> myglc2 (2016-02-07 21:04 +0300) wrote:
[...]
>> Calling these functions 'guix edit' and 'M-x guix-edit' implies that the
>> user will be able to modify the recipe, but this is not actually the
>> case. The functions should be given a more informative and accurate
>> name, such as: 'guix view', 'guix inspect', or 'guix examine'.
>
> Along with the package recipes that come with Guix, a user can also have
> his/her own packages (specified using GUIX_PACKAGE_PATH env var), and
> "guix edit my-super-package" opens a user's file with this package. It
> is highly likely that this file is editable, so "guix edit" is a perfect
> name in this case I think. IMO it's a user responsibility to understand
> what files can be edited and what cannot.
I sympathize with the frustration of myglc2, but I agree with you Alex.
> But I agree that this may be confusing, so maybe we should clarify the
> manual to explain in (info "(guix) Invoking guix edit") that store files
> must not be edited.
Yes. Can one of you propose a way to phrase it?
I also had in mind that ‘someday’ we could have:
guix edit --clone foo
which would automatically open, say,
~/.config/guix/personal/packages.scm with a template like:
(define-module (personal packages)
#:use-module (guix packages)
#:use-module (gnu packages foo))
(define-public my-foo
(package
(inherit foo)
(name "foo-personal")))
It’s a bit of work, but it’d be nice.
Ludo’.
next prev parent reply other threads:[~2016-02-08 18:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 18:04 bug#22587: ‘guix edit’ & ‘M-x guix-edit' typo, rename, & mode change myglc2
2016-02-07 18:58 ` Andreas Enge
2016-02-07 19:22 ` myglc2
2016-02-07 19:34 ` Andreas Enge
2016-02-07 20:26 ` myglc2
2016-02-08 8:34 ` Alex Kost
2016-02-08 15:30 ` Ludovic Courtès [this message]
2016-02-08 18:29 ` myglc2
2016-04-18 8:37 ` Alex Kost
2016-04-18 17:41 ` Ludovic Courtès
2016-04-19 8:18 ` Alex Kost
2016-04-19 10:50 ` Ludovic Courtès
2016-04-20 7:20 ` Alex Kost
2016-04-20 15:31 ` Ludovic Courtès
2016-04-21 10:40 ` Alex Kost
2016-06-02 19:40 ` Ludovic Courtès
2016-06-03 19:04 ` Alex Kost
2016-06-04 11:21 ` Ludovic Courtès
2016-04-18 21:10 ` myglc2
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=878u2vfcdc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=22587@debbugs.gnu.org \
--cc=alezost@gmail.com \
--cc=myglc2@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).