From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: <emacs-devel@gnu.org>
Subject: Byte-compilation of custom themes
Date: Sat, 20 Jan 2018 21:01:03 +0000 [thread overview]
Message-ID: <87efmk2qk0.fsf@tcd.ie> (raw)
This email is a follow-up to a question[1] I asked on the Emacs Stack
Exchange Q&A forum a couple of months ago, which received no answers in
the interim.
[1] https://emacs.stackexchange.com/q/36892/15748
I am wondering why custom themes are ordinarily left non-byte-compiled,
based on the following observations:
1. All built-in themes under etc/themes/ set the file variable
no-byte-compile to t.
2. The function custom-available-themes in lisp/custom.el considers only
*-theme.el and not *-theme.elc files under custom-theme-load-path.
3. The command load-theme in lisp/custom.el is able to load *-theme.elc
files under custom-theme-load-path, but does so only if there is no
corresponding source file in the same directory.
4. The manual nodes '(elisp) Custom Themes', '(emacs) Custom Themes' and
'(emacs) Creating Custom Themes' make no mention of byte-compilation.
Is this "aversion" to byte-compilation of custom themes intentional? If
so, what is the reasoning behind it? Should the documentation be
extended to describe it?
If not, should the functions custom-available-themes and load-theme be
made made less picky about which file extensions they consider? Should
the behaviour of the latter be likened more to the that of the load
function in src/lread.c?
FWIW, I have not noticed any issues when using my own byte-compiled
custom themes. The only minor nuisance is having to keep the source
files separate from their translations and out of
custom-theme-load-path.
Thanks,
--
Basil
next reply other threads:[~2018-01-20 21:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 21:01 Basil L. Contovounesios [this message]
2018-01-24 16:16 ` Byte-compilation of custom themes Stefan Monnier
2018-01-30 22:16 ` Basil L. Contovounesios
2018-01-31 2:26 ` Stefan Monnier
2018-02-01 0:45 ` Basil L. Contovounesios
2018-02-02 14:25 ` Stefan Monnier
2018-05-10 2:49 ` Basil L. Contovounesios
2018-05-10 2:54 ` Basil L. Contovounesios
2018-05-11 14:07 ` Eli Zaretskii
2018-05-11 14:02 ` Eli Zaretskii
2018-05-11 15:16 ` Basil L. Contovounesios
2018-05-11 16:03 ` Stefan Monnier
2018-05-11 20:03 ` Basil L. Contovounesios
2018-05-11 17:32 ` Eli Zaretskii
2018-05-11 20:43 ` Basil L. Contovounesios
2018-05-12 7:04 ` Eli Zaretskii
2018-06-01 20:48 ` Basil L. Contovounesios
2018-06-01 21:07 ` Basil L. Contovounesios
2018-06-02 11:24 ` Eli Zaretskii
2018-06-02 18:53 ` Basil L. Contovounesios
2018-06-02 19:32 ` Eli Zaretskii
2018-06-02 20:02 ` Basil L. Contovounesios
2018-06-03 3:52 ` Stefan Monnier
2018-06-03 11:21 ` Basil L. Contovounesios
2018-06-03 15:11 ` Eli Zaretskii
2018-06-03 16:08 ` Basil L. Contovounesios
2018-06-03 16:16 ` Eli Zaretskii
2018-06-03 17:48 ` Basil L. Contovounesios
2018-06-03 20:22 ` Stefan Monnier
2018-06-04 1:33 ` Basil L. Contovounesios
2018-07-03 7:57 ` Basil L. Contovounesios
2018-07-11 1:40 ` Stefan Monnier
2018-07-11 6:05 ` Basil L. Contovounesios
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efmk2qk0.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=emacs-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.