From: Gregory Heytings <gregory@heytings.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 21695@debbugs.gnu.org, hmelman@gmail.com, Richard Stallman <rms@gnu.org>
Subject: bug#21695: 25.0.50; Change most occurrences of `setq' in Emacs manual to `customize-set-variable'? Really?
Date: Sun, 12 Sep 2021 08:23:01 +0000 [thread overview]
Message-ID: <0d48a23084a8b0435f37@heytings.org> (raw)
In-Reply-To: <ca43a526bebda84c59d2@heytings.org>
[-- Attachment #1: Type: text/plain, Size: 88 bytes --]
I updated the patch with some documentation.
Is there any chance that it gets applied?
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-diff; name=Warn-when-custom-variable-is-wrongly-set.patch, Size: 2997 bytes --]
From ea9eeb65d6514c11ae9d0ac5c4fad36213e303f9 Mon Sep 17 00:00:00 2001
From: Gregory Heytings <gregory@heytings.org>
Date: Sun, 12 Sep 2021 08:19:25 +0000
Subject: [PATCH] Warn when custom variable is wrongly set.
* src/eval.c (Fsetq): Display warning when a custom variable with a :set
property is set with setq. Warnings are displayed only for custom variables
whose files have been loaded and that have a :set property. No warnings are
displayed for custom variables whose files have merely been preloaded,
for custom variables that do not have a :set property, and for non-custom
variables. See bug#21695.
* etc/NEWS: Document the warning.
* doc/emacs/custom.texi: Mention the warning.
---
doc/emacs/custom.texi | 3 ++-
etc/NEWS | 6 ++++++
src/eval.c | 9 ++++++++-
3 files changed, 16 insertions(+), 2 deletions(-)
diff --git a/doc/emacs/custom.texi b/doc/emacs/custom.texi
index 9220a2078f..1b7e7d9361 100644
--- a/doc/emacs/custom.texi
+++ b/doc/emacs/custom.texi
@@ -2378,7 +2378,8 @@ do that; to enable the mode in your init file, call the minor mode
command. Finally, a few customizable user options are initialized in
complex ways, and these have to be set either via the customize
interface (@pxref{Customization}) or by using
-@code{customize-set-variable} (@pxref{Examining}).
+@code{customize-set-variable} (@pxref{Examining}). If such options
+are inadvertently set with @code{setq}, a warning is displayed.
The second argument to @code{setq} is an expression for the new
value of the variable. This can be a constant, a variable, or a
diff --git a/etc/NEWS b/etc/NEWS
index ca269aabaa..dfdd925ec5 100644
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -3401,6 +3401,12 @@ truncating precision field, such as "%.2a".
Such mixes are always signs that the outer lexical binding was an
error and should have used dynamic binding instead.
+--
+** 'setq' displays a warning when 'customize-set-variable' should have been used.
+Some custom variables need to be set with 'customize-set-variable', because
+they were designed to be set through the Customization interface and have a
+:set lambda form which does other things after they have been set.
+
---
** New variable 'inhibit-mouse-event-check'.
If bound to non-nil, a command with '(interactive "e")' doesn't signal
diff --git a/src/eval.c b/src/eval.c
index 48104bd0f4..168a7749a0 100644
--- a/src/eval.c
+++ b/src/eval.c
@@ -525,8 +525,15 @@ usage: (setq [SYM VAL]...) */)
: Qnil);
if (!NILP (lex_binding))
XSETCDR (lex_binding, val); /* SYM is lexically bound. */
- else
+ else {
+ if (!NILP (Fget (sym, intern ("custom-set"))))
+ call2 (intern ("display-warning"), intern ("setq"),
+ CALLN (Fformat,
+ build_string
+ ("`%s' should be set with `customize-set-variable'"),
+ sym));
Fset (sym, val); /* SYM is dynamically bound. */
+ }
}
return val;
--
2.33.0
next prev parent reply other threads:[~2021-09-12 8:23 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 21:50 bug#21695: 25.0.50; Change most occurrences of `setq' in Emacs manual to `customize-set-variable' Drew Adams
2015-10-16 23:57 ` Drew Adams
2021-05-26 22:30 ` Lars Ingebrigtsen
2021-08-29 19:05 ` Drew Adams
2021-08-29 22:36 ` Drew Adams
2021-08-29 22:52 ` Drew Adams
2021-08-29 22:58 ` Drew Adams
2021-08-31 3:06 ` bug#21695: 25.0.50; Change most occurrences of `setq' in Emacs manual to `customize-set-variable'? Really? Richard Stallman
2021-08-31 3:43 ` Arthur Miller
2021-08-31 16:15 ` bug#21695: [External] : " Drew Adams
2021-08-31 16:15 ` Drew Adams
2021-09-02 6:53 ` Kevin Vigouroux via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-02 17:08 ` Drew Adams
2021-09-03 9:54 ` bug#21695: 25.0.50; Change most occurrences of `setq' in Emacs manual to `customize-set-variable' Kevin Vigouroux via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-01 3:07 ` bug#21695: 25.0.50; Change most occurrences of `setq' in Emacs manual to `customize-set-variable'? Really? Howard Melman
2021-09-02 3:42 ` Richard Stallman
2021-09-02 6:53 ` Eli Zaretskii
2021-09-02 17:08 ` bug#21695: [External] : " Drew Adams
2021-09-02 17:17 ` Eli Zaretskii
2021-09-05 3:42 ` Richard Stallman
2021-09-05 3:43 ` Richard Stallman
2021-09-06 17:43 ` Eli Zaretskii
2021-09-08 3:23 ` Richard Stallman
2021-09-08 7:03 ` Eli Zaretskii
2021-09-09 3:11 ` Richard Stallman
2021-09-09 6:52 ` Eli Zaretskii
2021-09-09 7:43 ` Gregory Heytings
2021-09-09 11:44 ` Gregory Heytings
2021-09-09 12:07 ` Lars Ingebrigtsen
2021-09-09 12:12 ` Gregory Heytings
2021-09-09 12:15 ` Lars Ingebrigtsen
2021-09-09 12:40 ` Gregory Heytings
2021-09-09 12:47 ` Lars Ingebrigtsen
2021-09-09 13:04 ` Gregory Heytings
2021-09-09 13:10 ` Lars Ingebrigtsen
2021-09-09 14:27 ` Gregory Heytings
2021-09-10 10:15 ` Lars Ingebrigtsen
2021-09-10 14:26 ` Gregory Heytings
2021-09-12 8:23 ` Gregory Heytings [this message]
2021-09-12 8:57 ` Eli Zaretskii
2021-09-12 9:30 ` Gregory Heytings
2021-09-12 9:37 ` Eli Zaretskii
2021-09-12 9:54 ` Gregory Heytings
2021-09-12 10:11 ` Eli Zaretskii
2021-09-12 10:21 ` Eli Zaretskii
2021-09-12 21:26 ` Gregory Heytings
2021-09-12 22:11 ` Gregory Heytings
2021-09-13 7:04 ` Lars Ingebrigtsen
2021-09-13 9:11 ` Gregory Heytings
2021-09-13 9:18 ` Lars Ingebrigtsen
2021-09-13 13:00 ` Gregory Heytings
2021-09-13 13:56 ` Eli Zaretskii
2021-09-13 12:17 ` Eli Zaretskii
2021-09-13 11:31 ` Eli Zaretskii
2021-09-13 8:03 ` martin rudalics
2021-09-13 9:14 ` Gregory Heytings
2021-09-13 12:36 ` martin rudalics
2021-09-13 12:52 ` Gregory Heytings
2021-09-15 9:27 ` martin rudalics
2021-09-15 10:00 ` Gregory Heytings
2021-09-15 20:13 ` Richard Stallman
2021-09-16 6:56 ` martin rudalics
2021-09-18 0:30 ` Richard Stallman
2021-09-18 7:34 ` martin rudalics
2021-09-18 9:20 ` Gregory Heytings
2021-09-13 1:17 ` Richard Stallman
2021-09-10 3:41 ` Richard Stallman
2021-09-10 13:49 ` Gregory Heytings
2021-09-13 1:17 ` Richard Stallman
2021-09-02 17:08 ` bug#21695: [External] : " Drew Adams
2021-09-05 3:42 ` Richard Stallman
2021-09-04 3:38 ` Richard Stallman
2021-09-01 12:48 ` Augusto Stoffel
2021-09-02 3:38 ` Richard Stallman
2021-09-02 6:56 ` Eli Zaretskii
2021-09-02 17:07 ` bug#21695: [External] : " Drew Adams
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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 \
--in-reply-to=0d48a23084a8b0435f37@heytings.org \
--to=gregory@heytings.org \
--cc=21695@debbugs.gnu.org \
--cc=hmelman@gmail.com \
--cc=larsi@gnus.org \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs.git
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).