From: Alex Kost <alezost@gmail.com>
To: myglc2 <myglc2@gmail.com>
Cc: 22550@debbugs.gnu.org
Subject: bug#22550: (require 'magit) produces error: "no such file or directory" "dash"
Date: Sat, 06 Feb 2016 00:54:42 +0300 [thread overview]
Message-ID: <87si16n7q5.fsf@gmail.com> (raw)
In-Reply-To: <87oabv1a75.fsf@gmail.com> (myglc2@gmail.com's message of "Fri, 05 Feb 2016 09:52:14 -0500")
myglc2 (2016-02-05 17:52 +0300) wrote:
> 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.
>>
>> For "M-x guix-edit", there is a trick that allows to point to any place
>> with packages — setting 'guix-directory' variable. For example, if you
>> cloned guix to "~/src" directory, after:
>>
>> (setq guix-directory "~/src/guix")
>>
>> "M-x guix-edit magit" will open "~/src/guix/gnu/packages/emacs.scm" file.
>
> Thank you Alex. This really helps me. FWIW, Here are a couple thoughts:
>
> It was confusing to me that 'guix-edit' shows "Note: file is write
> protected". This behavior made me wonder what was wrong with my setup
> and/or my understanding.
Nothing is wrong. What you describe is a common Emacs thing when you
open a read-only file. Emacs displays this message because you open a
file from /gnu/store (which is read-only). If you run:
touch /tmp/foo ; chmod 444 /tmp/foo
and then open this /tmp/foo file in Emacs, you'll get the same message.
> This might be improved by:
>
> 1) expanding one of the messages: "Note: file is write protected", or
> 'command-execute: Buffer is read-only: #<buffer screen.scm>' to say,
> if you want to modify guix see "8.1 Building from Git".
These messages come from Emacs itself, not from any guix code, so I
don't see how to change it (and I actually wouldn't like to do it, as I
think changing a default Emacs behaviour would be more confusing)
> - or -
>
> a) rename the current 'guix-edit' function to guix-inspect',
> 'guix-examine', or'guix-view'.
"M-x guix-edit" Emacs command was named so after "guix edit" shell
command. I think having "M-x guix-view" which will do the same as "guix
edit" in shell and "M-x guix-edit" which will do something else will be
confusing.
> b) make a new/improved 'guix-edit' that prompts for guix-directory if it
> is not already not set, perhaps also refering the user to "8.1
> Building from Git".
As I see it, 'M-x guix-edit' should do the same as 'guix edit' in shell,
i.e. it should open a package file without additional prompting. OTOH I
think it would be good to improve 'guix-edit' so that with C-u it will
prompt for a directory with guix packages.
--
Alex
next prev parent reply other threads:[~2016-02-05 21:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 4:15 bug#22550: (require 'magit) produces error: "no such file or directory" "dash" myglc2
2016-02-04 13:17 ` Alex Kost
2016-02-04 15:16 ` myglc2
2016-02-04 20:00 ` Alex Kost
2016-02-04 23:40 ` myglc2
2016-02-05 8:43 ` Alex Kost
2016-02-05 14:52 ` myglc2
2016-02-05 21:54 ` Alex Kost [this message]
2016-02-06 12:38 ` Ludovic Courtès
2016-02-07 8:14 ` Alex Kost
2016-02-08 9:22 ` Ludovic Courtès
2016-02-10 7:46 ` Alex Kost
2016-02-07 8:56 ` Alex Kost
2016-02-08 2:52 ` myglc2
2016-02-08 9:19 ` Alex Kost
2016-03-06 14:47 ` myglc2
2016-03-07 9:14 ` Alex Kost
2016-03-07 20:03 ` myglc2
2016-03-08 9:25 ` Alex Kost
2016-03-08 13:49 ` myglc2
2016-03-09 10:58 ` Alex Kost
2016-03-09 14:47 ` myglc2
2016-03-24 16:20 ` Alex Kost
2016-03-25 15:20 ` myglc2
2016-03-26 0:08 ` Alex Kost
2016-03-26 2:51 ` myglc2
2016-02-08 9:55 ` bug#22550: Fixed Alex Kost
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=87si16n7q5.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=22550@debbugs.gnu.org \
--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).