From: Jim Porter <jporterbugs@gmail.com>
To: "Kévin Le Gouguec" <kevin.legouguec@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 17:37:15 -0800 [thread overview]
Message-ID: <346de561-ac0f-017b-832a-036ff3eadb99@gmail.com> (raw)
In-Reply-To: <874jsog5x0.fsf@gmail.com>
On 1/17/2023 2:19 PM, Kévin Le Gouguec wrote:
> Jim Porter <jporterbugs@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.
> 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.
Yup, the icon we have today is implemented via icons.el:
(define-icon warnings-suppress button
'((emoji "⛔")
(symbol " ■ ")
(text " stop "))
"Suppress warnings."
:version "29.1"
:help-echo "Click to suppress this warning type")
next prev parent reply other threads:[~2023-01-18 1:37 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
2023-01-18 1:37 ` Jim Porter [this message]
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=346de561-ac0f-017b-832a-036ff3eadb99@gmail.com \
--to=jporterbugs@gmail.com \
--cc=60854@debbugs.gnu.org \
--cc=kevin.legouguec@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).