From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Re: Algorithm in electric-pair--unbalanced-strings-p unsuitable for CC Mode Date: Wed, 3 Jul 2019 13:32:17 +0000 Message-ID: <20190703133217.GC11238@ACM> References: <20190702131632.GA30597@ACM> <20190702160410.GB30597@ACM> <20190702182811.GC30597@ACM> <20190703105804.GA11238@ACM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="212607"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.10.1 (2018-07-13) Cc: =?iso-8859-1?Q?Jo=E3o_T=E1vora?= , emacs-devel To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 03 15:44:08 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hifYL-000spI-RD for ged-emacs-devel@m.gmane.org; Wed, 03 Jul 2019 15:44:05 +0200 Original-Received: from localhost ([::1]:36066 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hifO8-0003Zz-D3 for ged-emacs-devel@m.gmane.org; Wed, 03 Jul 2019 09:33:32 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41808) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hifN4-0003XS-CA for emacs-devel@gnu.org; Wed, 03 Jul 2019 09:32:27 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hifN3-0006yw-Aq for emacs-devel@gnu.org; Wed, 03 Jul 2019 09:32:26 -0400 Original-Received: from colin.muc.de ([193.149.48.1]:40655 helo=mail.muc.de) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1hifN3-0006wO-4M for emacs-devel@gnu.org; Wed, 03 Jul 2019 09:32:25 -0400 Original-Received: (qmail 6412 invoked by uid 3782); 3 Jul 2019 13:32:19 -0000 Original-Received: from acm.muc.de (p4FE15C0A.dip0.t-ipconnect.de [79.225.92.10]) by colin.muc.de (tmda-ofmipd) with ESMTP; Wed, 03 Jul 2019 15:32:17 +0200 Original-Received: (qmail 11941 invoked by uid 1000); 3 Jul 2019 13:32:17 -0000 Content-Disposition: inline In-Reply-To: X-Delivery-Agent: TMDA/1.1.12 (Macallan) X-Primary-Address: acm@muc.de X-detected-operating-system: by eggs.gnu.org: FreeBSD 9.x [fuzzy] X-Received-From: 193.149.48.1 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:238327 Archived-At: Hello, Dmitry. On Wed, Jul 03, 2019 at 16:07:59 +0300, Dmitry Gutov wrote: > On 03.07.2019 13:58, Alan Mackenzie wrote: > >> But only in Emacs 27/cc-mode, probably starting from fe06f64b (that's > >> a git commit hash). > > I'm fully aware it's a git commit hash. Funnily enough, I don't > > memorise such hashes, so if you wish to draw my attention to some > > commit, please have the decency to give me its date, and the summary > > line of its commit message, instead of expecting me to do your work to > > make your point. > The rest of the discussion aside, IMO it's a very strange reply. Though > I might be biased, given that a lot of my software-related discussions > are on platforms that linkify commit hashes. > Even so, is calling 'git show fe06f64b' too hard to do? Yes. As you'll have noticed, this is an adversarial debate rather than a constructive cooperation, and expecting me to put in unnecessary work in order to assist my opponent in making a point against me is not reasonable. Surely it is a matter of plain ettiquette: for the writer to put in that little extra bit of work himself, rather than forcing his readers to do it. When writing, I always do this myself. Besides, other people will read this post, and they'll have to remain mystified, or put in the work themselves. Giving a cryptic, rather than a meaningful, reference thus costs more time than it saves. Besides[2], the next time we move to a new VCS, the reference will become totally meaningless. > I would print its output on this occasion here, but in this case Git > says it's 'ambiguous'. So maybe Joao should elaborate. -- Alan Mackenzie (Nuremberg, Germany).