GNU bug report logs - #77917
31.0.50; [PATCH] Stop using the "stop" sign for all warning levels

Previous Next

Full log

Message #97 received at 77917 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Robert Pluim <rpluim <at> gmail.com>
Cc: yantar92 <at> posteo.net, 77917 <at> debbugs.gnu.org, prot <at> protesilaos.com,
 juri <at> linkov.net
Subject: Re: bug#77917: 31.0.50; [PATCH] Stop using the "stop" sign for all
 warning levels
Date: Tue, 06 May 2025 14:29:34 +0300

> From: Robert Pluim <rpluim <at> gmail.com>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,  Ihor Radchenko <yantar92 <at> posteo.net>,
>   77917 <at> debbugs.gnu.org,  prot <at> protesilaos.com
> Date: Tue, 06 May 2025 09:39:56 +0200
> 
> >>>>> On Mon, 05 May 2025 21:53:31 +0300, Juri Linkov <juri <at> linkov.net> said:
> 
>     >>> Then, what about
>     >>> 
>     >>> +                (insert (buttonize (concat (icon-string 'warnings-suppress) " [Suppress?]")
>     >>> +                                   #'warnings-suppress
>     >>> +                                   type
>     >>> +                                   "Click to suppress this warning type")
>     >> 
>     >> May I suggest to look at how other applications handle such
>     >> situations, i.e. when a message is shown and the user is given a
>     >> capability of disabling it?  Maybe that way we will find
>     >> implementation ideas that are both familiar to users and look nicer?
> 
>     Juri> Here is an interesting solution of using the context menu
>     Juri> to suppress warnings:
> 
>     Juri> https://stackoverflow.com/questions/32085708/suppress-warnings-in-visual-studio-2015-for-custom-code-analyzers
> 
> I conclude from that that we should use U+26A0 U+FE0F ⚠️ as the symbol
> to insert.

Really?  So we've just made another full circle back to the beginning?
Where someone said, and I agree, that showing ⚠️ explains itself worse
than the existing symbol, because it could be easily interpreted as
meaning just "Warning".

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.