From: Stefan Kangas Date: Sun, 15 Dec 2024 18:14:04 +0000 (+0100) Subject: Improve purify-flag docstring X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=9e05dfa8c36d80d3f88a94b153f9af3b6a420c1b;p=emacs.git Improve purify-flag docstring * src/alloc.c (syms_of_alloc): Improve purify-flag docstring. (cherry picked from commit f818744cd4b1dddece0a221b06e6e83740e06e2d) --- diff --git a/src/alloc.c b/src/alloc.c index dfa1d68d122..40a59854a87 100644 --- a/src/alloc.c +++ b/src/alloc.c @@ -7569,13 +7569,11 @@ If this portion is smaller than `gc-cons-threshold', this is ignored. */); DEFVAR_LISP ("purify-flag", Vpurify_flag, doc: /* Non-nil means loading Lisp code in order to dump an executable. -This used to mean that certain objects should be allocated in shared (pure) -space. It can also be set to a hash-table, in which case this table is used -to do hash-consing of the objects allocated to pure space. -The hash-consing still applies, but objects are not allocated in pure -storage any more. -This flag is still used in a few places not to decide where objects are -allocated but to know if we're in the preload phase of Emacs's build. */); +This used to mean that certain objects should be allocated in shared +(pure) space, but objects are not allocated in pure storage any more. +This flag is still used in a few places, not to decide where objects are +allocated, but to know if we're in the preload phase of Emacs's +build. */); DEFVAR_BOOL ("garbage-collection-messages", garbage_collection_messages, doc: /* Non-nil means display messages at start and end of garbage collection. */);