[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Why elisp-flymake-byte-compile-load-path doesn't contain everything in l
|
From: |
Akib Azmain Turja |
|
Subject: |
Why elisp-flymake-byte-compile-load-path doesn't contain everything in load-path? |
|
Date: |
Wed, 23 Nov 2022 12:59:40 +0600 |
Flymake's Emacs Lisp checker uses elisp-flymake-byte-compile-load-path
instead of load-path, and it only contains the current directory. But
why?
If this is for security reasons (I think it's not), then I'd say this
doesn't really work, since byte compilation can execute arbitrary code.
--
Akib Azmain Turja, GPG key: 70018CE5819F17A3BBA666AFE74F0EFA922AE7F5
Fediverse: akib@hostux.social
Codeberg: akib
emailselfdefense.fsf.org | "Nothing can be secure without encryption."
signature.asc
Description: PGP signature
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- Why elisp-flymake-byte-compile-load-path doesn't contain everything in load-path?,
Akib Azmain Turja <=