branch: externals/emms
commit dcc6f99d348ea0ed14682e1166dce24279768f3f
Author: Erica Lina <erical...@proton.me>
Commit: Erica Lina <erical...@proton.me>
repplace references of lexical-let to let with lexcal-bindings.
---
doc/emms.texinfo | 8 ++++----
emms-filters.el | 10 +++++-----
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/doc/emms.texinfo b/doc/emms.texinfo
index d36ed15c56..1730de33d6 100644
--- a/doc/emms.texinfo
+++ b/doc/emms.texinfo
@@ -2738,7 +2738,7 @@ Here is a summary of differences and features of the
filter system.
@item Filters return true if they match the tracks.
@item Filters are lambda functions created with factories from data.
@item There is no difference between a search function and a filter function.
-@item The factory should wrap the lambda in a lexical-let.
+@item The factory should wrap the lambda in a let with lexical-binding t.
@item The factories and the filters must both be registered with Emms-filters.
@item Registered factories have a built in interactive prompting system.
@item Any results can be pushed to the cache stack for future filters and
searches.
@@ -2786,9 +2786,9 @@ order to create new filters at any time.
Filter factories depend upon lexical context of their parameters. In
order to have data values that stick after function creation there
-is lexical-let to ensure the factory behaves as expected.
+is let with lexical-binding to ensure the factory behaves as expected.
This transfers the values to local values and uses them as normal
-in the returned #'(lambda (track)...) anonymous function.
+within the returned #'(lambda (track)...) anonymous function.
As an example, here is the generic field-compare function.
It takes an operator function, a field name and the value to compare.
@@ -2801,7 +2801,7 @@ using any comparison function we would like.
Works for number fields and string fields provided the appropriate
type match between values and the comparison function. Partials can
easily make more specific factory functions from this one."
- (lexical-let ((local-operator operator-func)
+ (let ((local-operator operator-func)
(local-field field)
(local-compare-val compare-val))
#'(lambda (track)
diff --git a/emms-filters.el b/emms-filters.el
index 96fb18c210..596bcc2ba6 100644
--- a/emms-filters.el
+++ b/emms-filters.el
@@ -133,7 +133,7 @@
;;
;; Filters are slightly different when coded for emms-filters.
;; 1. They should return true if they match the tracks
-;; 2. The factory should wrap the lambda in a lexical-let.
+;; 2. The factory should wrap the lambda in a let with lexical-binding t.
;; 3. The factory and the filters must both be registered with emms-filters.
;; This provides a higher level of interaction with the filters.
;; 4. There is no difference between a search function and a filter function.
@@ -194,16 +194,16 @@
;;
;; Filter factories depend upon lexical context of their parameters. In
;; order to have data values that stick after function creation there
-;; is lexical-let to ensure the factory behaves as expected.
-;; This transfers the values to local values and uses them as normal
-;; in the returned #'(lambda (track)...).
+;; is let using lexical binding to ensure the factory behaves as expected.
+;; This transfers the values to local values and uses them as local
+;; within the returned #'(lambda (track)...).
;;
;; (defun emms-filters-make-filter-field-compare (operator-func field
compare-val)
;; "Make a filter that compares FIELD to COMPARE-VALUE with OPERATOR-FUNC.
;; Works for number fields and string fields provided the appropriate
;; type match between values and the comparison function. Partials can
;; easily make more specific factory functions from this one."
-;; (lexical-let ((local-operator operator-func)
+;; (let ((local-operator operator-func)
;; (local-field field)
;; (local-compare-val compare-val))
;; #'(lambda (track)
