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.bugs Subject: bug#50658: Error messages including function names violates coding conventions Date: Sat, 18 Sep 2021 18:00:00 +0300 Message-ID: <83h7ei53pr.fsf@gnu.org> References: <83y27u5efd.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39379"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 50658@debbugs.gnu.org To: Stefan Kangas Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Sep 18 17:01:23 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1mRbqE-000A5T-Lj for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 18 Sep 2021 17:01:22 +0200 Original-Received: from localhost ([::1]:49300 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mRbqC-0001nG-9I for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 18 Sep 2021 11:01:20 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57270) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mRbpv-0001lE-4V for bug-gnu-emacs@gnu.org; Sat, 18 Sep 2021 11:01:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:53127) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mRbpu-0000qK-OO for bug-gnu-emacs@gnu.org; Sat, 18 Sep 2021 11:01:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mRbpu-0002PM-HD for bug-gnu-emacs@gnu.org; Sat, 18 Sep 2021 11:01:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 18 Sep 2021 15:01:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 50658 X-GNU-PR-Package: emacs Original-Received: via spool by 50658-submit@debbugs.gnu.org id=B50658.16319772469225 (code B ref 50658); Sat, 18 Sep 2021 15:01:02 +0000 Original-Received: (at 50658) by debbugs.gnu.org; 18 Sep 2021 15:00:46 +0000 Original-Received: from localhost ([127.0.0.1]:36440 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mRbpb-0002Og-01 for submit@debbugs.gnu.org; Sat, 18 Sep 2021 11:00:46 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:40144) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mRbpY-0002OQ-Nk for 50658@debbugs.gnu.org; Sat, 18 Sep 2021 11:00:41 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:54846) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mRbpS-0000Rk-2O; Sat, 18 Sep 2021 11:00:35 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1408 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mRbp8-00042x-Lh; Sat, 18 Sep 2021 11:00:17 -0400 In-Reply-To: (message from Stefan Kangas on Sat, 18 Sep 2021 07:54:26 -0700) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:214642 Archived-At: > From: Stefan Kangas > Date: Sat, 18 Sep 2021 07:54:26 -0700 > Cc: 50658@debbugs.gnu.org > > While working on this, I realized that it is impossible to know if in > something like: > > (error "frobnicator not available") > > The 'frobnicator' part is a Lisp symbol (that can be in lower-case), or > if it is a regular word (that must be capitalized). It would obviously > be helpful if our conventions could be unambiguous. > > Perhaps we could add a requirement here, something like: a Lisp symbol > must always be in `quotes', or behind ": "? Yes, I think the idea is that the error message proper starts after the colon. > (I guess this would also affect the text we want to put in `(elisp) > Documentation Tips'.) Yes.