From: myglc2 <myglc2@gmail.com>
To: help-guix@gnu.org
Subject: Re: M-x guix bug
Date: Thu, 30 Jun 2016 13:16:18 -0400 [thread overview]
Message-ID: <86y45mfvh9.fsf@gmail.com> (raw)
In-Reply-To: 87poqyagi0.fsf@gmail.com
Alex Kost <alezost@gmail.com> writes:
> John J Foerch (2016-06-29 04:43 +0300) wrote:
>
>> ludo@gnu.org (Ludovic Courtès) writes:
>>
>>> Hi!
>>>
>>> John J Foerch <jjfoerch@earthlink.net> skribis:
>>>
>>>> On a fresh guix installation with only a few packages installed, M-x
>>>> guix in emacs produced the following error:
>>>>
>>>> Cannot open load file: no such file or directory, magit-popup
>>>>
>>>> It seems that guix's emacs components have an unlisted magit dependency.
>>>
>>> The dependency is documented (info "(guix) Emacs Initial Setup"), but
>>> note that it’s only necessary if you use the M-x guix popup.
>>>
>>> Without magit-popup, you can still use M-x
>>> guix-newest-available-packages, M-x guix-prettify-mode, M-x
>>> guix-licenses, and so on.
>>
>> Okay, good to know. I think that a helpful message instead of an error
>> would be appropriate, or perhaps some way of not exposing the 'guix'
>> command if magit is not installed.
>
> I think the right thing would be to make "M-x guix" work by default.
> This can be done simply by adding 'magit-popup' dependency (i.e., by
> adding it to 'propagated-inputs') to our 'guix' package.
I agree. I don't use magit popup, but IMO, the less installation &/or
config required to enable features described in the manual, the better.
> But if I
> understood correctly, Ludovic wouldn't like to do it:
> <http://lists.gnu.org/archive/html/guix-devel/2015-08/msg00576.html>
Looked at this tread but don't see this point made.
next prev parent reply other threads:[~2016-06-30 17:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 10:29 M-x guix bug John J Foerch
2016-06-28 21:58 ` Ludovic Courtès
2016-06-29 1:43 ` John J Foerch
2016-06-30 14:38 ` Alex Kost
2016-06-30 17:16 ` myglc2 [this message]
2016-07-01 9:07 ` Alex Kost
2016-06-30 17:46 ` John J Foerch
2016-06-30 21:21 ` Ludovic Courtès
2016-07-01 2:48 ` myglc2
2016-07-01 9:02 ` Alex Kost
2016-07-01 9:30 ` Ludovic Courtès
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=86y45mfvh9.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=help-guix@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.