From: Ihor Radchenko <email@example.com>
Subject: defcustom :set vs. add-variable-watcher
Date: Thu, 05 Jan 2023 08:06:45 +0000 [thread overview]
Message-ID: <87a62xiewa.fsf@localhost> (raw)
AFAIK, the traditional way to provide side effects to customization
value changes if :set option in `defcustom' definition.
However, it has been suggested  that one might also utilize
`add-variable-watcher' for the same purpose.
Given that many users don't actually use customize interface and instead
tend to set variables directly, `add-variable-watcher' looks like a more
reliable option compared to :set.
Are there any reasons to prefer :set over `add-variable-watcher'? Maybe
some non-obvious pitfalls?
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>
reply other threads:[~2023-01-05 8:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).