From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 4/4] emacs: Add "Build Log" button to Package Info.
Date: Wed, 01 Jun 2016 23:04:09 +0200 [thread overview]
Message-ID: <87zir4ei46.fsf@gnu.org> (raw)
In-Reply-To: <87fusy3pfz.fsf@gmail.com> (Alex Kost's message of "Wed, 01 Jun 2016 00:09:04 +0300")
Alex Kost <alezost@gmail.com> skribis:
> Ludovic Courtès (2016-05-31 00:17 +0300) wrote:
[...]
>> I think having this extra info and extra buttons is nice. I wonder
>> though if in the future we should have a way to hide non-essential info
>> and buttons, so that someone who just wants to search and install/remove
>> software isn’t overwhelmed.
>>
>> What are your thoughts?
>
> I agree that there may be too much buttons for a new user, but I
> wouldn't like to hide features by default. For users, there is
> 'guix-package-info-format' variable. It is a bit complicated but it
> allows to control any aspect of *Guix Package Info* buffer. For
> example, one could hide all non-essential info like this:
>
> (setq guix-package-info-format
> '(guix-package-info-insert-heading
> (outputs ignore guix-package-info-insert-outputs)))
OK, makes sense. Let’s keep it this way for now.
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-06-01 21:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 14:36 [PATCH 1/4] emacs: Show built output directories in Package Info Alex Kost
2016-05-28 14:36 ` [PATCH 2/4] emacs: Extend 'guix-mapinsert' Alex Kost
2016-05-30 21:14 ` Ludovic Courtès
2016-05-28 14:36 ` [PATCH 3/4] emacs: Add "Build" button to Package Info Alex Kost
2016-05-30 21:15 ` Ludovic Courtès
2016-05-28 14:36 ` [PATCH 4/4] emacs: Add "Build Log" " Alex Kost
2016-05-30 21:17 ` Ludovic Courtès
2016-05-31 21:09 ` Alex Kost
2016-06-01 21:04 ` Ludovic Courtès [this message]
2016-05-30 21:13 ` [PATCH 1/4] emacs: Show built output directories in " 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=87zir4ei46.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.