From: Eli Zaretskii <eliz@gnu.org>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: bug#24514: 24.5; Lispy backtraces
Date: Mon, 05 Dec 2016 05:30:41 +0200 [thread overview]
Message-ID: <838trvkq72.fsf@gnu.org> (raw)
In-Reply-To: <233f14a0-7542-5d0c-d8da-209e7e5e54f7@gmail.com> (message from Clément Pit--Claudel on Sun, 4 Dec 2016 17:14:38 -0500)
> Cc: emacs-devel@gnu.org
> From: Clément Pit--Claudel <clement.pit@gmail.com>
> 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?
next prev parent reply other threads:[~2016-12-05 3:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160922231447.GA3833@odonien.localdomain>
[not found] ` <98fbb582-3da4-bd83-a2e9-e341dd7f6140@gmail.com>
[not found] ` <20160923075116.GA612@odonien.localdomain>
[not found] ` <82e39377-f31b-698c-5a9a-343868686799@gmail.com>
[not found] ` <20161202005226.GA4215@odonien.localdomain>
2016-12-02 1:23 ` bug#24514: 24.5; Lispy backtraces Clément Pit--Claudel
2016-12-02 2:24 ` Stefan Monnier
2016-12-03 22:15 ` Clément Pit--Claudel
2016-12-04 15:30 ` Eli Zaretskii
2016-12-04 19:27 ` Clément Pit--Claudel
2016-12-04 20:41 ` Eli Zaretskii
2016-12-04 22:14 ` Clément Pit--Claudel
2016-12-05 3:30 ` Eli Zaretskii [this message]
2016-12-05 6:02 ` Lisp-friendly backtraces [was: Lispy backtraces] Clément Pit--Claudel
2016-12-05 13:20 ` Stefan Monnier
2016-12-05 14:14 ` Clément Pit--Claudel
2016-12-05 14:37 ` Stefan Monnier
2016-12-05 16:31 ` Clément Pit--Claudel
2016-12-05 16:54 ` Eli Zaretskii
2016-12-05 16:23 ` Eli Zaretskii
2016-12-05 18:59 ` Clément Pit--Claudel
2016-12-06 18:55 ` Eli Zaretskii
2016-12-07 8:27 ` Clément Pit--Claudel
2016-12-12 22:42 ` Clément Pit--Claudel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838trvkq72.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=clement.pit@gmail.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).