From: Gregory Heytings <gregory@heytings.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 21695@debbugs.gnu.org, hmelman@gmail.com, rms@gnu.org
Subject: bug#21695: 25.0.50; Change most occurrences of `setq' in Emacs manual to `customize-set-variable'? Really?
Date: Mon, 13 Sep 2021 13:00:15 +0000 [thread overview]
Message-ID: <97113ce8baf7455e6f58@heytings.org> (raw)
In-Reply-To: <87fsu8esvg.fsf@gnus.org>
>> That being said, I would say that using (setq latin1-display t) when
>> latin1-display has a :set is always a bug, in the init file,
>> interactively, or in built-in code (bytecompiled or not), and that (set
>> 'latin1-display t) should be used instead. WDYT?
>
> I have not studied the code -- I just picked a variable at random. The
> point is that code in a package will commonly use setq on the user
> options to implement the code, and this is how it should be.
>
My point is that code that sets a user option that has a :set should set
it with (set 'foo val) instead of (setq foo val).
I just checked: on the current trunk, there are 331 defcustoms with a
:set. Out of these, only 49 are set with setq, 33 only at one place, and
16 more than once. That would require changing 85 setq's into set's.
>
> (Also note that your patch will issue a bunch of warnings if the user
> does an `eval-buffer' after loading .emacs into a buffer and then
> evaling it (in a running Emacs).)
>
There are not that many custom variables that will behave differently when
the init file is first loaded and when it is eval-buffer'd. AFAICS this
will only happen for variables whose files have been loaded in the
meantime after they have been setq'd.
next prev parent reply other threads:[~2021-09-13 13:00 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
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 [this message]
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=97113ce8baf7455e6f58@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).