emenel/doomemacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Don't exec postscript #3746

Browse source 
Doesn't seem to persist exported environment variables (like __DOOMPOST)
in some windows environments.
This commit is contained in:
Henrik Lissner 2020-08-25 20:22:06 -04:00
parent 239516a7db
commit 47b42a9d08
No known key found for this signature in database
GPG key ID: 5F6C0EA160557395
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
bin/doom
View file

@ -4,7 +4,7 @@
:; export __DOOMPOST="${TMPDIR:-/tmp}/doom.sh" :; export __DOOMPOST="${TMPDIR:-/tmp}/doom.sh"
:; $EMACS --version >/dev/null 2>&1 || { >&2 echo "Can't find emacs in your PATH"; exit 1; } :; $EMACS --version >/dev/null 2>&1 || { >&2 echo "Can't find emacs in your PATH"; exit 1; }
:; $EMACS --no-site-file --script "$0" -- "$@" || __DOOMCODE=$? :; $EMACS --no-site-file --script "$0" -- "$@" || __DOOMCODE=$?
:; [ "${__DOOMCODE:-0}" -eq 128 ] && exec "$__DOOMPOST" "$0" "$@" :; [ "${__DOOMCODE:-0}" -eq 128 ] && { "$__DOOMPOST" "$0" "$@" && true; __DOOMCODE=$?; }
:; exit $__DOOMCODE :; exit $__DOOMCODE
;; The garbage collector isn't important during CLI ops. A higher threshold ;; The garbage collector isn't important during CLI ops. A higher threshold