Re: bug#24514: 24.5; Lispy backtraces

[Eli Zaretskii]

> Cc: address@hidden
> From: Clément Pit--Claudel <address@hidden>
> Date: Sun, 4 Dec 2016 17:14:38 -0500
> 
> > 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! Are you worried about the cost of allocating a list 
> containing all frames? 

No, I'm not worried about that.

> a variant of backtrace taking a callback would definitely make 
> backtrace-frames easy to implement on the lisp side :)

Yup.

> There's no big hurry on this, anyway: it's just that we recently added a neat 
> option to backtrace, and there were mentions of making the backtrace buffer 
> more useful in various ways, too.

Will you be working on this idea at some point?