From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.devel Subject: Re: master ff4de1b: Fix quoting style in Lisp comments Date: Fri, 17 Sep 2021 14:59:12 +0200 Message-ID: <87tuijbae9.fsf@gnu.org> References: <20210912165141.9491.52637@vcs0.savannah.gnu.org> <87sfy8d7oo.fsf@gnus.org> <9194fc93-fb9c-000f-a35a-321ddd259893@gmx.at> <8735q5yi63.fsf@mail.linkov.net> <83czp9by3s.fsf@gnu.org> <05cbffe0-f89b-ff54-64f5-cd1d11bac4f5@yandex.ru> <831r5pbt7j.fsf@gnu.org> <83wnnhacy4.fsf@gnu.org> <40937e22-994f-466c-87be-4f70a522118a@yandex.ru> <83pmt790cz.fsf@gnu.org> <41b90a60-04ab-8ef1-24ee-ac30d39640aa@yandex.ru> <837dff8niq.fsf@gnu.org> <8a9a14b9-c562-8813-daea-28108f3173f3@yandex.ru> <8335q38ktr.fsf@gnu.org> <2974ba74db56df1eeb0090cbab5b8177@webmail.orcon.net.nz> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31095"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.6.6; emacs 28.0.50 To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Sep 17 15:27:44 2021 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 1mRDu3-0007un-MQ for ged-emacs-devel@m.gmane-mx.org; Fri, 17 Sep 2021 15:27:43 +0200 Original-Received: from localhost ([::1]:50954 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mRDu1-0004zQ-Ec for ged-emacs-devel@m.gmane-mx.org; Fri, 17 Sep 2021 09:27:41 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51964) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mRDtL-0004JG-2n for emacs-devel@gnu.org; Fri, 17 Sep 2021 09:26:59 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:57982) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mRDtK-0005oc-S3 for emacs-devel@gnu.org; Fri, 17 Sep 2021 09:26:58 -0400 Original-Received: from auth1-smtp.messagingengine.com ([66.111.4.227]:44637) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mRDtK-00066j-Od for emacs-devel@gnu.org; Fri, 17 Sep 2021 09:26:58 -0400 Original-Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailauth.nyi.internal (Postfix) with ESMTP id 4264C27C0054 for ; Fri, 17 Sep 2021 09:26:58 -0400 (EDT) Original-Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 17 Sep 2021 09:26:58 -0400 X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudehiedgiedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpehffgfhvffuffgjkfggtgesthdtre dttdertdenucfhrhhomhepvfgrshhsihhlohcujfhorhhnuceothhsughhsehgnhhurdho rhhgqeenucggtffrrghtthgvrhhnpeevveeikeetkeeviefgfeffiedvteeguddvffeuue duveegtddthedvhfeuveffhfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhep mhgrihhlfhhrohhmpehthhhorhhnodhmvghsmhhtphgruhhthhhpvghrshhonhgrlhhith ihqdekieejfeekjeekgedqieefhedvleekqdhtshguhheppehgnhhurdhorhhgsehfrghs thhmrghilhdrfhhm X-ME-Proxy: Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Fri, 17 Sep 2021 09:26:57 -0400 (EDT) In-reply-to: <2974ba74db56df1eeb0090cbab5b8177@webmail.orcon.net.nz> 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:274873 Archived-At: Phil Sainty writes: >> It doesn't matter. This is a decision we already made, so just >> saying you don't like it is not good enough. We need a much stronger >> reason to reverse previous decisions. > > I might have missed something, but I think almost everyone else in > this thread has expressed some degree of surprise/confusion that elisp > comments would be categorised as "plain text" and/or the notion that > the previous decision was ever intended to apply to those. Just to add another data point: I didn't know the new convention and always used `...' in elisp code comments because it felt like the right way simply because it got highlighted and I had symbol-completion enabled after typing the ` in a comment. And I wouldn't have considered code comments in elisp files to be in the came category of plain-text documents like NEWS or ChangeLog. I don't consider `...' to be ugly but in the end I don't care as long as the style going to be used for quoting symbols in code comments is supported by font-lock and completion. In his regard, I do consider `...' or the markdown-style `...` to be quite good because they are seldomly used in prose or for emphasis in contrast to '...' reducing the likelyhood of false-positives. Bye, Tassilo