all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Drew Adams <drew.adams@oracle.com>,
	Emacs Development <emacs-devel@gnu.org>
Subject: Re: Rant on ...
Date: Fri, 18 Nov 2016 03:17:58 +0100	[thread overview]
Message-ID: <87d1htjzu1.fsf@web.de> (raw)
In-Reply-To: <m3vavlbv07.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 17 Nov 2016 23:29:28 +0100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Yes, that would be very nice.  And a command to expand the `...' under
> point.  If we had those commands, I think we'd cover most of the
> complaints and confusion tied to the *print-le* variables.

FWIW, I chose this different solution for my init file: when I hit a
certain key at any line in the debugger buffer, I get a popup window
that shows the according (clicked) frame as pretty printed lisp
expression in emacs-lisp-mode.  Having a separate buffer has its
advantages, since this expression can be really huge.  The tricky part
is to get the correct frame number to pass to `backtrace-frame'.

Another command pops up a buffer containing the whole backtrace as a
list of lisp expressions.  I chose to bind print-circle -> t for this,
because the frames can share large structures.  With print-circle ->
nil, the individual frame are better readable, but the whole thing gets
even huger.


Michael.



  reply	other threads:[~2016-11-18  2:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 20:47 Rant on Alan Mackenzie
2016-11-17 20:54 ` Lars Ingebrigtsen
2016-11-17 21:04   ` Clément Pit--Claudel
2016-11-17 21:09   ` Lars Ingebrigtsen
2016-11-17 21:20     ` Clément Pit--Claudel
2016-11-17 21:31     ` Drew Adams
2016-11-17 21:33       ` Drew Adams
2016-11-17 22:29       ` Lars Ingebrigtsen
2016-11-18  2:17         ` Michael Heerdegen [this message]
2016-11-18  2:56           ` Drew Adams
2016-11-18  3:27             ` Noam Postavsky
2016-11-18  3:50               ` Drew Adams
2016-11-19  0:10               ` Michael Heerdegen
2016-11-18  2:25         ` 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

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

  git send-email \
    --in-reply-to=87d1htjzu1.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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 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.