unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>, aaaa <livi@cock.li>, emacs-devel@gnu.org
Subject: Re: Proposal for a new emacs icon
Date: Sun, 5 May 2024 06:44:43 +0300	[thread overview]
Message-ID: <050de6f3-090c-4c6c-b846-a9c82908eacd@gutov.dev> (raw)
In-Reply-To: <87cyq3b1j3.fsf@yahoo.com>

On 03/05/2024 14:03, Po Lu wrote:
> Dmitry Gutov<dmitry@gutov.dev>  writes:
> 
>> I'll have to revisit the branch, but an icon set that is off by
>> default is about just as useful for improving the default look of the
>> editor as the ability to toggle the tool-bar off. Which is to say,
>> very little improvement over the status quo.
> Useful or not, it's what we decided, and there are yet no reasons to
> reconsider this decision.
> 
>> I'm sorry about downplaying the amount of effort that went into this,
>> though. Let me take a second look at the proposed set this
>> evening. Too bad we don't have a page with an overview - or it's lost
>> in some older thread.
> If it helps, most of the discussion took place in August 2022.

Thanks.

Here's a message with a comparison from back then for those that forgot: 
https://lists.gnu.org/archive/html/emacs-devel/2022-08/msg01085.html



  reply	other threads:[~2024-05-05  3:44 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30 23:07 Proposal for a new emacs icon Elijah G
2024-05-01  1:02 ` Po Lu
2024-05-01  7:03 ` Michael Albinus
2024-05-01 12:16   ` Eli Zaretskii
2024-05-01 14:40     ` [External] : " Drew Adams
2024-05-01 23:21       ` Jose E. Marchesi
2024-05-02 16:54         ` David Koppelman
2024-05-01 13:14   ` Visuwesh
2024-05-01 23:21   ` Elijah G
2024-05-01 23:55     ` Arsen Arsenović
2024-05-02  2:50       ` Werner LEMBERG
2024-05-02  0:52     ` Po Lu
2024-05-02  1:52       ` Elijah G
2024-05-02  3:02         ` Po Lu
2024-05-02  6:53         ` Eli Zaretskii
2024-05-02  7:26       ` Arash Esbati
2024-05-02  7:49         ` Po Lu
2024-05-02  8:02           ` Arash Esbati
2024-05-02  9:45             ` Po Lu
2024-05-02 10:00               ` Arash Esbati
2024-05-02  7:24     ` Ulrich Mueller
2024-05-02 19:26       ` Elijah G
2024-05-01 14:53 ` aaaa
2024-05-01 15:58 ` Ulrich Mueller
2024-05-01 18:14 ` Dmitry Gutov
2024-05-01 20:26   ` aaaa
2024-05-02  6:59     ` Eli Zaretskii
2024-05-02  9:57       ` Dmitry Gutov
2024-05-02 12:03         ` Po Lu
2024-05-02 12:08           ` Po Lu
2024-05-03 10:47           ` Dmitry Gutov
2024-05-03 11:03             ` Po Lu
2024-05-05  3:44               ` Dmitry Gutov [this message]
2024-05-02  8:05 ` Philip Kaludercic
2024-05-02  9:52   ` Po Lu
2024-05-02 17:01     ` Philip Kaludercic
2024-05-02  8:54 ` Tino Calancha

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=050de6f3-090c-4c6c-b846-a9c82908eacd@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=livi@cock.li \
    --cc=luangruo@yahoo.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).