unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Konstantin Kharlamov <hi-angel@yandex.ru>
To: 60854@debbugs.gnu.org
Subject: bug#60854: [PATCH] Make warnings show a "warning" emoji instead of a stop-sign
Date: Thu, 30 Mar 2023 23:58:06 +0300	[thread overview]
Message-ID: <9f05f1a05b9d8f1a496aed84bf44b039ac7bb662.camel@yandex.ru> (raw)
In-Reply-To: <1214753ab8b9b72bb2dbbeb4113e67ab0b088167.camel@yandex.ru>

On Sat, 2023-02-11 at 13:56 +0300, Konstantin Kharlamov wrote:
> Jim Porter wrote:
> > On 1/17/2023 2:19 PM, Kévin Le Gouguec wrote:
> > > Jim Porter <jporterbugs <at> gmail.com> writes:
> > > > Perhaps a bit better would be 🚫, whose official name is apparently "No
> > > > Entry
> > > > Sign", even though the slashed circle visual usually just means "No
> > > > ____",
> > > > e.g. "No Smoking". Hence, some sources call it the Prohibited emoji.
> > > 
> > > (My ¢2: wouldn't a cross mark (❌) also work to convey the idea of
> > > "suppressing" something?)
> > 
> > That would work too. I still like turning this into a toggle button
> > where the icon shows the current state (i.e. is it an active warning -
> > ⚠️ - or has it been suppressed - ⚬). But changing to 🚫 or ❌ would be
> > single-character patches, which is nice too.
> 
> As a user, seeing any of ❌ or 🚫 in compilation buffer I think immediately of
> a
> problem because these emojis are shown in red color. You might say that color
> depends on a font, however they both are even documented on emojipedia to be
> "red", so rest assured, if there's a colorful emoji support on a user system,
> most likely the color will be red.
> 
> The fact it's actually a button that is supposed to do something is an
> interesting one, but since a button isn't actually used for displaying the
> button, it's kind of an easter egg. We know it's a button, but no one else
> will. (as a side note, I am also not sure why to make a button on every
> warning)
> 
> So please, let's either replace it with ⚠ as originally suggested, or make it
> an
> actual button with an actual text "suppress warnings". As it stands now, just
> replacing it with ❌ or 🚫 will not reduce any confusion.

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





  reply	other threads:[~2023-03-30 20:58 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     ` Konstantin Kharlamov [this message]
2023-03-31  5:55       ` bug#60854: " 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=9f05f1a05b9d8f1a496aed84bf44b039ac7bb662.camel@yandex.ru \
    --to=hi-angel@yandex.ru \
    --cc=60854@debbugs.gnu.org \
    /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).