From: "Ludovic Courtès" <ludo@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Cc: 54307@debbugs.gnu.org
Subject: [bug#54307] [PATCH 0/2] Highlight headings showing what to build/download
Date: Thu, 10 Mar 2022 11:19:10 +0100 [thread overview]
Message-ID: <87mthyyush.fsf_-_@gnu.org> (raw)
In-Reply-To: <14d71f279ec542fb8fb5557934b6d6ae7f7792b3.camel@ist.tugraz.at> (Liliana Marie Prikler's message of "Wed, 09 Mar 2022 11:52:48 +0100")
Hi,
Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> skribis:
> Am Mittwoch, dem 09.03.2022 um 11:12 +0100 schrieb Ludovic Courtès:
>> * guix/colors.scm (highlight/warn): New procedure.
>> * guix/ui.scm (show-what-to-build): Use 'highlight/warn' when
>> displaying
>> what would/will be built.
> highlight/warn sounds somewhat misleading for this use-case. Should
> this be highlight/info instead?
I agree “warn” is misleading, but I don’t find “info” any clearer. :-)
Maybe ‘highlight-more’ or something?
Ludo’.
next prev parent reply other threads:[~2022-03-10 10:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 9:57 [bug#54307] [PATCH 0/2] Highlight headings showing what to build/download Ludovic Courtès
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 ` Ludovic Courtès [this message]
2022-03-10 10:46 ` [bug#54307] [PATCH 0/2] Highlight headings showing what to build/download 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=87mthyyush.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=54307@debbugs.gnu.org \
--cc=liliana.prikler@ist.tugraz.at \
/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.