From a9aedc7149db6c0d8a7afac09f07c892a1a3a690 Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Sun, 22 Dec 2024 12:11:46 +0200 Subject: [PATCH] ; Fix node name in emacs-lisp-intro.texi * doc/lispintro/emacs-lisp-intro.texi (Lexical vs Dynamic Binding Example): Renamed from "... vs. ...", to avoid using period in node names. (cherry picked from commit 861b7864fc4b8319a8f8756f02e9a4cfcc25bbfe) --- doc/lispintro/emacs-lisp-intro.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/lispintro/emacs-lisp-intro.texi b/doc/lispintro/emacs-lisp-intro.texi index 2f8df449379..0b513007fce 100644 --- a/doc/lispintro/emacs-lisp-intro.texi +++ b/doc/lispintro/emacs-lisp-intro.texi @@ -3773,7 +3773,7 @@ elisp, The Emacs Lisp Reference Manual}. @menu * Lexical & Dynamic Binding Differences:: -* Lexical vs. Dynamic Binding Example:: +* Lexical vs Dynamic Binding Example:: @end menu @node Lexical & Dynamic Binding Differences @@ -3810,7 +3810,7 @@ on the top of the stack, and then executes the @code{let} body. Once the @code{let} body finishes, it takes that binding off of the stack, revealing the one it had (if any) before the @code{let} expression. -@node Lexical vs. Dynamic Binding Example +@node Lexical vs Dynamic Binding Example @unnumberedsubsubsec Example of Lexical vs. Dynamic Binding In some cases, both lexical and dynamic binding behave identically. However, in other cases, they can change the meaning of your program. -- 2.39.5