From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: "M-x guix" - magit-like interface for guix commands
Date: Wed, 26 Aug 2015 14:35:41 +0300 [thread overview]
Message-ID: <87wpwiwacy.fsf@gmail.com> (raw)
In-Reply-To: <87mvxfgjiq.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 25 Aug 2015 23:12:13 +0200")
Ludovic Courtès (2015-08-26 00:12 +0300) wrote:
> Alex Kost <alezost@gmail.com> skribis:
>
>> Thompson, David (2015-08-14 17:40 +0300) wrote:
[...]
>>> depending on Magit is too heavy a dependency.
>>
>> It does not depend on the whole Magit but only on a single
>> "magit-popup.el" file which may be installed separately (available on
>> Melpa, for example). So potentially we can make a package just for this
>> library and use it.
>>
>> However, according to its manual¹, it will be superseded by a general
>> library which will not be a part of magit, so eventually it will be a
>> light-weight dependency I think.
>>
>> Anyway, we already have a heavy dependency for Emacs interface (Geiser).
>
> Yes, but Geiser is an “obvious” one that cannot be avoided.
>
> I haven’t tested wip-emacs-popup-ui yet because I have yet to switch to
> Magit 2 (I’m slightly afraid of breaking my workflow, maybe unreasonably
> so!).
Magit2 broke my workflow completely when I switched to it several months
ago, and it took some time to set it up for my needs.
> That said, since the functionality is in a separate file, people who
> don’t have magit-popup.el can just choose to not use M-x guix while
> still being available to use the other features, right?
Yes. I think I'll mention in the manual that it is an optional
dependency used for “M-x guix”.
>>> I noticed an 'e' for 'environment'. I imagine that's just a placeholder. ;)
>>
>> Not really, all commands (including 'environment') are ready to use.
>> You just specify the options you want in the magit manner and then you run
>> "Execute" action. And the specified command is executed in Guix REPL.
>>
>> Specifically for 'environment' it may lead to a very interesting result
>> as it will spawn an external process, unless --dry-run or --search-paths
>> options were specified. But still it will… let's say… work, but only if
>> a user is brave enough to try it ;)
>
> :-)
>
> It Would Be Nice to have, say, M-x guix-compile-in-environment, which
> would be like M-x compile but just run the thing in ‘guix environment’.
> Just thought I’d mention this in passing. ;-)
Yes, I remember about emacs+environment wishes, but I don't promise
anything :-(
>> Also along with "execute in REPL" action I'm going to add 2 more default
>> actions for each command:
>>
>> - "execute in shell" — this will be a complete alternative to writing a
>> full command manually in a shell buffer.
>>
>> - "copy the command line" — i.e., to put the specified command arguments
>> into kill ring, so later a user could do with it whatever he wants.
>
> (he or she)
>
> Sounds like more exciting stuff ahead!
If you mean those 2 actions, they were implemented a couple of days
later.
> Thanks for your creativity & hack power!
Thank you very much!
--
Alex
next prev parent reply other threads:[~2015-08-26 11:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 8:19 "M-x guix" - magit-like interface for guix commands Alex Kost
2015-08-14 14:40 ` Thompson, David
2015-08-15 15:29 ` Alex Kost
2015-08-25 21:12 ` Ludovic Courtès
2015-08-26 11:35 ` Alex Kost [this message]
2015-08-25 21:14 ` Ludovic Courtès
2015-08-26 11:05 ` Alex Kost
2015-08-28 9:37 ` Ludovic Courtès
2015-08-28 20:08 ` Alex Kost
2015-08-29 16:01 ` Ludovic Courtès
2015-08-30 9:35 ` Alex Kost
2015-08-30 11:48 ` Ludovic Courtès
2015-08-30 15:28 ` 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=87wpwiwacy.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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).