From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.devel Subject: Comments on setopt Date: Mon, 14 Feb 2022 23:01:00 +0000 Message-ID: <871r05rr2r.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34139"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Feb 15 00:04:22 2022 Return-path: Envelope-to: ged-emacs-devel@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 1nJkOM-0008j9-1N for ged-emacs-devel@m.gmane-mx.org; Tue, 15 Feb 2022 00:04:22 +0100 Original-Received: from localhost ([::1]:56958 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nJkOK-0004w3-JB for ged-emacs-devel@m.gmane-mx.org; Mon, 14 Feb 2022 18:04:20 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:46578) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nJkLO-00030j-Lv for emacs-devel@gnu.org; Mon, 14 Feb 2022 18:01:18 -0500 Original-Received: from mout01.posteo.de ([185.67.36.65]:48761) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nJkLI-0004vM-HK for emacs-devel@gnu.org; Mon, 14 Feb 2022 18:01:17 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 518DF240027 for ; Tue, 15 Feb 2022 00:01:07 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1644879667; bh=ZLGrB8kuxhU+FHQzJvqjSAtLaweZa8Iw5GJCLoPkbmI=; h=From:To:Cc:Subject:Autocrypt:Date:From; b=Zrh2pqLr7Qouo9TJWlLuHc+Ndqbevl8f9EcOT7JWvar42NIPia6hArVV59smjqrub HGnXSgLmv3ai2P5mcaId9TkEvQek4Igw1spK3lFANDRT7Yk4AfijRXPSc6Xp/BzrD9 rld674TN9FcUrDmJzKUqVr4GCjD2Y21RQIuc8yhSZ4/nvQOyFE8uRe/AyYn6NDfcR2 FtwIteMgOwPt4b2ZEh87wjyHaO2oMGA/s72rXpOjuVZ5Q20wUG/psPMPauvrus8cti xRz/5Cgi5/qJKn2JroU77Q+5LMPc59fS4EIEpzrzuxApmvKSvUs6C8bltp2rX6dW8b zenak5D7+ecnQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4JyKTG1d35z6tpy; Tue, 15 Feb 2022 00:01:05 +0100 (CET) Autocrypt: addr=philipk@posteo.net; prefer-encrypt=nopreference; keydata= mDMEYHHqUhYJKwYBBAHaRw8BAQdAp3GdmYJ6tm5McweY6dEvIYIiry+Oz9rU4MH6NHWK0Ee0QlBo aWxpcCBLYWx1ZGVyY2ljIChnZW5lcmF0ZWQgYnkgYXV0b2NyeXB0LmVsKSA8cGhpbGlwa0Bwb3N0 ZW8ubmV0PoiQBBMWCAA4FiEEDM2H44ZoPt9Ms0eHtVrAHPRh1FwFAmBx6lICGwMFCwkIBwIGFQoJ CAsCBBYCAwECHgECF4AACgkQtVrAHPRh1FyTkgEAjlbGPxFchvMbxzAES3r8QLuZgCxeAXunM9gh io0ePtUBALVhh9G6wIoZhl0gUCbQpoN/UJHI08Gm1qDob5zDxnIHuDgEYHHqUhIKKwYBBAGXVQEF AQEHQNcRB+MUimTMqoxxMMUERpOR+Q4b1KgncDZkhrO2ql1tAwEIB4h4BBgWCAAgFiEEDM2H44Zo Pt9Ms0eHtVrAHPRh1FwFAmBx6lICGwwACgkQtVrAHPRh1Fw1JwD/Qo7kvtib8jy7puyWrSv0MeTS g8qIxgoRWJE/KKdkCLEA/jb9b9/g8nnX+UcwHf/4VfKsjExlnND3FrBviXUW6NcB Received-SPF: pass client-ip=185.67.36.65; envelope-from=philipk@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:286303 Archived-At: Hi Lars, I'm glad to see the recent addition of the setopt macro. Having have experimented with similar macros in the past, I wanted to raise these points: - Unless it makes more sense for `customize-set-variable' to take care of it, should there be some type checking with errors or warnings if the value doesn't match the type of a user option? - As `customize-set-variable' is being used directly, the "user" theme is modified, and a customisation might be mirrored in `custom-set-variables'. This can lead to the unfortunate situation where your setopt configuration is overriden by the `custom-set-variables', depending on when and how you load `custom-file' and when and how the `custom-set-variables' was generated. - While I don't mind it really, I can imagine that others might object to the "long" name, when compared to setq. Would a default alias like "seto" or "setc" be worth it or not? -- Philip Kaludercic