[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Proposal: stack traces with line numbers
From: |
Noam Postavsky |
Subject: |
Re: Proposal: stack traces with line numbers |
Date: |
Sat, 14 Oct 2017 23:20:15 -0400 |
On Sat, Oct 14, 2017 at 10:42 PM, raman <address@hidden> wrote:
> Actually pressing enter on a line in the backtrace buffer jumps to the
> appropriate source code -- what more would line numbers give us?
Well, jumping to a particular line might be more useful than just
jumping to the beginning of a function. In practice, I find the
current behaviour of jumping to the function is generally good enough.
Apropos line numbers, there is also the long-standing issue of
inaccurate line numbers in byte compile errors & warnings (Bug#2681),
I think Alan was working on it, but perhaps it's stalled since I don't
recall any mention of it since July [1]. At any rate, since both these
things involve changes to the reader, probably some coordination is in
order. In particular, the shortcut of only taking line numbers for the
head of list might not be sensible if we want to solve the
error/warning line numbering problem too. Stefan had some ideas about
a "real" solution in [2].
[Bug#2681]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=2681
[1]: https://lists.gnu.org/archive/html/emacs-devel/2017-07/msg00653.html
[2]: https://lists.gnu.org/archive/html/emacs-devel/2017-07/msg00729.html
- Proposal: stack traces with line numbers, John Williams, 2017/10/14
- Re: Proposal: stack traces with line numbers, Daniele Nicolodi, 2017/10/14
- Re: Proposal: stack traces with line numbers, raman, 2017/10/14
- Re: Proposal: stack traces with line numbers,
Noam Postavsky <=
- Re: Proposal: stack traces with line numbers, Robert Weiner, 2017/10/14
- Re: Proposal: stack traces with line numbers, Helmut Eller, 2017/10/15
- Re: Proposal: stack traces with line numbers, Richard Stallman, 2017/10/15
- Re: Proposal: stack traces with line numbers, Wilfred Hughes, 2017/10/16