unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: "Jim Porter" <jporterbugs@gmail.com>,
	"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: Wed, 18 Jan 2023 11:30:38 +0100	[thread overview]
Message-ID: <87a62gb0dt.fsf@gmail.com> (raw)
In-Reply-To: <877cxkqqs8.fsf@gmail.com> ("Kévin Le Gouguec"'s message of "Wed, 18 Jan 2023 07:51:19 +0100")

>>>>> On Wed, 18 Jan 2023 07:51:19 +0100, Kévin Le Gouguec <kevin.legouguec@gmail.com> said:

    Kévin> Jim Porter <jporterbugs@gmail.com> writes:
    >> 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.

    Kévin> Sure, the toggle sounds like a nice idea regardless, since IIUC right
    Kévin> now a user has to go through Customize to take warnings off either
    Kévin> warning-suppress-*types.

    Kévin> (Sorry for the idle musing, this is the first time I look at what knobs
    Kévin>  warnings.el lets the user tweak.

    Kévin>  As things stand, if a user doesn't want to completely ignore a warning,
    Kévin>  their only choices seem to be "pop *Warnings*" or "meh, tuck it in
    Kévin>  *Warnings* but don't pop; hopefully I'll remember to check that buffer
    Kévin>  someday", is that correct?

Yes

    Kévin>  Might be nice to have further options for "suppression", e.g.…

    Kévin>  "don't pop the *Warnings* buffer, but display in echo area", or
    Kévin>                                "…  but add a modeline indicator"

    Kévin>  … but that's its own feature request)

Sure. Just donʼt turn that on by default :-)

    >>> 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")

    Kévin> (Ah, great, so we're only missing an 'image entry for that one.  Just a
    Kévin> trivial matter of choosing what the image should look like then 😁)

Whilst youʼre changing stuff, the text should not be "stop", it should
be "suppress" or "ignore" or something.

Robert
-- 





  reply	other threads:[~2023-01-18 10:30 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
2023-01-18  6:51         ` Kévin Le Gouguec
2023-01-18 10:30           ` Robert Pluim [this message]
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=87a62gb0dt.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=60854@debbugs.gnu.org \
    --cc=jporterbugs@gmail.com \
    --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).