From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Improving representation of EIEIO objects in backtraces/error messages
Date: Thu, 29 Dec 2016 11:02:47 -0800 [thread overview]
Message-ID: <87ful6o8x4.fsf@ericabrahamsen.net> (raw)
I can't be the first one to be bitten by this...
When developing using EIEIO objects, backtraces and edebug messages can
be very difficult to use. In edebug, if you're lucky, you get the
#<object-class I'm an object> representation, but if you're unlucky, you
get the vector. In backtraces, you always get the vector.
For large objects, or those involving recursive data structures, this
makes error reporting frustrating, to put it delicately. It can take the
printer a good couple seconds to barf up the representation of an
object, and when it does it makes a huge mess of the minibuffer and/or
*Message* buffer.
I've defined `object-print' methods for some classes, and would dearly
love it if those methods could be used everywhere, even in simple
`eval-expression' situations. Or if there were at least an option that
would allow me to turn this behavior on and off.
Can I open a bug report?
Eric
next reply other threads:[~2016-12-29 19:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 19:02 Eric Abrahamsen [this message]
2016-12-29 20:32 ` Improving representation of EIEIO objects in backtraces/error messages Eli Zaretskii
2016-12-29 20:54 ` Eric Abrahamsen
2016-12-30 7:45 ` Eli Zaretskii
2016-12-31 19:48 ` Eric Ludlam
2016-12-31 20:48 ` Eric Abrahamsen
2017-01-08 1:51 ` Eric Ludlam
2017-01-08 17:24 ` Eric Abrahamsen
2017-01-12 0:47 ` Eric Ludlam
2017-01-12 1:36 ` Eric Abrahamsen
2017-01-12 1:47 ` 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
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=87ful6o8x4.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).