Subject: PATCH

From: Paul Pogonyshev <[email-masked]>
Date: Tue, 27 Oct 2020 01:10:58 +0100

Trivial patch attached.
From 87d927a3a61f16fa908b5dd1c00457023f269114 Mon Sep 17 00:00:00 2001
From: Paul Pogonyshev <[email-masked]>
Date: Tue, 27 Oct 2020 01:08:19 +0100
Subject: [PATCH] Don't leak result of nested byte-compilation to outer level
 (bug#41065)

---
 lisp/emacs-lisp/bytecomp.el | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/lisp/emacs-lisp/bytecomp.el b/lisp/emacs-lisp/bytecomp.el
index a547b672b1..cbda16d051 100644
--- a/lisp/emacs-lisp/bytecomp.el
+++ b/lisp/emacs-lisp/bytecomp.el
@@ -1938,7 +1938,7 @@ byte-compile-file
         (byte-compile--known-dynamic-vars
          (byte-compile--load-dynvars (getenv "EMACS_DYNVARS_FILE")))
 	target-file input-buffer output-buffer
-	byte-compile-dest-file)
+	byte-compile-dest-file byte-compiler-error-flag)
     (setq target-file (byte-compile-dest-file filename))
     (setq byte-compile-dest-file target-file)
     (with-current-buffer
@@ -2000,7 +2000,6 @@ byte-compile-file
 	  'no-byte-compile)
       (when byte-compile-verbose
 	(message "Compiling %s..." filename))
-      (setq byte-compiler-error-flag nil)
       ;; It is important that input-buffer not be current at this call,
       ;; so that the value of point set in input-buffer
       ;; within byte-compile-from-buffer lingers in that buffer.
-- 
2.20.1