unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: zimoun <zimon.toutoune@gmail.com>
Cc: "guix-devel\\\\@gnu.org" <guix-devel@gnu.org>
Subject: Re: guix describe user experience improvement proposition
Date: Tue, 12 May 2020 20:13:49 +0000	[thread overview]
Message-ID: <EUEVdh_a1BlxNIhjkVLQTIo-y24OJ8S0qzf2gLybQPO6Bp8_jVfiECCfCXsX2R4-zF9qTmqVI46eq97350y_rspdUbi6u-CI8JODgKFhotY=@elenq.tech> (raw)
In-Reply-To: <CAJ3okZ1Z7M_dsO4Wi70OGpi_AkJihvq0E-YyXe7zcLOOw5bZLg@mail.gmail.com>

On Tuesday, May 12, 2020 9:44 PM, zimoun <zimon.toutoune@gmail.com> wrote:

> Dear
>
> On Tue, 12 May 2020 at 21:07, Ekaitz Zarraga ekaitz@elenq.tech wrote:
>
> > I suggest adding the possible format list in the help of the `guix describe -h` command. That way the feature discovery is easier for users that don't want to dig in the code.
>
> Usually, the way to add such information is '--list-formats', e.g.,
> see "guix graph"with '--list-types' and '-list-backends'. I do not
> know if it is an usually. ;-)

But do you think it's interesting?
Or is it just me?

I like the `--list-types` approach. If it's interesting I would contribute with a patch.

> > -   (display (G_ "
> > -   -f, --format=FORMAT display information in the given FORMAT"))
> >
> > -   (display (string-append (G_ "
> > -   -f, --format=FORMAT display information in the given FORMAT: ") (string-join available-formats "|")))
>
> The issue is the length, so at least it should on 2 lines to fix screen size.

Yeah I was aware of that. I was just adding the diff to try to share what I wanted, rather than like something we should add with no changes. :)

Thanks for the feedback!

Ekaitz


  reply	other threads:[~2020-05-12 20:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 19:07 guix describe user experience improvement proposition Ekaitz Zarraga
2020-05-12 19:44 ` zimoun
2020-05-12 20:13   ` Ekaitz Zarraga [this message]
2020-05-12 22:20     ` Ekaitz Zarraga

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='EUEVdh_a1BlxNIhjkVLQTIo-y24OJ8S0qzf2gLybQPO6Bp8_jVfiECCfCXsX2R4-zF9qTmqVI46eq97350y_rspdUbi6u-CI8JODgKFhotY=@elenq.tech' \
    --to=ekaitz@elenq.tech \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@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).