bug#40990: closed (Improve message-mode and isearch icons)

[GNU bug Tracking System]

Your message dated Mon, 11 May 2020 04:42:32 +0300
with message-id <address@hidden>
and subject line Re: bug#40990: Improve message-mode and isearch icons
has caused the debbugs.gnu.org bug report #40990,
regarding Improve message-mode and isearch icons
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
40990: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=40990
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: Improve message-mode and isearch icons Date: Fri, 1 May 2020 02:50:04 +0300 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0

As discussed previously in the "Why is emacs so square?" thread, here's
a couple of patches that improve the toolbar icons in GTK builds.

Attached are several screenshots from my machine: isearch toolbar with
the x-gtk-stock-map patch and without (the difference is one icon), and
message-mode toolbar without the patch, with the patch, and also with
the extra patch that makes message-tool-bar-retro use the standrd
"mail/send" icon instead of the Gnus-specific one. Fixing Emacs not to
use message-tool-bar-retro is left as a future exercise.

I'd like to present a few arguments for the inclusion of the
x-gtk-stock-map patch in Emacs 27 (on which the current answer is no,
but I'll try to elaborate):

1. With it, the answer to the question "why does everybody tell the new
users to turn off toolbars" becomes less obvious, at least in GTK based
environments.

2. This only affects GTK. And also, if a theme doesn't contain the "new"
replacement image, the previous one will be shown instead.

3. Since "everybody" turns off the toolbars now, the risk of complaints
is pretty low. By the same token, we could de-prioritize said complaints
even if they appear, given that for most people the improvement is most
likely obvious (feedback welcome).

The second patch is a tiny bit more risky, but honestly, since it uses
an icon apparently borrowed from some old GTK-related icon set, using a
new version of the same icon shouldn't bother most people. But this
patch *can* affect users on different toolkits and different platforms
(again, feedback welcome).

message-tool-bar-retro.diff
Description: Text Data

x-gtk-stock-map.diff
Description: Text Data

isearch-icons-new.png
Description: PNG image

isearch-icons-old.png
Description: PNG image

message-mode-icons-new.png
Description: PNG image

message-mode-icons-new-with-extra-patch.png
Description: PNG image

message-mode-icons-old.png
Description: PNG image

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#40990: Improve message-mode and isearch icons
>
>
>
>
> Date: 
>
> Mon, 11 May 2020 04:42:32 +0300
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0
>
>
>
>
> Now fixed on master. Closing.
>
> On 02.05.2020 09:23, Eli Zaretskii wrote:
>
> > > Anyway, for all I know, we could release 27 tomorrow. As soon as we deal
> > > with the "modify literal objects" documentation discussion.
> >
> > There's always "that one last" issue to be fixed.
> >
> > The only way to speed up our releases that I see is to care less about
> > stability and regressions.  If you are following the bug list closely,
> > you will see that we just recently started to get reports about
> > significant regressions in Emacs 27 (and some in Emacs 26).  Should we
> > disregard them?  We never did that, not since Emacs 25, at least.
>
> I don't know what's the best course of action in each case, but if we 
> did make a point of releasing more often (e.g. did time-based releases, 
> for instance), Emacs 27.1 would probably have been less stable. But it 
> would have been released maybe a year ago, and by now we'd already have 
> released, say, 27.2 and 27.3, with more regressions fixed and faster 
> because of exposure to a wider audience, more testing.
>
> It's a tricky road, but a possible one.
>
>
> --- End Message ---