From: myglc2 <myglc2@gmail.com>
To: 22550@debbugs.gnu.org
Subject: bug#22550: (require 'magit) produces error: "no such file or directory" "dash"
Date: Fri, 05 Feb 2016 09:52:14 -0500 [thread overview]
Message-ID: <87oabv1a75.fsf@gmail.com> (raw)
In-Reply-To: <87egctdsb0.fsf@gmail.com>
Alex Kost <alezost@gmail.com> writes:
> myglc2 (2016-02-05 02:40 +0300) wrote:
>
> [...]
>>> Right now I can't check it, but I think if you start emacs like this:
>>>
>>> EMACSLOADPATH=/etc/emacs: emacs
>>>
>>> you'll get "M-x guix-…" commands. Could you confirm?
>>
>> Yes that works.
>>
>> ... and then if I do
>>
>> '(guix-emacs-load-autoloads "/run/current-system/profile")'
>>
>> 'M-x magit-status' works.
>
> Thanks for confirming. It will be fixed soon.
>
>> I am a little confused (not your fault). May I ask an off-topic
>> question?
>
> Sure.
>
>> It seems that doing ... 'M-x guix-edit foo.scm' ... amounts to hacking
>
> just "foo" without ".scm" ---------------^^^^^^^
> (BTW package names are completed if you press TAB)
>
>> guix.
>>
>> However '8.1 Building from Git' says, "If you want to hack Guix itself,
>> it is recommended to use the latest version from the Git repository."
>> ... and goes on to describe a different approach.
>>
>> Can you comment on which approach is best for which situation.
>
> 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.
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".
- or -
a) rename the current 'guix-edit' function to guix-inspect',
'guix-examine', or'guix-view'.
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".
c) possibly allow "warping" from "guix-inspect" to "guix-edit".
next prev parent reply other threads:[~2016-02-05 14:53 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 [this message]
2016-02-05 21:54 ` Alex Kost
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oabv1a75.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=22550@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 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.