unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 40990@debbugs.gnu.org
Subject: bug#40990: Improve message-mode and isearch icons
Date: Fri, 1 May 2020 18:21:32 +0300	[thread overview]
Message-ID: <e3d0bb0f-87e7-29c2-ff3a-325a9c3a635b@yandex.ru> (raw)
In-Reply-To: <83ees4w562.fsf@gnu.org>

On 01.05.2020 09:16, Eli Zaretskii wrote:
> Thanks, but I see nothing in these arguments to say that it's urgent
> or even very important to have these UI changes in Emacs 27.

It's steps like this that address the perceived lack of polish that 
users see when starting to use Emacs. So I'm fairly sure it's important. 
Just not critical, of course.

And my arguments are, as usual, about the added value vs risk. Which I'm 
fairly sure is minimal.

> Please help me release Emacs 27.1 as soon as possible by trying to
> look at this stuff from my POV.

...I do? (*) Just with somewhat different approach, e.g. preponderance 
of evidence rather than presumption of unimportance. :-)

Anyway, such discussions should become rare if we somehow manage to 
speed up the release cycle someday.

(*) For instance, I chose the proposed changes critically, leaving out 
certain others that would add more risk.





  reply	other threads:[~2020-05-01 15:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 23:50 bug#40990: Improve message-mode and isearch icons Dmitry Gutov
2020-05-01  6:16 ` Eli Zaretskii
2020-05-01 15:21   ` Dmitry Gutov [this message]
2020-05-01 15:43     ` Eli Zaretskii
2020-05-01 15:49       ` Eli Zaretskii
2020-05-01 22:12       ` Dmitry Gutov
2020-05-02  6:23         ` Eli Zaretskii
2020-05-11  1:42           ` Dmitry Gutov
2020-05-11  2:35             ` Eli Zaretskii
2020-05-11  2:46               ` Dmitry Gutov
2020-05-11  4:17                 ` Eli Zaretskii
2020-05-11 14:18                   ` Dmitry Gutov
2020-05-11 15:53                     ` Eli Zaretskii

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=e3d0bb0f-87e7-29c2-ff3a-325a9c3a635b@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=40990@debbugs.gnu.org \
    --cc=eliz@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).