Ruijie Yu <rui...@netyu.xyz> writes: >> 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?
Not really. It is a common problem that users keep using `setq' instead of `setopt', customize interface, or `custom-set-variables'. Lin Sun's solution is one approach to deal with this problem for `org-babel-load-languages', but only partial, as I outlined. I'd prefer to use either `add-variable-watcher' or oc.el-like API with `org-cite-try-load-processor' being called when babel backend information is requested. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
