From: Eli Zaretskii <eliz@gnu.org>
To: Konstantin Kharlamov <hi-angel@yandex.ru>
Cc: 60854@debbugs.gnu.org
Subject: bug#60854: [PATCH] Make warnings show a "warning" emoji instead of a stop-sign
Date: Fri, 31 Mar 2023 08:55:47 +0300 [thread overview]
Message-ID: <83355l4g7w.fsf@gnu.org> (raw)
In-Reply-To: <9f05f1a05b9d8f1a496aed84bf44b039ac7bb662.camel@yandex.ru> (message from Konstantin Kharlamov on Thu, 30 Mar 2023 23:58:06 +0300)
> From: Konstantin Kharlamov <hi-angel@yandex.ru>
> Date: Thu, 30 Mar 2023 23:58:06 +0300
>
> Given release is pretty close, how about at least replacing the emoji to radio
> button? 🔘 This way it would be clearly a button, and also wouldn't have any
> reds in it
Who says this character is widespread enough for us to use it?
Anyway, I see no reason to rush with this. The current situation is
not really that bad, considering that these messages should not be
shown too frequently. Feel free to suggest customizable changes for
master, and let's see where that leads us. (IME, these fancy
characters are still not supported widely enough, but that's me.)
next prev parent reply other threads:[~2023-03-31 5:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 8:45 bug#61413: [PATCH] Make warnings show a "warning" emoji instead of a stop-sign Konstantin Kharlamov
[not found] ` <handler.61413.B.16761051946467.ack@debbugs.gnu.org>
2023-02-11 8:49 ` bug#61413: Acknowledgement ([PATCH] Make warnings show a "warning" emoji instead of a stop-sign) Konstantin Kharlamov
2023-02-11 10:36 ` bug#61413: [PATCH] Make warnings show a "warning" emoji instead of a stop-sign Eli Zaretskii
2023-02-11 10:56 ` bug#60854: " Konstantin Kharlamov
2023-03-30 20:58 ` bug#60854: " Konstantin Kharlamov
2023-03-31 5:55 ` Eli Zaretskii [this message]
2023-03-31 6:19 ` Konstantin Kharlamov
2023-03-31 6:26 ` Konstantin Kharlamov
2023-03-31 7:05 ` Eli Zaretskii
2023-03-31 7:48 ` Konstantin Kharlamov
2023-03-31 7:54 ` Eli Zaretskii
2023-03-31 8:10 ` Konstantin Kharlamov
2023-03-31 7:00 ` Eli Zaretskii
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83355l4g7w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60854@debbugs.gnu.org \
--cc=hi-angel@yandex.ru \
/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/emacs.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).