From: Eric Ludlam <eric@siege-engine.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-devel@gnu.org
Subject: Re: eieio, pretty printing, and edebug
Date: Tue, 28 Oct 2014 22:38:23 -0400 [thread overview]
Message-ID: <5450531F.1060601@siege-engine.com> (raw)
In-Reply-To: <jwvwq7kup5l.fsf-monnier+emacs@gnu.org>
On 10/28/2014 12:44 PM, Stefan Monnier wrote:
>> Line 895 in eieio.el, were it not commented out, would fix this by
>> having edebug print using the object-print generic, not prin1. I eval'ed
>> the line and tried it, and it seemed to work fine.
>
>> How come it's currently commented out? Can I open a bug for this?
>
> `defalias' is clearly not right, since it hijacks the function. But if
> we change it to advice-add, I think it'd be OK to enable this
> edebug help.
>
> I think it would also be good to add hooks to the native printing system
> so that such tweaks can be done more reliably. Ideally, these same
> hooks could be used for things like desktop and savehist to replace
> markers or other "non-printable" objects with alternative output.
Hi,
Related to debugging EIEIO classes, the `data-debug.el' extension which
is a part of Emacs includes a nice way to browse large data structures.
In it, data-debug-eval-expression is something I've bound to M-: for
myself. It shows the short version of the eval'd expression when it is
short, and goes into a browser type buffer when it is particularly large.
Eric
next prev parent reply other threads:[~2014-10-29 2:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 18:22 eieio, pretty printing, and edebug Eric Abrahamsen
2014-10-28 16:44 ` Stefan Monnier
2014-10-29 2:38 ` Eric Ludlam [this message]
2014-10-29 23:40 ` Eric Abrahamsen
2014-10-30 1:57 ` Stefan Monnier
2014-10-30 2:36 ` Eric Abrahamsen
2014-10-30 2:34 ` Stefan Monnier
2014-10-30 2:50 ` Eric Abrahamsen
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=5450531F.1060601@siege-engine.com \
--to=eric@siege-engine.com \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=monnier@iro.umontreal.ca \
/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.