all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Emacs Development <emacs-devel@gnu.org>
Subject: Re: pretty printing frames from *Backtrace*
Date: Mon, 21 Nov 2016 18:31:12 -0500	[thread overview]
Message-ID: <CAM-tV-8kfR+7C1vMmAnA2bXF6LqyMadE5HEwFwPEmjg0BMVjaQ@mail.gmail.com> (raw)
In-Reply-To: <877f80i1sd.fsf@web.de>

On Fri, Nov 18, 2016 at 10:30 PM, Michael Heerdegen
<michael_heerdegen@web.de> wrote:
>
>> I think it would be easier to integrate directly into the debugger, it
>> would probably save the trouble of cumbersome frame counting.
>
> Doesn't the debugger already do frame counting from Lisp - see
> `debugger-frame-number' (AFAICT marking frames for debugger-reentry is
> based on this)?  FWIW I've changed my code to use this function instead
> of reinventing the wheel.

Ah, if you can reuse the debugger's counting that's okay. I still
think this would be better as an integrated feature of the debugger
though. Currently I switch to edebug as soon as I have an idea of
which function to instrument because of how hard it is to read
backtraces, having this feature really looks like a bare minimum to
me, not an addon.



  reply	other threads:[~2016-11-21 23:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-19  3:09 pretty printing frames from *Backtrace* (WAS: Rant on ...) Noam Postavsky
2016-11-19  3:30 ` pretty printing frames from *Backtrace* Michael Heerdegen
2016-11-21 23:31   ` Noam Postavsky [this message]
2016-11-22  0:28     ` Clément Pit--Claudel
2016-11-22 14:22       ` Michael Heerdegen
2016-11-24 23:05         ` Noam Postavsky

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAM-tV-8kfR+7C1vMmAnA2bXF6LqyMadE5HEwFwPEmjg0BMVjaQ@mail.gmail.com \
    --to=npostavs@users.sourceforge.net \
    --cc=emacs-devel@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.