From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Robert Weiner Newsgroups: gmane.emacs.devel Subject: Re: Proposal: stack traces with line numbers Date: Sat, 14 Oct 2017 23:40:59 -0400 Message-ID: References: Reply-To: rswgnu@gmail.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a11473a8454c5cf055b8daa75" X-Trace: blaine.gmane.org 1508038920 9240 195.159.176.226 (15 Oct 2017 03:42:00 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 15 Oct 2017 03:42:00 +0000 (UTC) Cc: emacs-devel To: John Williams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Oct 15 05:41:56 2017 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 1e3Zo8-0000a0-1B for ged-emacs-devel@m.gmane.org; Sun, 15 Oct 2017 05:41:44 +0200 Original-Received: from localhost ([::1]:56033 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3ZoF-0000Q0-6l for ged-emacs-devel@m.gmane.org; Sat, 14 Oct 2017 23:41:51 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53612) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3Znz-0000O9-Cs for emacs-devel@gnu.org; Sat, 14 Oct 2017 23:41:36 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e3Znu-0007Ta-Lj for emacs-devel@gnu.org; Sat, 14 Oct 2017 23:41:35 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:60922) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3Znu-0007TU-Hb for emacs-devel@gnu.org; Sat, 14 Oct 2017 23:41:30 -0400 Original-Received: from mail-qk0-f175.google.com ([209.85.220.175]:52092) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1e3Znu-0002Yp-7w for emacs-devel@gnu.org; Sat, 14 Oct 2017 23:41:30 -0400 Original-Received: by mail-qk0-f175.google.com with SMTP id 17so9217757qkq.8 for ; Sat, 14 Oct 2017 20:41:30 -0700 (PDT) X-Gm-Message-State: AMCzsaWUkWbOmE9dBzqMSgZWxKxNcZvr73fdU8H1jHv6zuMG2yF5+Kqf BgSkJ2hqKaAnnc49drrHzI7Cdq/bOCa8kU2sqVo= X-Google-Smtp-Source: ABhQp+RBTxS8+8bbm1VQHKVcheu37H58pqErGS5YTYog2oxdIjMPDOGnJ9M72178rQA/zGlMXI1xbHSMNwzqufAcu+c= X-Received: by 10.55.25.85 with SMTP id k82mr7971082qkh.223.1508038889750; Sat, 14 Oct 2017 20:41:29 -0700 (PDT) Original-Received: by 10.237.34.225 with HTTP; Sat, 14 Oct 2017 20:40:59 -0700 (PDT) In-Reply-To: X-Gmail-Original-Message-ID: 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:219541 Archived-At: --001a11473a8454c5cf055b8daa75 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Oct 14, 2017 at 8:17 PM, John Williams wrote: > Elisp is a fun language to work in, for the most part, but one thing I > find very irritating compared to other languages is that there's no > way to get a stack trace with line numbers. I'm wondering if others > feel the same way and would be open to accepting a change to add > better support for line numbers. =E2=80=8BSounds like some nice work that will pinpoint Lisp errors even more closely than stack traces do now. But as noted in an earlier message, things are not bad in the Lisp space. Emacs C code is where we often lack any reasonable pointer to the source of an error, so improving upon the core mechanisms there would be most valuable. Bob --001a11473a8454c5cf055b8daa75 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sat, Oct 14, 2= 017 at 8:17 PM, John Williams <j= rw@pobox.com> wr= ote:
=
Elisp is a fun language to work in, for the = most part, but one thing I
find very irritating compared to other languages is that there's no
way to get a stack trace with line numbers. I'm wondering if others
feel the same way and would be open to accepting a change to add
better support for line numbers.

=E2=80=8BSounds lik= e some nice work that will pinpoint Lisp errors
even more closely than sta= ck traces do now.=C2=A0 But as noted
in an earlier message, things are not= bad in the Lisp space.
Emacs C code is where we often lack any reasonable= pointer
to the source of an error, so improving upon the core
mechanisms= there would be most valuable.

Bob

--001a11473a8454c5cf055b8daa75--