unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: guix package is slow
Date: Mon, 02 Jul 2018 23:28:01 +0300	[thread overview]
Message-ID: <87h8lhgz72.fsf@gmail.com> (raw)
In-Reply-To: <87lgatu1px.fsf@gmail.com> (Maxim Cournoyer's message of "Mon, 02 Jul 2018 10:55:06 -0400")

Maxim Cournoyer (2018-07-02 10:55 -0400) wrote:

> Hi,
>
> Oleg Pykhalov <go.wigust@gmail.com> writes:
>
>> Hello,
>>
>> Pierre Neidhardt <ambrevar@gmail.com> writes:
>>
>>> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>>>
>>>>> - Perform transactions (install/remove) over multiple packages.
>>>>
>>>> To be fair, I think you can already accomplish this using emacs-guix by
>>>> separating with commas multiple package names :).
>>>
>>> Can you explain?  I don't know how to do that.
>>>
>>> The point of the Helm interface is that it allows to "batch select"
>>> multiple packages.  I don't think that emacs-guix can do that.
>>
>> […]
>>
>> Another way in ‘M-x guix-all-packages’ or any ‘guix-search-by-*’:
>>
>>   • Hit ‘i’ on not installed packages.
>>   • Hit ‘d’ on installed package.
>>   • Hit ‘x’ to apply.
>
> Thanks Oleg! I keep forgetting about this interface;

he-he, it is only one of about 10 different interfaces of this kind (for
packages, profiles, generations, services, etc.).  If you use only "M-x
guix", you miss most of Emacs-Guix features.

> there doesn't seem
> to be an entry point from M-x guix for easy discovery.

"M-x guix" can't be an entry point for this or any other interface, it
is only for "guix" *shell* commands.  Actually I'm very surprised
someone uses "M-x guix", I find it unpractical.  I even plan to rename
it to "M-x guix-command", and to make "M-x guix" a real entry point for
the various Emacs-Guix commands (including "guix-command" and all the
interfaces).

-- 
Alex

  reply	other threads:[~2018-07-02 20:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-30 15:20 guix package is slow swedebugia
2018-06-30 15:25 ` Pierre Neidhardt
2018-07-01 15:34   ` Maxim Cournoyer
2018-07-01 18:50     ` Pierre Neidhardt
2018-07-01 19:33       ` Maxim Cournoyer
2018-07-01 19:41         ` Pierre Neidhardt
2018-07-01 20:18           ` Maxim Cournoyer
2018-07-01 20:32             ` Pierre Neidhardt
2018-07-02  1:04           ` Oleg Pykhalov
2018-07-02 14:55             ` Maxim Cournoyer
2018-07-02 20:28               ` Alex Kost [this message]
2018-07-03 17:06                 ` swedebugia
2018-07-03 19:39                 ` Ludovic Courtès
2018-07-08 16:05                 ` Maxim Cournoyer
2018-07-09 16:42                 ` George Clemmer
2018-07-10  2:45                   ` Oleg Pykhalov
2018-07-02 20:39           ` Alex Kost
2018-07-01 15:32 ` Maxim Cournoyer
2018-07-02 10:20   ` Ludovic Courtès
2018-07-02 15:48     ` Maxim Cournoyer
2018-07-02 13:36 ` ‘package-transitive-supported-systems’ " 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

  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=87h8lhgz72.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@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).