From: Gregory Heytings <gregory@heytings.org>
To: Richard Stallman <rms@gnu.org>
Cc: 21695@debbugs.gnu.org, hmelman@gmail.com, larsi@gnus.org
Subject: bug#21695: 25.0.50; Change most occurrences of `setq' in Emacs manual to `customize-set-variable'? Really?
Date: Sat, 18 Sep 2021 09:20:50 +0000 [thread overview]
Message-ID: <be3d426f709c268f7134@heytings.org> (raw)
In-Reply-To: <E1mROFk-0001T9-N6@fencepost.gnu.org>
>
> everything else in this discussion seems to support the opposite
> conclusion: setting one of these variables with setq in an init file, in
> the usual simple case (you haven't loaded the definition yet), is
> perfectly ok.
>
Understanding statements always requires some context. Using setq on a
variable that hasn't been loaded is indeed okay, but that does not
contradict what Martin said, because a variable that hasn't been loaded
never has a :set form (even if its definition contains a :set form). In
summary:
1. 'foo' does not have a :set form in its definition => it's okay to set
it with setq, no warning is displayed
2. 'foo' has a :set form in its definition, but its definition hasn't been
loaded => it's okay to set it with setq, no warning is displayed
3. 'foo' has a :set form in its definition, and its definition has been
loaded => it's a bug to set it with setq, a warning is displayed
There are a number of corner cases that are not covered by the above
description, however:
1. if you eval-buffer your init file during an Emacs session, definitions
have been loaded in the meantime, so you get warnings you didn't get when
you started Emacs; are these legitimate warnings?
2. if you byte-compile your init file, setq's become set's, so the
warnings you would see with your non-byte-compiled init files are not
displayed anymore; should they be displayed?
3. in (some) files in which variables with a :set form are defined, setq
is used to set them (which means that warnings would be displayed if they
were eval-buffer'd or loaded without byte-compiling them); are these
legitimate warnings? is it a bug to use setq in those files?
next prev parent reply other threads:[~2021-09-18 9:20 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
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 [this message]
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=be3d426f709c268f7134@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).