Em sexta, 03/05/2024 às 19:50 (GMT), Philip Kaludercic <philipk@posteo.net> escreveu:

> I think one would have to study `elisp-flymake-byte-compile' and related
> functions in greater detail to understand that

I've skimmed through it a couple of times, but the byte compilation is
still bit cryptic in what it does.

> Will do, but as I said I first have to fine the time and motivation to
> work on this in the first place.  It is not really a pressing issue, and
> I have to admit that my enthusiasm wrt. setup.el is not really at an
> all-time-high (though I still prefer it to use-package).

That's fine, it really is just annoying warnings TBH. I've picked up

> No problem, I'm always happy to receive emails like these, because then
> at least I know that someone is using setup.el ^^

I've been meaning to try setup.el for a long time now. Most of the local
macros I defined for setup.el were macros I already had on my config. I
tried use-package for a while but it felt too magic, so I just came up
with my own wrapper to `with-eval-after-load' and a function to install
a package if it isn't installed and went from there. Couple years pass
and I start to realize I have created a bunch of other macros here and
there to do other things, but they were all over the place. That's where
setup.el comes in! It allows me put all of my configuration for a single
library in the same place, with some neat macros to make things cleaner!
I guess it might not be everyone's cup of tea, but it fit like a glove

Em sábado, 27/04/2024 às 06:35 (GMT), Philip Kaludercic <philipk@posteo.net> escreveu:

> My apologies, I had convinced myself that I had already responded to
> your message, but it appears all I did was prepare a message in my mind.
> Thank you for the reminder, my backlog is currently horrible :/

No worries! Thanks for taking the time to reply.

> So the (format "%s" package) above is just a placeholder?

Yeah, sorry about that. It should've been `(:package ,package) instead.

> That's `ensure-list' (Emacs 28.1+) btw.

Hi Philip,

As you suggested in your personal blog[0], I'm pinging you with regards
to this after a week :D

[0] https://amodernist.com/#email

Cheers,

Em quinta, 18/04/2024 às 20:17 (-03), João Pedro <jpedrodeamorim@gmail.com> escreveu:

> Greetings,
>
> I'm trying to define a local macro to only install packages after some

I'm forwarding the following message because I believe it wasn't
delivered (I've been having issues with emails appearing as sent but not
being delivered).

-------------------- Start of forwarded message --------------------
From: João Pedro <jpedrodeamorim@gmail.com>
To: ~pkal/public-inbox@lists.sr.ht
Subject: setup.el: :repeatable doesn't respect list arguments
Date: Thu, 18 Apr 2024 20:09:14 -0300

Greetings,

I'm trying to define a local macro to only install packages after some
features have been loaded, here's the code for it:

Em quinta, 08/02/2024 às 11:27 (+02), Protesilaos Stavrou <info@protesilaos.com> escreveu:

> It is on purpose because the mode does have those warnings. I don't know
> if they are needed, but I guess someone has a use for them. Do you think
> they should be different?

It might be personal preference, but I'd rather face whitespace
indication as just that, an indication that there is whitespace there,
instead of it being a 'warning'. But that's just me, it indeed does seem
like whitespace-mode tends to treat them as warnings by default. The
semantic highlights seem to have solved it, I just added

    ;; whitespace
    (bg-space bg-dim)

Em quinta, 08/02/2024 às 11:25 (+02), Protesilaos Stavrou <info@protesilaos.com> escreveu:

> Oh, I see. I think the easier way for this is for me to add a semantic
> palette override to that effect.
>
> Until then, try this:
>
>     (defun my-modus-themes-faces ()
>       (modus-themes-with-colors
>         (custom-set-faces
>          '(org-block-begin-line ((,c :background ,bg-dim))))))
>
>     (add-hook 'modus-themes-post-load-hook #'my-modus-themes-faces)
>

Em quinta, 08/02/2024 às 11:21 (+02), Protesilaos Stavrou <info@protesilaos.com> escreveu:

> Sorry for the late reply. I am slow to respond due to my limited typing
> time (I have pain in my left arm).

I should be the one apologising this time. A day before you replied I
had a surgery and haven't touched a computer while recovering. I'm all
recovered now!

> Note that some faces inherit from 'fixed-pitch' only if the user option
> 'modus-themes-fixed-pitch' is enabled. Otherwise they do not inherit
> anything.

This option doesn't seem to apply anymore, can I ask you what changed?

Em quarta, 04/01/2023 às 18:56, Protesilaos Stavrou <info@protesilaos.com> escreveu:

> Personally I am fine.  We'll see how the rest goes.  I hope you are
> doing well.

Seems like it is a end/start-of-the-year tradition for me to mail you
regarding some faces in Modus Themes! :P

I'm so incredibly sorry I had not replied to you on this, I completely
forgot about it and might've hit my shortcut to tag it as read without
actually reading it thoroughly...

> -    `(whitespace-line ((,c :inherit modus-themes-subtle-yellow)))
> +    `(whitespace-line ((,c :background ,bg-yellow-subtle)))

Em segunda, 25/12/2023 às 22:21, João Pedro <jpedrodeamorim@gmail.com> escreveu:

> The situation I came upon was that, when using `org-modern' I noticed
> that the height set in `org-modern-block-name' wasn't respected, and it
> turns out it was due to the fact that `org-block-begin-line' inherits
> from `modus-themes-fixed-pitch', which has a set height. If I execute
>
>     (set-face-attribute 'org-block-begin-line nil :inherit nil)
>
> I get the correct fontification of the height, but this seems to be far
> from ideal since other attributes should be inherited from the fixed
> pitch face.

It might also be helpful to explain what I'm trying to achieve in the