summaryrefslogtreecommitdiff
path: root/src/emacs.c
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2023-03-12 16:19:49 +0200
committerEli Zaretskii <eliz@gnu.org>2023-03-12 16:19:49 +0200
commit42335c2c1f18c250719dd621a1923d0f40b82927 (patch)
tree17eb4823aaa137a23ad8f757cc7f5572003f17d7 /src/emacs.c
parentfffbce29349b14daa5f9b9c97ff5ba230b56c247 (diff)
downloademacs-42335c2c1f18c250719dd621a1923d0f40b82927.tar.gz
Fix value history shown for 'gc-cons-percentage'
When Emacs is built, temacs is run in batch mode, so if we enlarge 'gc-cons-percentage' in that case, the enlarged value will be "remembered" by the dumped Emacs, and will show confusing information in "C-h v", claiming that the original value was 1.0. Keeping the value at 0.1 during dumping avoids that. * src/emacs.c (main): Increase 'gc-cons-percentage' in batch mode only if we are not initializing (a.k.a. "dumping") Emacs.
Diffstat (limited to 'src/emacs.c')
-rw-r--r--src/emacs.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/emacs.c b/src/emacs.c
index 214e2e2a296..e63b0924282 100644
--- a/src/emacs.c
+++ b/src/emacs.c
@@ -1954,7 +1954,7 @@ Using an Emacs configured with --with-x-toolkit=lucid does not have this problem
/* Do less garbage collection in batch mode (since these tend to be
more short-lived, and the memory is returned to the OS on exit
anyway). */
- Vgc_cons_percentage = make_float (noninteractive? 1.0: 0.1);
+ Vgc_cons_percentage = make_float (noninteractive && initialized ? 1.0 : 0.1);
no_loadup
= argmatch (argv, argc, "-nl", "--no-loadup", 6, NULL, &skip_args);