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: Tue, 08 Mar 2016 12:25:50 +0300 [thread overview]
Message-ID: <87r3flmich.fsf@gmail.com> (raw)
In-Reply-To: <87mvqadpid.fsf@gmail.com> (myglc2@gmail.com's message of "Mon, 07 Mar 2016 15:03:38 -0500")
myglc2 (2016-03-07 23:03 +0300) wrote:
> Alex Kost <alezost@gmail.com> writes:
>
> [...]
>
>> No, I mean it is fixed in the current master, but as I wrote¹ it will
>> take effect only after we update our "guix" package. Currently it is
>> "guix-devel" package at commit c3f29bc², which is older then commit
>> 004ea62 (that fixed this issue).
>>
>> After we update "guix" package (either via updating "guix-devel"
>> snapshot or via pointing "guix" to "guix-0.9.1" after the new release),
>> this will be finally fixed.
>>
>> ¹ http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22550#38
>> ²
>> http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/package-management.scm#n198
>
> Thank you. Sorry you had to explain this twice :(
>
> I re-read your earlier posts. AIUI now, in order to use the latest guix
> emacs features from 'git checkout master' one must add to emacs init:
>
> (let ((dir "~/src/guix/emacs"))
> (add-to-list 'load-path dir)
> (setq guix-load-path dir)
> (require 'guix-init nil t))
Yes, this is the recommended way of setting it up. It is described in
(info "(guix) Emacs Initial Setup").
> Do you think we should we add that to (info "(guix) Building from Git") ?
Since it is already described in the other section, it shouldn't be
duplicated, but we can add a cross reference, not into "Building from
Git" though, maybe to (info "(guix) The Perfect Setup")
--
Alex
next prev parent reply other threads:[~2016-03-08 9:26 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
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 [this message]
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=87r3flmich.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).