From: Tim Cross <theophilusx@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Gerry Agbobada <emacs-devel@gagbo.net>,
"Gregory Heytings via Emacs development discussions."
<emacs-devel@gnu.org>
Subject: Re: Theme generator (was: solarized)
Date: Wed, 16 Sep 2020 11:49:04 +1000 [thread overview]
Message-ID: <CAC=50j9U5zaw-Ya+rZNanvZGrc8P_21V71KOfMQ6nr-JcsRyKA@mail.gmail.com> (raw)
In-Reply-To: <jwvwo0vw1h8.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1971 bytes --]
I think this is a better approach than trying to come up with a definitive
set of themes. The 'look' of your editor is a pretty personal preference
and we are unlikely to find a definitive set of themes that will suit all.
On the other hand, if we can make it easier to define a theme, we are
enabling people to make it look the way they want, which seems to be part
of the core essence of Emacs - do it your way.
At present, while you have all the power to customize faces, it isn't
necessary easy to get things consistent. Defining a new theme usually takes
a lot of trial and error. It has certainly improved since I first started
with Emacs in the 90s, but could probably be improved further with a theme
generator. The big challenge is that Emacs has far more 'faces' than other
editors and it sin't always clear how all these faces interact. Some sort
of theme generator which could help with this would make it easier for
people to define their own themes.
The spacemacs setup also has a pretty straight-forward way to tweak
existing themes with their theming-modifications list, which makes it easy
to tweak specific settings for specific themes (and ensures they are
applied when themes change or are re-loaded etc).
On Wed, 16 Sep 2020 at 00:43, Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
> > Henrik tried to do it with emacs-doom-themes
> > ( https://github.com/hlissner/emacs-doom-themes ) but apparently the
> theme
> > generation part is not really good and he has been trying to find time to
> > rewrite that part. But using that API to define a theme seems really
> easy :
> >
> https://github.com/hlissner/emacs-doom-themes/blob/master/themes/doom-one-theme.el
> >
> > I think this is the kind of helpers that would warrant upstream
> integration :
>
> Indeed, it seems that if we extended the `defface` machinery to allow
> evaluation of Elisp code, we could make this "standard".
>
>
> Stefan
>
>
>
--
regards,
Tim
--
Tim Cross
[-- Attachment #2: Type: text/html, Size: 2832 bytes --]
next prev parent reply other threads:[~2020-09-16 1:49 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 3:48 solarized Richard Stallman
2020-09-15 8:29 ` solarized Protesilaos Stavrou
2020-09-15 9:14 ` solarized Yuri Khan
2020-09-15 10:16 ` solarized Protesilaos Stavrou
2020-09-15 13:39 ` solarized Theodor Thornhill
2020-09-15 14:05 ` solarized Gerry Agbobada
2020-09-15 14:40 ` Theme generator (was: solarized) Stefan Monnier
2020-09-15 16:26 ` Theme generator Arthur Miller
2020-09-15 20:14 ` Stefan Monnier
2020-09-15 20:35 ` Stefan Monnier
2020-09-15 20:44 ` Arthur Miller
2020-09-16 1:49 ` Tim Cross [this message]
2020-09-17 0:25 ` Theme generator (was: solarized) chad
2020-09-17 14:25 ` Theme generator Arthur Miller
2020-09-16 5:03 ` Theme generator (was: solarized) Richard Stallman
2020-09-15 20:28 ` solarized Protesilaos Stavrou
2020-09-15 20:50 ` solarized Praharsh Suryadevara
2020-09-16 5:05 ` solarized Richard Stallman
2020-09-16 8:27 ` solarized Protesilaos Stavrou
2020-09-16 13:38 ` solarized Arthur Miller
2020-09-17 3:57 ` solarized Richard Stallman
2020-09-17 7:53 ` solarized Gian Uberto Lauri
2020-09-17 15:56 ` solarized Drew Adams
2020-09-18 4:08 ` solarized Richard Stallman
2020-09-18 4:08 ` solarized Richard Stallman
2020-09-18 16:44 ` solarized Drew Adams
2020-09-17 14:11 ` solarized Arthur Miller
2020-09-17 23:39 ` solarized Tim Cross
2020-09-18 4:13 ` solarized Richard Stallman
2020-09-18 5:49 ` solarized Tim Cross
2020-09-18 6:43 ` solarized Arthur Miller
2020-09-16 13:06 ` solarized Arthur Miller
2020-09-17 3:53 ` solarized Richard Stallman
2020-09-15 11:26 ` solarized Göktuğ Kayaalp
2020-09-15 12:15 ` solarized Elias Mårtenson
2020-09-15 12:56 ` solarized Göktuğ Kayaalp
2020-09-16 1:30 ` solarized Tim Cross
2020-09-16 10:21 ` solarized Göktuğ Kayaalp
2020-09-16 12:53 ` solarized Arthur Miller
2020-09-16 22:09 ` solarized Tim Cross
2020-09-17 14:29 ` solarized Arthur Miller
2020-09-18 13:32 ` solarized Stefan Kangas
2020-09-18 15:53 ` solarized Arthur Miller
2020-09-18 16:03 ` solarized Arthur Miller
2020-09-19 4:00 ` solarized Richard Stallman
2020-09-20 20:18 ` solarized Bozhidar Batsov
2020-09-15 12:05 ` WCAG AAA and Emacs themes Dmitry Gutov
2020-09-15 20:22 ` Protesilaos Stavrou
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='CAC=50j9U5zaw-Ya+rZNanvZGrc8P_21V71KOfMQ6nr-JcsRyKA@mail.gmail.com' \
--to=theophilusx@gmail.com \
--cc=emacs-devel@gagbo.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).