unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Konstantin Kharlamov <Hi-Angel@yandex.ru>
Cc: 61413@debbugs.gnu.org
Subject: bug#61413: [PATCH] Make warnings show a "warning" emoji instead of a stop-sign
Date: Sat, 11 Feb 2023 12:36:13 +0200	[thread overview]
Message-ID: <83h6vsjxpe.fsf@gnu.org> (raw)
In-Reply-To: <20230211084559.516124-1-Hi-Angel@yandex.ru> (message from Konstantin Kharlamov on Sat, 11 Feb 2023 11:45:59 +0300)

merge 61413 60854
thanks

> From: Konstantin Kharlamov <Hi-Angel@yandex.ru>
> Date: Sat, 11 Feb 2023 11:45:59 +0300
> 
> Stop-sign emoji is confusing in context of warnings, because it
> typically has red color, and looks like there was some error. Let's use
> instead a "warning" emoji, which is typically shown in yellow color and
> doesn't look as if immediate attention is needed.

This is a duplicate of bug#60854: you are misinterpreting the purpose
of the Emoji here.





  parent reply	other threads:[~2023-02-11 10:36 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 ` Eli Zaretskii [this message]
2023-02-11 10:56   ` bug#60854: bug#61413: [PATCH] Make warnings show a "warning" emoji instead of a stop-sign Konstantin Kharlamov
2023-03-30 20:58     ` bug#60854: " Konstantin Kharlamov
2023-03-31  5:55       ` Eli Zaretskii
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=83h6vsjxpe.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=61413@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).