all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] emacs: Improve interface for working with multiple profiles.
Date: Fri, 17 Oct 2014 23:34:40 +0200	[thread overview]
Message-ID: <87r3y61itr.fsf@gnu.org> (raw)
In-Reply-To: <87r3y6s8dx.fsf@gmail.com> (Alex Kost's message of "Sat, 18 Oct 2014 01:18:02 +0400")

Alex Kost <alezost@gmail.com> skribis:

> Ludovic Courtès (2014-10-17 23:29 +0400) wrote:
>
>> Alex Kost <alezost@gmail.com> skribis:
>
> [...]
>
>> What about renaming ‘guix-set-current-profile’ to
>> ‘guix-set-default-profile’?  Because now, what it does is just to define
>> the profile that is used when C-u isn’t used, right?
>
> Right, but I think it shouldn't be renamed as "default profile" and
> "current profile" have different meanings there:
>
> - default profile is "/var/guix/profiles/per-user/user/guix-profile" (or
>   whatever) and it is “fixed”;
>
> - current profile is used by commands (as you pointed) and it may be
>   changed.
>
> For example, a user decides to look at generations and installed
> packages of some profile.  So he may "M-x guix-set-current-profile ...",
> then "M-x guix-generations" and "M-x guix-installed-packages".  After
> that he could switch to another profile or to a default profile using
> "C-u M-x guix-set-current-profile".
>
> (there are even 2 variables: guix-default-profile and
> guix-current-profile)

OK, let’s keep it as ‘guix-set-current-profile’ then.

> Hawk eye :-)

Heheh.  :-)

OK to commit with those little changes!

Ludo’.

      reply	other threads:[~2014-10-17 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 18:44 [PATCH] emacs: Improve interface for working with multiple profiles Alex Kost
2014-10-17 19:29 ` Ludovic Courtès
2014-10-17 21:18   ` Alex Kost
2014-10-17 21:34     ` Ludovic Courtès [this message]

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=87r3y61itr.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --cc=guix-devel@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.