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: Add new functions to mark/unmark/delete all bookmarks Date: Sat, 25 Jul 2020 21:54:02 +0300 Message-ID: <83y2n7bf3p.fsf@gnu.org> References: <20200724005105.11f85d5f@pineapple> <87pn8ku3y9.fsf@red-bean.com> <20200725124618.49a073b1@pineapple> <83lfj7dfp2.fsf@gnu.org> <87tuxvpq1r.fsf@gmx.de> <83d04jd2pm.fsf@gnu.org> <87o8o3pp09.fsf@gmx.de> <83a6znd0bk.fsf@gnu.org> <838sf7d06s.fsf@gnu.org> <87k0yrpmte.fsf@gmx.de> <834kpvcz63.fsf@gnu.org> <20200725202856.7ae89cbe@pineapple> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20764"; mail-complaints-to="usenet@ciao.gmane.io" Cc: michael.albinus@gmx.de, drew.adams@oracle.com, emacs-devel@gnu.org To: Matthew White Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jul 25 20:55:22 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 1jzPKL-0005Jh-5G for ged-emacs-devel@m.gmane-mx.org; Sat, 25 Jul 2020 20:55:21 +0200 Original-Received: from localhost ([::1]:49154 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jzPKK-0004uX-7D for ged-emacs-devel@m.gmane-mx.org; Sat, 25 Jul 2020 14:55:20 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35544) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jzPJL-0003zq-DT for emacs-devel@gnu.org; Sat, 25 Jul 2020 14:54:19 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:48578) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jzPJK-00073s-7A; Sat, 25 Jul 2020 14:54:18 -0400 Original-Received: from [176.228.60.248] (port=2323 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jzPJH-0002R6-KZ; Sat, 25 Jul 2020 14:54:16 -0400 In-Reply-To: <20200725202856.7ae89cbe@pineapple> (message from Matthew White on Sat, 25 Jul 2020 20:28:56 +0200) 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:253231 Archived-At: > Date: Sat, 25 Jul 2020 20:28:56 +0200 > From: Matthew White > Cc: Eli Zaretskii , Michael Albinus , > Drew Adams > > What do you suggest? Is it ok to be consistent using Emacs style > in commit messages when typing Emacs' elements? There's no need to be "consistent" between Lisp comments and commit log messages. They are different contexts. In commit log messages please quote 'like this'. > There is also ‘this’ kind of quoting in Emacs. This requires non-ASCII characters, so could produce mojibake on some less capable displays. So please don't use that style in our log messages. Once again, we are talking only about commit log messages. Lisp comments, let alone doc strings, are another matter.