From: "Ludovic Courtès" <ludo@gnu.org>
To: 54307@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Julien Lepiller" <julien@lepiller.eu>,
"Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Subject: [bug#54307] [PATCH 0/2] Highlight headings showing what to build/download
Date: Wed, 9 Mar 2022 10:57:10 +0100 [thread overview]
Message-ID: <20220309095710.23849-1-ludo@gnu.org> (raw)
Hello Guix!
These patches color headings in the output of ‘show-what-to-build’:
The following derivations will be built:
is now printed in bold magenta, and:
X MB will be downloaded:
is printed in bold (this message is only visible at ‘-v2’.)
The reason it wasn’t done before is that it invalidates translations.
I think now is a good time as we prepare a release.
Julien, Maxim: WDYT?
Ludo’.
Ludovic Courtès (2):
ui: 'show-what-to-build' highlights "The following [...] will be
built".
ui: 'show-what-to-build' highlights "would be downloaded" headings.
guix/colors.scm | 4 +-
guix/ui.scm | 98 +++++++++++++++++++++++++++++--------------------
2 files changed, 61 insertions(+), 41 deletions(-)
base-commit: 0d14f8a8702ec8016ac58e5778a754b3105ef418
--
2.34.0
next reply other threads:[~2022-03-09 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 9:57 Ludovic Courtès [this message]
2022-03-09 10:12 ` [bug#54307] [PATCH 1/2] ui: 'show-what-to-build' highlights "The following [...] will be built" Ludovic Courtès
2022-03-09 10:12 ` [bug#54307] [PATCH 2/2] ui: 'show-what-to-build' highlights "would be downloaded" headings Ludovic Courtès
2022-03-09 10:52 ` [bug#54307] [PATCH 1/2] ui: 'show-what-to-build' highlights "The following [...] will be built" Liliana Marie Prikler
2022-03-10 10:19 ` [bug#54307] [PATCH 0/2] Highlight headings showing what to build/download Ludovic Courtès
2022-03-10 10:46 ` Liliana Marie Prikler
2022-03-13 22:00 ` Ludovic Courtès
2022-03-18 15:10 ` bug#54307: " 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=20220309095710.23849-1-ludo@gnu.org \
--to=ludo@gnu.org \
--cc=54307@debbugs.gnu.org \
--cc=julien@lepiller.eu \
--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 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.