diff options
author | jao <jao@gnu.org> | 2024-07-05 14:52:33 +0100 |
---|---|---|
committer | jao <jao@gnu.org> | 2024-07-05 14:52:33 +0100 |
commit | 410a3a50d724c0aaf8d209d6a620976828854881 (patch) | |
tree | 4fc845800cf17568445bb19ea4133567f7124e31 | |
parent | 2d3e4f9b3a83e4c42139e6b7b7ce84490c80d1eb (diff) | |
download | geiser-410a3a50d724c0aaf8d209d6a620976828854881.tar.gz geiser-410a3a50d724c0aaf8d209d6a620976828854881.tar.bz2 |
further clarifications re geiser-custom
A note on why we won't use the mapatom trick to make geiser-custom--defcustom
obsolete while still preserving geiser-reload functionality (cf. !22).
-rw-r--r-- | elisp/geiser-custom.el | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/elisp/geiser-custom.el b/elisp/geiser-custom.el index 7125f11..f9b05a7 100644 --- a/elisp/geiser-custom.el +++ b/elisp/geiser-custom.el @@ -47,9 +47,12 @@ in the macro arguments." (defvar geiser-custom--memoized-vars nil) (defun geiser-custom--memoize (name) - ;; FIXME: Why not build this list with mapatoms, filtering on a "\\`'geiser-" + ;; Why not build this list with mapatoms, filtering on a "\\`'geiser-" ;; prefix and checking that it's a `defcustom', so we don't need - ;; `geiser-custom--defcustom'? + ;; `geiser-custom--defcustom'? Because implementation-specific modules using + ;; geiser may use similarly named custom variables that are, for some reason + ;; or another, not meant to partake in the geiser-reload mechanism, and we + ;; don't know their names. (add-to-list 'geiser-custom--memoized-vars name)) (defmacro geiser-custom--defcustom (name &rest body) |