4

I'm thinking of writing one so that when I get those horrible tracebacks from bytecode files, I can better see where I was at.

Is there one already?

Are there any other tools for showing an error traceback in more Elisp programmer terms rather than computer- (not-human)-oriented elisp bytecode?

Edit: For what it's worth, I've started this on github

It seems to work find on the subset of things I've put in so far. So the two major items are to fill it out more which I have been doing slowly, and covert it all to Emacs Lisp from Python. (That too seems straightforward, just a bit of work.)

  • Have a look at disassemble. – Tobias Sep 10 '17 at 6:33
  • Um, I said decompile not "disassemble". However decompilers generally start off with a disasembly. See en.wikipedia.org/wiki/Decompiler – rocky Sep 10 '17 at 7:37
  • Personally, I believe that for the usecase of showing decent backtraces you'd be better off fixing Emacs than writing a decompiler. – wasamasa Sep 10 '17 at 8:56
  • 2
    Not yet, as far as I know. But I think they're working on providing this in an upcoming Emacs release (26.1?). See this and subsequent messages in Emacs bug #25295 thread. – Drew Sep 10 '17 at 15:04
  • 1
    Yes, that thread does not explicitly say that they plan to use what is discussed there to make backtrace parts that currently show byte-code be human-readable. Good idea to ask Stefan. But perhaps see also bug #6991. – Drew Sep 11 '17 at 0:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.