From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Thoughts on getting correct line numbers in the byte compiler's warning messages Date: Mon, 12 Nov 2018 18:19:25 +0200 Message-ID: <83wopi8e0i.fsf@gnu.org> References: <20181107170036.GA4934@ACM> <20181107184708.GB4934@ACM> <20181108140843.GB5041@ACM> <20181108221311.GD5041@ACM> <20181111125945.GA6487@ACM> <83k1lja9w6.fsf@gnu.org> <20181111201214.GA8219@ACM> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1542039523 10670 195.159.176.226 (12 Nov 2018 16:18:43 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 12 Nov 2018 16:18:43 +0000 (UTC) Cc: michael_heerdegen@web.de, monnier@IRO.UMontreal.CA, emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 12 17:18:39 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gMEv8-0002ds-5k for ged-emacs-devel@m.gmane.org; Mon, 12 Nov 2018 17:18:38 +0100 Original-Received: from localhost ([::1]:49429 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gMExE-0006Gm-AB for ged-emacs-devel@m.gmane.org; Mon, 12 Nov 2018 11:20:48 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40624) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gMEwF-0006FU-Tf for emacs-devel@gnu.org; Mon, 12 Nov 2018 11:19:48 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gMEw7-0007F0-2H for emacs-devel@gnu.org; Mon, 12 Nov 2018 11:19:45 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:45775) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gMEw4-0007De-4q; Mon, 12 Nov 2018 11:19:37 -0500 Original-Received: from [176.228.60.248] (port=4321 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gMEw1-0007Nl-Fg; Mon, 12 Nov 2018 11:19:34 -0500 In-reply-to: <20181111201214.GA8219@ACM> (message from Alan Mackenzie on Sun, 11 Nov 2018 20:12:14 +0000) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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:231097 Archived-At: > Date: Sun, 11 Nov 2018 20:12:14 +0000 > Cc: michael_heerdegen@web.de, monnier@IRO.UMontreal.CA, emacs-devel@gnu.org > From: Alan Mackenzie > > > This needs support in src/.gdbinit and documentation. > > Yes! I think .gdbinit will be relatively straightforward. How much to > put into the docs (the elisp manual?) is more difficult to decide. > Although primariliy for the byte compiler, Michael Heerdegen has already > said he's got other uses for it. The object and its predicate(s) should be documented, as well as the new primitive which uses it, read-positioning-symbols. The printed representation of the new Lisp object should also be documented (we do that for every other Lisp object). And there should be a short announcement in NEWS.