[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] fix/bug-31311-pcase-doc 2db5695: for @var{symbol}, also me
From: |
Thien-Thi Nguyen |
Subject: |
[Emacs-diffs] fix/bug-31311-pcase-doc 2db5695: for @var{symbol}, also mention unsuitability of keyword symbols |
Date: |
Wed, 16 May 2018 06:22:33 -0400 (EDT) |
branch: fix/bug-31311-pcase-doc
commit 2db569560cd56b0d8bd0005b545f14c6454ee444
Author: Thien-Thi Nguyen <address@hidden>
Commit: Thien-Thi Nguyen <address@hidden>
for @var{symbol}, also mention unsuitability of keyword symbols
---
doc/lispref/control.texi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/doc/lispref/control.texi b/doc/lispref/control.texi
index 0a85c1a..7766af3 100644
--- a/doc/lispref/control.texi
+++ b/doc/lispref/control.texi
@@ -362,7 +362,8 @@ This usage has some caveats
(@pxref{pcase-symbol-caveats,,caveats}).
Two symbols to avoid are @code{t}, which behaves like @code{_}
(above) and is deprecated, and @code{nil}, which signals error.
-It makes no sense to bind these (@pxref{Constant Variables}).
+Likewise, it makes no sense to bind keyword symbols
+(@pxref{Constant Variables}).
@item (pred @var{function})
Matches if the predicate @var{function} returns address@hidden
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] fix/bug-31311-pcase-doc 2db5695: for @var{symbol}, also mention unsuitability of keyword symbols,
Thien-Thi Nguyen <=