* Why elisp-flymake-byte-compile-load-path doesn't contain everything in load-path?
@ 2022-11-23 6:59 Akib Azmain Turja
0 siblings, 0 replies; only message in thread
From: Akib Azmain Turja @ 2022-11-23 6:59 UTC (permalink / raw)
To: emacs-devel
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
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."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-11-23 6:59 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-23 6:59 Why elisp-flymake-byte-compile-load-path doesn't contain everything in load-path? Akib Azmain Turja
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).