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.devel Subject: Re: adding to emacs coding standard / formatting Date: Mon, 19 Oct 2020 17:32:57 +0300 Message-ID: <83tuuqp9pi.fsf@gnu.org> References: <20201019031002.iulr45ztrkwsiqlo@E15-2016.optimum.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8695"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Boruch Baum Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Oct 19 16:37:42 2020 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 1kUWIA-00026J-EG for ged-emacs-devel@m.gmane-mx.org; Mon, 19 Oct 2020 16:37:42 +0200 Original-Received: from localhost ([::1]:53954 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kUWI9-00066V-F8 for ged-emacs-devel@m.gmane-mx.org; Mon, 19 Oct 2020 10:37:41 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59504) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kUWDT-00021x-BH for emacs-devel@gnu.org; Mon, 19 Oct 2020 10:32:51 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:34974) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kUWDS-0005eH-SR; Mon, 19 Oct 2020 10:32:50 -0400 Original-Received: from [176.228.60.248] (port=4625 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kUWDS-0005Iv-G3; Mon, 19 Oct 2020 10:32:50 -0400 In-Reply-To: <20201019031002.iulr45ztrkwsiqlo@E15-2016.optimum.net> (message from Boruch Baum on Sun, 18 Oct 2020 23:10:02 -0400) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:258118 Archived-At: > Date: Sun, 18 Oct 2020 23:10:02 -0400 > From: Boruch Baum > > I had expecting symbol definitions to be grouped together by symbol type > and function, eg. all `defcustom's to be listed together in a section > beginning "^;;; Customization variables:", and so on for symbol > categories ";;; Global variables:", ";;; Buffer-local variables", ";;; > Internal functions:", ";;; Hook functions:", ";;; Interactive > functions:", etc. Many packages group together defcustoms, variables, and functions that belong to a logical sub-group of features (and normally indicate such a group with a ^L character). I don't see why we should disallow such organization, it is useful to have related stuff close. > Also, this is an opportunity to address a pet peeve: I occasionally see > code either defining keybindings to lambda functions, or setting lambda > functions as elements of function lists (eg. lists of hook functions). > I'd like to propose that those uses be banned because of their > difficulty to modify. Where would you allow lambda functions, then?