diff options
| author | Alexey Lebedeff <binarin@binarin.info> | 2024-12-02 17:04:15 +0100 |
|---|---|---|
| committer | Lin Jian <me@linj.tech> | 2024-12-06 13:12:47 +0800 |
| commit | 5f9cbf9898b86c8151dde657c2023f3afdb714bf (patch) | |
| tree | ca791b296acec2717777071f57b923f53b342905 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 47b7878e2cbcafa75d342f98344c91c261a21149 (diff) | |
emacs: allow wrapped emacs to execute itself again
fixes #145302 #237855
emacsWithPackages wrapper script/`site-start.el` sanitize
EMACSLOADPATH, to make nested emacs invocations independent of the
package set specified in emacsWithPackages.
But there are valid use cases when one needs to call nested emacs with
the same package set. This includes built-in emacs functionality such
as async native compilations, and also external packages like
`emacs-async` and `esup`. In all of these cases
`invocation-directory`/`invocation-name` variables are being used to
launch nested emacs.
With this patch these variables will be populated to point to the
emacsWithPackages wrapper executable, so that executing
`(file-name-concat invocation-directory invocation-name)` will give a
fully functional emacs again.
`EMACSLOADPATH` sanitization was introduced by #106486, this behaviour
stays unchanged. The reasoning was to be able to run different emacs
executables without polluting their EMACSLOADPATH (as described here
https://github.com/NixOS/nixpkgs/pull/106486/commits/23d4bfb6661ca57a9e331a2cf4184232d38ac38b).
The only change is that invoking itself is again feasible (and that's
what emacs actually expects).
Co-authored-by: Lin Jian <me@linj.tech>
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions
