| Age | Commit message (Collapse) | Author |
|---|
|
As I announced here: <https://protesilaos.com/news/2026-04-21-omitting-the-surname/>.
|
|
I thought this was not needed, but Ihor Radchenko showed me a useful
example. This was done in issue 207: <https://github.com/protesilaos/modus-themes/issues/207>.
|
|
This is now introduced in the modus-themes.git. Thanks to aikrahguzar
for suggesting this in issue 70: <https://github.com/protesilaos/ef-themes/issues/70>.
|
|
I tried to do this with a recent commit but that broke things because
I also included a deftheme declaration. Having that meant that
modus-themes-theme would not declare the theme with all its data,
including its palette.
I looked at loaddefs-generate--emacs-batch and it seems that having
just the theme-autoload line is enough.
|
|
This reverts commit a4b5f9353063ef895f6c13c8cd594bfd5df455ca.
The reason is that this breaks the package when trying to load a theme
at startup. This was reported by Eamonn Sullivan in issue 69 in the
ef-themes repository: <https://github.com/protesilaos/ef-themes/issues/69>.
|
|
We need this because otherwise the autolaods are not generated
properly, which can cause problems for other packages that need to
read the theme data.
|
|
It was too subtle.
|
|
It is not needed. I had it there because some colour no longer had the
same mappings after refactoring the themes to be built on top of
Modus. But I am in the process of reviewing those colours now.
|
|
|
|
I did the changes with keyboard macros as usual. I now notice that
some themes have 26 changes while others have 28. This should probably
be due to some older inconsequential irregularities. I loaded each
theme right now and they all seem okay, so I will let this pass. If
anybody reports a bug, I am always happy to fix it.
At any rate, the main point for this change is to (i) ensure that we
get a complete palette while (ii) that we register the theme's palette
as a "core palette" because these are the correct semantics (e.g. that
ef-light ultimately may have inherited something from modus-operandi
is not relevant to the question "what is your core theme?").
|
|
|
|
ef-kassio also had a different notice about whether this file is part
of Emacs. I remember reading before that GNU ELPA packages are part of
Emacs, though I prefer to have that notice only if they are part of
emacs.git.
|
|
Those are used by tree-sitter and related faces.
|
|
|
|
This is supported in the latest version of the modus-themes.
|
|
|
|
|
|
|
|
|
|
I still need to re-implement the relevant commands to switch themes,
but this is already an important step forward.
|
|
The goal is two-fold:
1. Improve the semantics of relevant faces. This now covers the Org
agenda. We want pending/urgent tasks to be rendered in a bold font
and use a vivid colour. Whereas tasks that are not urgent should
have a subtle colour and a normal weight. Thanks to Adam
Porter (GitHub @alphapapa) for discussing this with me in issue
102 on the Modus themes repository (the same principles apply
here): <https://github.com/protesilaos/modus-themes/issues/102>.
2. Make the applicable colours be more consistent with the rest of the
theme. In practice, this means that the colour values are cooler
overall and the intensity is lower.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
