Timeline for Show line number on error
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 16, 2015 at 18:36 | comment | added | wasamasa | No, it won't. You get the function value of the symbol (which can either be a list or something byte-compiled) and that's pretty much it. | |
| Mar 16, 2015 at 18:05 | comment | added | Håkon Hægland |
Will this work if you don't use eval-buffer? For example, if you just press a keyboard shortcut that runs a private command that fails and opens the debugger in the *Backtrace* buffer..
|
|
| Feb 8, 2015 at 11:10 | history | edited | wasamasa | CC BY-SA 3.0 |
added 32 characters in body
|
| Feb 8, 2015 at 0:45 | vote | accept | Jackson Ray Hamilton | ||
| Feb 7, 2015 at 23:37 | comment | added | wasamasa |
With this code you'll see a line number in backtraces made by debug, you can check by visiting a faulty elisp file, doing M-x toggle-debug-on-error and M-x eval-buffer, then a backtrace with a line number at the problematic position should pop up.
|
|
| Feb 7, 2015 at 21:56 | comment | added | Jackson Ray Hamilton |
Thanks for your help, but I still don't understand how to get the line number. M-x debug ...? Then what do I press?
|
|
| Feb 1, 2015 at 8:03 | history | answered | wasamasa | CC BY-SA 3.0 |