From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#21695: 25.0.50; Change most occurrences of `setq' in Emacs manual to `customize-set-variable'? Really? Date: Thu, 02 Sep 2021 09:56:19 +0300 Message-ID: <837dfzpiss.fsf@gnu.org> References: <97d3ff2c-9e72-4004-88a9-08130ac99a74@default> <878s0g796w.fsf@gmail.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26669"; mail-complaints-to="usenet@ciao.gmane.io" Cc: ke.vigouroux@laposte.net, 21695@debbugs.gnu.org, arstoffel@gmail.com, larsi@gnus.org To: rms@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Sep 02 08:57:24 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mLgf5-0006gm-UY for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 02 Sep 2021 08:57:23 +0200 Original-Received: from localhost ([::1]:48424 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mLgf4-0006Cc-Ee for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 02 Sep 2021 02:57:22 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52292) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mLgej-0006CP-Q3 for bug-gnu-emacs@gnu.org; Thu, 02 Sep 2021 02:57:01 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:56200) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mLgej-0004uv-IT for bug-gnu-emacs@gnu.org; Thu, 02 Sep 2021 02:57:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mLgej-0002eE-Ht for bug-gnu-emacs@gnu.org; Thu, 02 Sep 2021 02:57:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 02 Sep 2021 06:57:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 21695 X-GNU-PR-Package: emacs Original-Received: via spool by 21695-submit@debbugs.gnu.org id=B21695.163056579410143 (code B ref 21695); Thu, 02 Sep 2021 06:57:01 +0000 Original-Received: (at 21695) by debbugs.gnu.org; 2 Sep 2021 06:56:34 +0000 Original-Received: from localhost ([127.0.0.1]:39513 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mLgeI-0002dX-G6 for submit@debbugs.gnu.org; Thu, 02 Sep 2021 02:56:34 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:36172) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mLgeG-0002dK-Gg for 21695@debbugs.gnu.org; Thu, 02 Sep 2021 02:56:32 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:51114) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mLgeB-0004T9-3X; Thu, 02 Sep 2021 02:56:27 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:3005 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mLge4-0000Bw-Rq; Thu, 02 Sep 2021 02:56:21 -0400 In-Reply-To: (message from Richard Stallman on Wed, 01 Sep 2021 23:38:37 -0400) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:213235 Archived-At: > From: Richard Stallman > Date: Wed, 01 Sep 2021 23:38:37 -0400 > Cc: ke.vigouroux@laposte.net, 21695@debbugs.gnu.org, larsi@gnus.org > > > Maybe calling setq during init time on automatically buffer-local > > variables should generate a warning. > > Perhaps it should do that only if you're in the buffer that is > current by default during the init files. > > I think the basic idea of this warning is good. > There are various possble ways to implement a warning, > so it would be useful to look, now, for the best way. That could be done, but let's please keep in mind that warnings shown during startup are notoriously easy to miss, especially if your startup sequence does a lot. Those messages flush in the echo-area, interspersed with a lot of informative messages from features that are initialized at startup, and the only way to see them is to look in *Messages* after startup, something that is unlikely to be done by a lot of us.