From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Jim Porter <jporterbugs@gmail.com>
Cc: "Pedro Andres Aranda Gutierrez" <paaguti@gmail.com>,
60854@debbugs.gnu.org, "Daniel Martín" <mardani29@yahoo.es>
Subject: bug#60854: Adjust icons shown with warnings
Date: Tue, 17 Jan 2023 23:19:55 +0100 [thread overview]
Message-ID: <874jsog5x0.fsf@gmail.com> (raw)
In-Reply-To: <fb1a9b33-1a24-24aa-1a23-21667b49de5c@gmail.com> (Jim Porter's message of "Mon, 16 Jan 2023 11:30:10 -0800")
(Passing by, can't remember the whole thread, sorry if what I'm
suggesting has already be said)
Jim Porter <jporterbugs@gmail.com> writes:
> On 1/16/2023 1:58 AM, Daniel Martín via Bug reports for GNU Emacs, the Swiss
> army knife of text editors wrote:
>> Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:
>>
>>> Currently, warnings are visually "enhanced" with a ⛔ sign.
>>> However, the warning signs are ⚠️ or its slightly different European
>>> version.
>> I had the same question as you, but it turns out that the ⛔ icon is not
>> intended to represent a warning, it is a button that you can click to
>> *suppress* that warning type.
>
> I think the confusion is that the literal meaning of the ⛔ icon is "No Entry",
> so it's very easy to read it as, "Stop! Don't go this way because there's a
> problem ahead."
>
> 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?)
> We could also add actual images for this icon if none of these are quite right,
> and use the emoji as a fallback.
The new icons.el that comes with Emacs 29 would be a prime candidate for
implementing this, right? It has the advantage of giving the user some
degree of control via icon-preference.
next prev parent reply other threads:[~2023-01-17 22:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 7:35 bug#60854: Adjust icons shown with warnings Pedro Andres Aranda Gutierrez
2023-01-16 9:58 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-16 12:22 ` Pedro Andres Aranda Gutierrez
2023-01-16 19:30 ` Jim Porter
2023-01-17 22:19 ` Kévin Le Gouguec [this message]
2023-01-18 1:37 ` Jim Porter
2023-01-18 6:51 ` Kévin Le Gouguec
2023-01-18 10:30 ` Robert Pluim
2023-01-22 21:36 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-17 9:56 ` Pedro Andres Aranda Gutierrez
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=874jsog5x0.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=60854@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
--cc=mardani29@yahoo.es \
--cc=paaguti@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 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).