unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 54454@debbugs.gnu.org
Subject: [bug#54454] [PATCH] ui: Describe package outputs.
Date: Sat, 19 Mar 2022 12:24:12 -0400	[thread overview]
Message-ID: <YjYDrIRxR4mv9tb7@jasmine.lan> (raw)
In-Reply-To: <cf9713d087089126b1f8b9102cb8f37a879fa6fd.camel@gmail.com>

On Fri, Mar 18, 2022 at 08:16:39PM +0100, Liliana Marie Prikler wrote:
> * guix/ui.scm (package->recutils): Output outputs with their descriptions,
> one per line.
> ---
> Salut Guix,
> 
> People have been complaining for a while, that outputs are not really
> discoverable [who?].  This patch attempts to fix that by displaying each
> on their own line with a (hopefully) helpful description next to it.
> It is expected, that these descriptions do not span multiple lines.

Excellent, thank you for stepping up to work on this!




  parent reply	other threads:[~2022-03-19 16:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18 19:16 [bug#54454] [PATCH] ui: Describe package outputs Liliana Marie Prikler
2022-03-18 20:12 ` Maxime Devos
2022-03-18 20:23   ` Liliana Marie Prikler
2022-03-18 20:16 ` Maxime Devos
2022-03-18 20:25   ` Liliana Marie Prikler
2022-03-18 20:50     ` Maxime Devos
2022-03-18 20:54 ` Maxime Devos
2022-03-18 22:24   ` Liliana Marie Prikler
2022-03-18 22:57     ` Maxime Devos
2022-03-18 23:27       ` Liliana Marie Prikler
2022-03-19  8:56         ` Maxime Devos
2022-03-19 10:48           ` Ludovic Courtès
2022-03-19 16:24 ` Leo Famulari [this message]
2022-06-26 12:37 ` [bug#54454] [PATCH v2] " Liliana Marie Prikler
2022-08-16 19:37   ` bug#54454: " Liliana Marie Prikler
2022-09-02 17:07     ` [bug#54454] " Ludovic Courtès
2022-09-02 17:14       ` Liliana Marie Prikler
2022-09-03  9:53         ` zimoun
2022-09-05  7:25           ` 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=YjYDrIRxR4mv9tb7@jasmine.lan \
    --to=leo@famulari.name \
    --cc=54454@debbugs.gnu.org \
    --cc=liliana.prikler@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).