From: Protesilaos Stavrou <info@protesilaos.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, larsi@gnus.org, 55414@debbugs.gnu.org
Subject: bug#55414: 29.0.50; Byte compilation error for the modus-themes
Date: Tue, 24 May 2022 07:37:02 +0300 [thread overview]
Message-ID: <87v8tv7dht.fsf@protesilaos.com> (raw)
In-Reply-To: <83czg47bz7.fsf@gnu.org>
> From: Eli Zaretskii <eliz@gnu.org>
> Date: Mon, 23 May 2022 13:57:32 +0300
>
>> From: Protesilaos Stavrou <info@protesilaos.com>
>> Cc: larsi@gnus.org, 55414@debbugs.gnu.org
>> Date: Mon, 23 May 2022 06:51:10 +0300
>>
>> > Do we know what value is necessary for modus-themes to successfully
>> > byte-compile? If so, let's increase the value separately for each
>> > case: byte compilation and native-compilation.
>>
>> Then I should add local variables? I am fine with this. Just need to
>> have your verdict on the matter.
>
> No, I assumed that we could increase the global values separately for
> each case.
>
> But if you can use local values, that'd be fine with me.
I tried setting local values, both by writing them to the files and
adding them to .dir-locals.el, but they are ignored. They are also
ignored when I visit the files, as I keep getting a warning about risky
local variables even after adding those to safe-local-variable-values
and ensuring that ignored-local-variable-values is nil.
--
Protesilaos Stavrou
https://protesilaos.com
next prev parent reply other threads:[~2022-05-24 4:37 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 18:07 bug#55414: 29.0.50; Byte compilation error for the modus-themes Protesilaos Stavrou
2022-05-15 13:45 ` Lars Ingebrigtsen
[not found] ` <87lev296hl.fsf@protesilaos.com>
2022-05-15 15:16 ` Lars Ingebrigtsen
2022-05-16 7:58 ` Alan Mackenzie
2022-05-16 8:21 ` Protesilaos Stavrou
2022-05-16 11:15 ` Eli Zaretskii
2022-05-16 12:03 ` Alan Mackenzie
2022-05-16 12:26 ` Eli Zaretskii
2022-05-16 13:48 ` Alan Mackenzie
2022-05-16 13:56 ` Eli Zaretskii
2022-05-16 14:52 ` Protesilaos Stavrou
2022-05-16 15:56 ` Eli Zaretskii
2022-05-22 13:10 ` Alan Mackenzie
2022-05-22 13:25 ` Eli Zaretskii
2022-05-23 3:51 ` Protesilaos Stavrou
2022-05-23 10:57 ` Eli Zaretskii
2022-05-24 4:37 ` Protesilaos Stavrou [this message]
2022-05-24 11:09 ` Eli Zaretskii
2022-05-25 3:24 ` Protesilaos Stavrou
2022-05-25 13:12 ` Eli Zaretskii
2022-05-26 5:55 ` Protesilaos Stavrou
2022-05-26 11:32 ` Eli Zaretskii
2022-05-26 11:57 ` Lars Ingebrigtsen
2022-05-26 12:59 ` Eli Zaretskii
2022-05-26 15:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-26 15:42 ` Protesilaos Stavrou
2022-05-27 9:52 ` Alan Mackenzie
2022-05-27 10:25 ` Lars Ingebrigtsen
2022-05-26 16:02 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-26 15:30 ` Mattias Engdegård
2022-05-27 9:03 ` Mattias Engdegård
2022-05-27 10:23 ` Lars Ingebrigtsen
2022-05-27 10:39 ` Protesilaos Stavrou
2022-05-27 10:42 ` Lars Ingebrigtsen
2022-05-27 11:32 ` Alan Mackenzie
2022-05-27 11:52 ` Lars Ingebrigtsen
2022-05-27 13:42 ` Alan Mackenzie
2022-05-27 13:50 ` Lars Ingebrigtsen
2022-05-28 23:13 ` Richard Stallman
2022-05-27 12:15 ` Protesilaos Stavrou
2022-05-27 13:59 ` Alan Mackenzie
2022-05-27 16:53 ` Mattias Engdegård
2022-05-27 18:24 ` Alan Mackenzie
2022-05-29 9:18 ` Mattias Engdegård
2022-05-29 13:38 ` Alan Mackenzie
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=87v8tv7dht.fsf@protesilaos.com \
--to=info@protesilaos.com \
--cc=55414@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
/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).