From: Eugene Medvedev <rn3aoh.g@gmail.com>
Date: Tue, 6 Sep 2016 08:23:27 +0000 (+0300)
Subject: emacs: Patch for the load-history problem (#433)
X-Git-Url: https://git.distorted.org.uk/~mdw/termux-packages/commitdiff_plain/51fb4b0d1de784cca2b8cb42e0a0aa72cb0321a3

emacs: Patch for the load-history problem (#433)

Closes termux/termux-packages#423
---

diff --git a/packages/emacs/lisp-loadup.el-2.patch.beforehostbuild b/packages/emacs/lisp-loadup.el-2.patch.beforehostbuild
new file mode 100644
index 00000000..e316780c
--- /dev/null
+++ b/packages/emacs/lisp-loadup.el-2.patch.beforehostbuild
@@ -0,0 +1,16 @@
+diff -u -r ../emacs-25.0.92/lisp/loadup.el ./lisp/loadup.el
+--- ../emacs-25.0.92/lisp/loadup.el	2016-09-06 09:49:51.838175278 +0300
++++ ./lisp/loadup.el	2016-09-06 09:57:18.694585441 +0300
+@@ -378,7 +378,11 @@
+       (message "Warning: Change in load-path due to site-init will be \
+ lost after dumping")))
+ 
+-(setq current-load-list nil)
++;; On an emacs that runs undumped, i.e. Android, this causes bogus 
++;; entries to appear in load-history. Commenting this out causes an entry
++;; for loadup.el with a bogus filename to appear instead, but since it
++;; neither provides nor requires anything, it appears to be safe.
++;;(setq current-load-list nil)
+ ;; Avoid storing references to build directory in the binary.
+ (setq custom-current-group-alist nil)
+