Ihor Radchenko <yanta...@posteo.net> writes:
> Ruijie Yu <rui...@netyu.xyz> writes: > >>> 1. `setopt' already triggers loading when variable is set. It is just >>> `setq', often used in place of `setopt', that does not trigger >>> loading/unloading. >> >> Speaking of which, since we now (or are about to?) depend on compat, we >> can just do (require 'compat) and forget that `setopt' is an Emacs 29 >> addition. > > No. Compat does not support and does not plan to support `setopt' (see > https://elpa.gnu.org/packages/doc/compat.html#Limitations). > And it is not us who needs to use `setopt', but users. > We just have to deal with de facto situation with users using `setq' > mindlessly. Makes sense. So, does that mean nothing should be changed, except for maybe some additions to documentation mentioning that the users should avoid using `setq' to set customizable variables, and instead use `setopt' if >= 29, or [some function in cus-edit.el which I don't recall] otherwise? -- Best, RY [Please note that this mail might go to spam due to some misconfiguration in my mail server -- still investigating.]