From: Eli Zaretskii <eliz@gnu.org>
Date: Fri, 26 Feb 2021 14:50:41 +0000 (+0200)
Subject: Fix last change
X-Git-Tag: emacs-28.0.90~2727^2~121
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=5540d73441a8fb518cc876ba01561d0875739283;p=emacs.git

Fix last change

* lisp/emacs-lisp/comp.el (comp-async-report-warnings-errors):
Improve wording of the doc string.
---

diff --git a/lisp/emacs-lisp/comp.el b/lisp/emacs-lisp/comp.el
index 184aef489dc..d559fa02514 100644
--- a/lisp/emacs-lisp/comp.el
+++ b/lisp/emacs-lisp/comp.el
@@ -126,16 +126,18 @@ Usable to modify the compiler environment."
 (defcustom comp-async-report-warnings-errors t
   "Whether to report warnings and errors from asynchronous native compilation.
 
-When native compilation happens asynchronously this can produce
-warnings and errors, some of these diagnostic messages might not be
-emitted by the first synchronous byte-compilation.  The typical case
-for that is byte-compiling a file that is missing to require a
-necessary feature while having it already loaded into the environment.
-
-As asynchronous native compilation always starts from a fresh
-environment it is more sensitive into highlighting issues about non
-consistent source files and might not be able to compile correctly
-these."
+When native compilation happens asynchronously, it can produce
+warnings and errors, some of which might not be emitted by a
+byte-compilation.  The typical case for that is native-compiling
+a file that is missing some `require' of a necessary feature,
+while having it already loaded into the environment when
+byte-compiling.
+
+As asynchronous native compilation always starts from a pristine
+environment, it is more sensitive to such omissions, and might be
+unable to compile such Lisp source files correctly.
+
+Set this variable to nil if these warnings annoy you."
   :type 'boolean)
 
 (defcustom comp-async-query-on-exit nil