From: myglc2 <myglc2@gmail.com>
To: 22587@debbugs.gnu.org
Subject: bug#22587: ‘guix edit’ & ‘M-x guix-edit' typo, rename, & mode change
Date: Sun, 07 Feb 2016 13:04:40 -0500 [thread overview]
Message-ID: <8737t4jt1j.fsf@gmail.com> (raw)
Alex Kost <alezost@gmail.com> writes:
[...]
> The purpose of "M-x guix-edit" Emacs command (and "guix edit" shell
> command) is just to show you the source code of the package. This
> source is usually placed in the store, and you shouldn't edit it. If
> you are going to contribute to guix, (info "(guix) Building from Git")
> is the right way.
From guix INFO:
6.2 Invoking ‘guix edit’
[...]
launches the program specified in the ‘VISUAL’ or in the ‘EDITOR’
environment variable to edit the recipe of GCC 4.8.4 and that of Vim."
TYPO:
"edit" (last line above) should be replaced with "view", "inspect", or
"examine".
RENAME:
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'.
MODE CHANGE:
In emacs, read-only .scm files should be opened in view-mode.
next reply other threads:[~2016-02-07 18:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 18:04 myglc2 [this message]
2016-02-07 18:58 ` bug#22587: ‘guix edit’ & ‘M-x guix-edit' typo, rename, & mode change 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
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=8737t4jt1j.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=22587@debbugs.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 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).