From: Robert Weiner <rsw@gnu.org>
To: John Williams <jrw@pobox.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Proposal: stack traces with line numbers
Date: Sat, 14 Oct 2017 23:40:59 -0400 [thread overview]
Message-ID: <CA+OMD9j8yEc9g1GDF4qOW_hu+-GzWEHS8EqxfVBXLcQ4d0Q8fQ@mail.gmail.com> (raw)
In-Reply-To: <CAEdRJLD=PROHc59mqK7s6AehoYSY4+bkRUO-uQDJ5_B-xQYpZw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
On Sat, Oct 14, 2017 at 8:17 PM, John Williams <jrw@pobox.com> 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.
Sounds 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
[-- Attachment #2: Type: text/html, Size: 1907 bytes --]
next prev parent reply other threads:[~2017-10-15 3:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 0:17 Proposal: stack traces with line numbers John Williams
2017-10-15 1:54 ` Daniele Nicolodi
2017-10-15 2:42 ` raman
2017-10-15 3:20 ` Noam Postavsky
2017-10-15 3:40 ` Robert Weiner [this message]
2017-10-15 10:01 ` Helmut Eller
2017-10-15 16:20 ` Stefan Monnier
2017-10-16 22:43 ` John Williams
2017-10-17 0:00 ` Helmut Eller
2017-10-18 15:00 ` John Williams
2017-10-16 1:53 ` Richard Stallman
2017-10-16 21:51 ` Wilfred Hughes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+OMD9j8yEc9g1GDF4qOW_hu+-GzWEHS8EqxfVBXLcQ4d0Q8fQ@mail.gmail.com \
--to=rsw@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jrw@pobox.com \
--cc=rswgnu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).