`doom env` doesn't correctly capture my PATH about doomemacs HOT 3 OPEN

I can't reproduce Doom not picking up the $PATH from its containing environment without:

• Running doom env from within Emacs (in vterm, eshell, etc),
• Making the emacs executable a shim script with a shebang line invoking an interactive or sandboxed shell,
• Running doom env from inside a directory managed with direnv, or a sub-shell spawned by nix-shell (though, env would've caught this).

Try removing the env file by hand before running doom env again: rm -f ~/.emacs.d/.local/env; doom env

from doomemacs.

@hlissner My emacs is indeed a shim script:

❯ cat /home/x/.junest/usr/bin_wrappers/emacs
#!/usr/bin/env bash

eval "junest_args_array=(${JUNEST_ARGS:-ns})"
junest "${junest_args_array[@]}" -- $(basename ${0}) "$@"

What should I do?

junest might be the problem ... I don't really know how junest works. I use it to install emacs without having root access.

Trying various combinations of junest and env:

env -i HOME="$HOME" ${commands[junest]} $SHELL -ic env

env -i HOME="$HOME" ${commands[junest]} ns -- $SHELL -ic env

These still catch my PATH correctly ...

from doomemacs.

@hlissner When I use exec-path-from-shell, the PATH is captured correctly.

(require 'exec-path-from-shell)
(exec-path-from-shell-initialize)

from doomemacs.