You could also set native-compile-target-directory, although it's not clear to me that this is safe, so it's probably better to manipulate the path list. See C-h v comp-el-to-eln-filename for details. It does indeed seem that native-comp-eln-load-path is used when deciding where to write. See C-h i g (elisp)Watching Variables for that. Failing that, I'd suggest using a variable watcher to try to track down when it's getting modified. You could use emacs-startup-hook to act after other start-up procedures, or to check what the value is at that point in the proceedings. I tried your code in 28.0.90 and couldn't replicate the problem, though, so whatever that "something else" is seems non-standard to me (at least in this version). That same function subsequently calls command-line to process your init files (both early-init-el and init.el), so whatever you do there should be sticking unless there's something else again messing with the value. See normal-top-level in startup.el for where that happens. I don't understand what the problem is here. emacs.d and the eln files are all then subsequently created there as well. in the cache dir) right at the start-up of emacs but a new eln-cache dir is always also created at the root of my. I will get a few files compiled in the proper place (i.e. (setq native-comp-async-report-warnings-errors nil) (expand-file-name (convert-standard-filename ".local/temp/cache/eln-cache/") (when (boundp 'native-comp-eln-load-path) I have this in the opening of my early-init.el file: Dir for eln-cache I would like the eln-cache for natively compiled files (I'm using emacs 29, built from the master branch) to be in a custom location.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |