* lisp/loadup.el: Don't accidentally reduce max-lisp-eval-depth
This commit is contained in:
parent
73582ed6d4
commit
b513036770
1 changed files with 1 additions and 1 deletions
|
@ -103,7 +103,7 @@
|
|||
;; During bootstrapping the byte-compiler is run interpreted
|
||||
;; when compiling itself, which uses a lot more stack
|
||||
;; than usual.
|
||||
(setq max-lisp-eval-depth 3400)))
|
||||
(setq max-lisp-eval-depth (max max-lisp-eval-depth 3400))))
|
||||
|
||||
(if (eq t purify-flag)
|
||||
;; Hash consing saved around 11% of pure space in my tests.
|
||||
|
|
Loading…
Add table
Reference in a new issue