From: Jim Porter <jporterbugs@gmail.com>
To: rms@gnu.org, Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: 60850@debbugs.gnu.org
Subject: bug#60850:
Date: Mon, 16 Jan 2023 21:44:38 -0800 [thread overview]
Message-ID: <7622a8e8-934b-0f7a-3363-b093582fcb26@gmail.com> (raw)
In-Reply-To: <E1pHe2m-0003eY-En@fencepost.gnu.org>
On 1/16/2023 8:57 PM, Richard Stallman wrote:
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> > > On 1/15/2023 10:29 PM, Pedro Andres Aranda Gutierrez wrote:
> > > > BTW: Isn't ⛔ a bit to "visually drastic" for a _warning_ ? Shouldn't it
> > > be
> > > > reserved for things like errors?
> > >
> > > Maybe worth filing a separate bug about this, but how about ⚠️ instead?
> > > Its official name is "Warning Sign", which seems appropriate.
>
> In what context are these characters used? I never see them in using
> Emacs -- which is a good thing, since the Linux console can't display
> them: they appear onit as one or three blue diamonds.
They appear in the *Warnings* buffer if some code calls
'display-warning'. You can see what it looks like on your system by
evaluating:
(display-warning 'some-type "a warning message")
The code to generate these icons is (well, should be) smart enough to
choose a fallback string instead of ⛔ if your Emacs session can't
display that character.
next prev parent reply other threads:[~2023-01-17 5:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 6:29 bug#60850: Pedro Andres Aranda Gutierrez
2023-01-16 6:50 ` bug#60850: Jim Porter
2023-01-16 7:35 ` bug#60850: Pedro Andres Aranda Gutierrez
2023-01-17 4:57 ` bug#60850: Richard Stallman
2023-01-17 5:44 ` Jim Porter [this message]
2023-01-20 4:00 ` bug#60850: Richard Stallman
2023-01-16 14:43 ` bug#60850: Eli Zaretskii
2023-09-05 23:35 ` bug#60850: Stefan Kangas
2023-09-06 6:57 ` bug#60850: Pedro Andres Aranda Gutierrez
2023-09-06 7:31 ` bug#60850: Stefan Kangas
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=7622a8e8-934b-0f7a-3363-b093582fcb26@gmail.com \
--to=jporterbugs@gmail.com \
--cc=60850@debbugs.gnu.org \
--cc=paaguti@gmail.com \
--cc=rms@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).