From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: visuweshm@gmail.com, dgutov@yandex.ru, angelo.g0@libero.it,
emacs-devel@gnu.org
Subject: Re: Adding icon sets to Emacs -- and next steps for icons.el
Date: Wed, 24 Aug 2022 19:34:59 +0300 [thread overview]
Message-ID: <8335dl61n0.fsf@gnu.org> (raw)
In-Reply-To: <jwvbks9pq4w.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 24 Aug 2022 12:23:42 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Visuwesh <visuweshm@gmail.com>, dgutov@yandex.ru, angelo.g0@libero.it,
> emacs-devel@gnu.org
> Date: Wed, 24 Aug 2022 12:23:42 -0400
>
> >> I think the current trend is in the opposite direction? Everywhere I
> >> go, it is monochrome icons, or the same colour scheme for all the icons
> >> making them indistinguishable (looking at you Google).
> >
> > Some progress... What next? back to 640KB memory?
>
> No, the end result may look like what we had back then, but the resource
> consumption never goes back.
There are always overlays (in program memory, I mean, not display
overlays we use in Emacs). Lots of fun!
next prev parent reply other threads:[~2022-08-24 16:34 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 12:43 Adding icon sets to Emacs -- and next steps for icons.el Angelo Graziosi
2022-08-24 13:05 ` Dmitry Gutov
2022-08-24 13:22 ` Eli Zaretskii
2022-08-24 13:26 ` Visuwesh
2022-08-24 14:19 ` Eli Zaretskii
2022-08-24 14:32 ` Visuwesh
2022-08-24 16:23 ` Stefan Monnier
2022-08-24 16:34 ` Eli Zaretskii [this message]
2022-08-25 1:11 ` Po Lu
2022-08-25 1:35 ` Visuwesh
2022-08-24 13:36 ` Po Lu
2022-08-24 13:51 ` Angelo Graziosi
2022-08-24 16:40 ` Stefan Kangas
2022-08-24 13:46 ` Angelo Graziosi
2022-08-24 13:47 ` Dmitry Gutov
2022-08-24 13:58 ` Po Lu
2022-08-24 14:26 ` Dmitry Gutov
2022-08-25 1:10 ` Po Lu
2022-08-25 1:22 ` Dmitry Gutov
2022-08-25 2:34 ` Po Lu
2022-08-24 23:09 ` Stefan Kangas
2022-08-25 1:23 ` Po Lu
2022-08-25 5:39 ` Eli Zaretskii
2022-08-25 6:49 ` Po Lu
2022-08-25 11:01 ` Visuwesh
2022-09-07 20:03 ` Jean Louis
2022-09-08 8:18 ` Po Lu
2022-09-08 8:25 ` Dmitry Gutov
2022-09-08 8:37 ` Jean Louis
2022-09-08 10:38 ` Po Lu
2022-08-25 21:26 ` Rudolf Adamkovič
2022-09-08 11:00 ` Jean Louis
2022-09-09 11:04 ` Rudolf Adamkovič
2022-09-07 19:18 ` references for usability - " Jean Louis
2022-08-25 9:28 ` Lars Ingebrigtsen
2022-09-07 19:11 ` Jean Louis
-- strict thread matches above, loose matches on Subject: below --
2022-09-08 12:19 Payas Relekar
2022-09-08 14:03 ` Po Lu
2022-09-08 14:11 ` Payas Relekar
2022-09-08 21:24 ` Stefan Kangas
2022-09-09 1:48 ` Po Lu
2022-09-08 10:03 Payas Relekar
2022-09-08 11:44 ` Dmitry Gutov
2022-09-09 3:03 ` Richard Stallman
2022-08-24 16:08 Payas Relekar
2022-08-24 18:10 ` Dmitry Gutov
2022-08-25 1:39 ` Visuwesh
2022-08-25 5:28 ` Tim Cross
2022-08-24 6:45 Stefan Kangas
2022-08-24 6:56 ` Po Lu
2022-08-24 7:20 ` Stefan Kangas
2022-08-24 11:25 ` Lars Ingebrigtsen
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=8335dl61n0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=angelo.g0@libero.it \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=visuweshm@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).