From: Robert Pluim <rpluim@gmail.com>
To: Wolfgang Pausch <wolfgang.pausch@iteg.at>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Entering backtrace buffer if displayed information is huge
Date: Tue, 08 Oct 2019 14:13:18 +0200 [thread overview]
Message-ID: <m236g3a10h.fsf@gmail.com> (raw)
In-Reply-To: <f4741947-2bcf-e985-8fd3-69ed7a7604a3@iteg.at> (Wolfgang Pausch's message of "Mon, 7 Oct 2019 17:29:54 +0300")
>>>>> On Mon, 7 Oct 2019 17:29:54 +0300, Wolfgang Pausch <wolfgang.pausch@iteg.at> said:
Wolfgang> Hello,
Wolfgang> I'm implementing some lisp code based on js2-mode. The nodes of the
Wolfgang> abstract syntax tree of that mode frequently need to be passed between
Wolfgang> defuns.
Wolfgang> My problem is that the Backtrace buffer tries to display the huge
Wolfgang> contents of that nodes, and this makes entering the Backtrace buffer
Wolfgang> extremely slow, and sometimes impossible at all.
Wolfgang> (and once opened, each editor move within the Backtrace buffer can
Wolfgang> cause emacs to freeze for an additional time)
Wolfgang> What's a senseful way to debug in such situations? Basically, if the
Wolfgang> contents of the variables passed to a defun are too huge to be
Wolfgang> displayed in a efficient manner, at least the names of the functions
Wolfgang> being called would be a help while debugging --- is it somehow
Wolfgang> possible to restrict opening a Backtrace buffer to such more basic
Wolfgang> information?
Wolfgang> Currently, I have the situation that debugging trivial programming
Wolfgang> problems costs way too much time...
Wolfgang> Thanks for all hints,
Does setting 'print-length' to something sensible help?
Robert
next prev parent reply other threads:[~2019-10-08 12:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 14:29 Entering backtrace buffer if displayed information is huge Wolfgang Pausch
2019-10-08 12:13 ` Robert Pluim [this message]
2019-10-08 12:25 ` Wolfgang Pausch
2019-10-08 12:52 ` Michael Heerdegen
2019-10-08 17:55 ` Stefan Monnier
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=m236g3a10h.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=wolfgang.pausch@iteg.at \
/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.