From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Robert Weiner Newsgroups: gmane.emacs.devel Subject: Re: custom-set-variables considered harmful Date: Fri, 1 Dec 2017 15:42:13 -0500 Message-ID: References: <8782ed42-3aec-4111-b4f0-471c838e7370@default> Reply-To: rswgnu@gmail.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a114a71661b8718055f4d69ef" X-Trace: blaine.gmane.org 1512161045 8824 195.159.176.226 (1 Dec 2017 20:44:05 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 1 Dec 2017 20:44:05 +0000 (UTC) Cc: Philippe Vaucher , =?UTF-8?Q?Elias_M=C3=A5rtenson?= , Stefan Monnier , emacs-devel To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 01 21:44:01 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eKsAC-0001vg-5S for ged-emacs-devel@m.gmane.org; Fri, 01 Dec 2017 21:44:00 +0100 Original-Received: from localhost ([::1]:60914 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eKsAJ-0005v4-Fk for ged-emacs-devel@m.gmane.org; Fri, 01 Dec 2017 15:44:07 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57399) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eKs92-0005sk-7A for emacs-devel@gnu.org; Fri, 01 Dec 2017 15:42:49 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eKs8z-0004Cp-2B for emacs-devel@gnu.org; Fri, 01 Dec 2017 15:42:48 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:35331) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eKs8y-0004CZ-Ub for emacs-devel@gnu.org; Fri, 01 Dec 2017 15:42:44 -0500 Original-Received: from mail-qk0-f176.google.com ([209.85.220.176]:42882) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1eKs8y-0007Bl-JG for emacs-devel@gnu.org; Fri, 01 Dec 2017 15:42:44 -0500 Original-Received: by mail-qk0-f176.google.com with SMTP id a71so14755608qkc.9 for ; Fri, 01 Dec 2017 12:42:44 -0800 (PST) X-Gm-Message-State: AKGB3mKyB28TnaNzgpMBIo0PF6R3YK9VL6bLCrBkMa7/h19Wd8Xe63c8 F8CEcMZ5pR+S+scM+FKRXg28hUMpvmEX+KOLrys= X-Google-Smtp-Source: AGs4zMbobMpz9B0hXg4wwTZmQUxtYNKEoCQbVSPdjsLjctCpQr8ffmWbLS+FISLAAWEAyz7LWdEuST8TvtyK8KQN2OM= X-Received: by 10.55.80.8 with SMTP id e8mr9697105qkb.126.1512160964083; Fri, 01 Dec 2017 12:42:44 -0800 (PST) Original-Received: by 10.200.55.124 with HTTP; Fri, 1 Dec 2017 12:42:13 -0800 (PST) In-Reply-To: <8782ed42-3aec-4111-b4f0-471c838e7370@default> X-Gmail-Original-Message-ID: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:220590 Archived-At: --001a114a71661b8718055f4d69ef Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Nov 29, 2017 at 10:03 AM, Drew Adams wrote: > > Here's a crazy possibility (not a suggestion, but maybe > food for thought): Make `setq' do `customize-set-variable' > for an option and do what it does now otherwise. > =E2=80=8BI have been wondering about this too. Are there any arguments for= not having setq run the setter of a custom option when available? Is it a performance issue? Is it a load ordering issue? If there is no fundamental issue, then this would be great because one wouldn't have to worry about the type of a variable when setting it. Bob --001a114a71661b8718055f4d69ef Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Nov 29, 2= 017 at 10:03 AM, Drew Adams <drew.adams@oracle.com> wrote:

Here's a crazy possibility (not a suggestion, but maybe
food for thought): Make `setq' do `customize-set-variable'
for an option and do what it does now otherwise.

<= /div>
=E2=80=8BI have been wondering about this too.=C2=A0 Are there any argumen= ts for not having setq run the setter of a custom option when available?=C2= =A0 Is it a performance issue?
Is it a load ordering issue?

If ther= e is no fundamental issue, then this would be great because one wouldn'= t have to worry about the type of a variable when setting it.

Bo= b

--001a114a71661b8718055f4d69ef--