Commit 9c5047fb authored by Juanma Barranquero's avatar Juanma Barranquero
Browse files

Backport 2011-03-01T03:59:31Z!lekktu@gmail.com from trunk.

*lisp/emacs-lisp/cl-macs.el (lexical-let*): Fix argument name in docstring.
parent 6dbf95e5
2011-03-11 Juanma Barranquero <lekktu@gmail.com>
Backport revno:103463 from trunk.
* emacs-lisp/cl-macs.el (lexical-let*): Fix argument name in docstring.
Backport revno:103622 from trunk.
* help-fns.el (describe-variable): Don't complete keywords.
Suggested by Teodor Zlatanov <tzz@lifelogs.com>.
......
......@@ -282,7 +282,7 @@ Not documented
;;;;;; flet progv psetq do-all-symbols do-symbols dotimes dolist
;;;;;; do* do loop return-from return block etypecase typecase ecase
;;;;;; case load-time-value eval-when destructuring-bind function*
;;;;;; defmacro* defun* gentemp gensym) "cl-macs" "cl-macs.el" "75e86ac663887b54bf1778f2dd028463")
;;;;;; defmacro* defun* gentemp gensym) "cl-macs" "cl-macs.el" "12451ac01f94f10d30cf7a8f92625c42")
;;; Generated autoloads from cl-macs.el
(autoload 'gensym "cl-macs" "\
......@@ -505,7 +505,7 @@ lexical closures as in Common Lisp.
(autoload 'lexical-let* "cl-macs" "\
Like `let*', but lexically scoped.
The main visible difference is that lambdas inside BODY, and in
successive bindings within BINDINGS, will create lexical closures
successive bindings within VARLIST, will create lexical closures
as in Common Lisp. This is similar to the behavior of `let*' in
Common Lisp.
......
......@@ -1455,7 +1455,7 @@ lexical closures as in Common Lisp.
(defmacro lexical-let* (bindings &rest body)
"Like `let*', but lexically scoped.
The main visible difference is that lambdas inside BODY, and in
successive bindings within BINDINGS, will create lexical closures
successive bindings within VARLIST, will create lexical closures
as in Common Lisp. This is similar to the behavior of `let*' in
Common Lisp.
\n(fn VARLIST BODY)"
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment