From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: myglc2 <myglc2@gmail.com>, 22550@debbugs.gnu.org
Subject: bug#22550: (require 'magit) produces error: "no such file or directory" "dash"
Date: Sat, 06 Feb 2016 13:38:49 +0100 [thread overview]
Message-ID: <87h9hm2eue.fsf@gnu.org> (raw)
In-Reply-To: <87si16n7q5.fsf@gmail.com> (Alex Kost's message of "Sat, 06 Feb 2016 00:54:42 +0300")
Alex Kost <alezost@gmail.com> skribis:
> myglc2 (2016-02-05 17:52 +0300) wrote:
[...]
>> 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.
Yes, that would be nice. However, AIUI, it would require spawning a new
Guix REPL for this specific ‘guix-directory’ value, no?
Ludo’.
next prev parent reply other threads:[~2016-02-06 12:40 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 [this message]
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=87h9hm2eue.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=22550@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).