Lisp-friendly backtraces [was: Lispy backtraces]

[Clément Pit--Claudel]

On 2016-12-04 22:30, Eli Zaretskii wrote:
>>> So would it perhaps make sense to rename 'backtrace' into something
>>> like 'backtrace--internal', and make it accept one more argument, the
>>> function to apply to each frame, which is now hard-coded as 'prin1'?
>>> Would that allow you to implement 'backtrace' in Lisp and also
>>> implement whatever application you had in mind, by calling
>>> 'backtrace--internal' passing it your own function instead of 'prin1'?
>>
>> Quite possibly!
>
> Will you be working on this idea at some point?

Yup.  I've attached a rough patch, and an ELisp file showing what calling the 
new function (mapbacktrace) looks like.

Let me know if this direction makes sense.  If so, I will write the 
corresponding documentation, a Changelog entry, and a proper commit message.

(CC Alan, since you recently expressed frustration with the contents of the 
*Backtrace* buffer; hopefully this new function will help with implementing a 
more flexible *Backtrace* buffer?)

Cheers,
Clément.

0001-New-function-mapbacktrace.patch
Description: Text Data

bt.el
Description: Text Data

signature.asc
Description: OpenPGP digital signature