From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Alan Mackenzie <acm@muc.de>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: edebug: regrettable loss of information in Emacs 26.1 when printing a variable's value.
Date: Mon, 21 May 2018 17:20:08 -0400 [thread overview]
Message-ID: <CAM-tV-_u+CeMEvFGCqyNy0jwS16+o8h7p6aBSeqLw8J4=1x=tA@mail.gmail.com> (raw)
In-Reply-To: <83sh6keu9n.fsf@gnu.org>
On 21 May 2018 at 14:30, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Noam Postavsky <npostavs@gmail.com>
>> Date: Mon, 21 May 2018 13:47:53 -0400
>> Cc: Emacs developers <emacs-devel@gnu.org>
>>
>> > So, can I get edebug to print out the contents of a variable containing
>> > a function? If so how?
>>
>> (fset 'edebug-prin1-to-string #'prin1-to-string) ; gives Emacs 25 behaviour
Alternatively (setq cl-print-readably t) has the same (though it
affects non-edebug usage of cl-print as well).
>>
>> Or
>>
>> (setq cl-print-compiled 'static) ; shows constants array, but not bytecode
>
> It's IMO not nice to have this customizable on such a low level, let
> alone in a different package. I think we will need Edebug defcustom's
> for tailoring this behavior. (And given the terse output of the
> current default in this case, I wonder why we changed the default
> behavior from what it was in Emacs 25.)
I think it was due to overly verbose output for EIEIO objects (e.g., Bug#25295).
> Maybe it's too late to introduce defcustom's before 26.1 is released,
> but in any case, this should be called out in NEWS. Could you please
> add an entry about this?
Yup, done.
[1: d65430f6cb]: 2018-05-21 17:11:29 -0400
* etc/NEWS: Mention change in `edebug-prin1-to-string'.
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=d65430f6cb48d009c28cc27c5171f6fc82c79663
next prev parent reply other threads:[~2018-05-21 21:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 17:10 edebug: regrettable loss of information in Emacs 26.1 when printing a variable's value Alan Mackenzie
2018-05-21 17:47 ` Noam Postavsky
2018-05-21 18:23 ` Alan Mackenzie
2018-05-21 18:30 ` Eli Zaretskii
2018-05-21 21:20 ` Noam Postavsky [this message]
2018-05-22 16:53 ` Eli Zaretskii
2018-05-21 17:58 ` Eli Zaretskii
2018-05-21 19:04 ` Alan Mackenzie
2018-05-21 18:05 ` Stefan Monnier
2018-05-21 21:24 ` Noam Postavsky
2018-05-22 0:52 ` Stefan Monnier
2018-05-23 17:28 ` Stefan Monnier
2018-05-23 16:03 ` Message's text-properties in *Messages* (was: edebug: regrettable loss of information in Emacs 26.1 when printing a variable's value) Stefan Monnier
2018-05-23 16:10 ` Drew Adams
2018-05-23 16:46 ` Message's text-properties in *Messages* Stefan Monnier
2018-05-26 0:48 ` John Wiegley
2018-05-26 15:52 ` Stefan Monnier
2018-05-26 19:50 ` Amin Bandali
2018-05-27 14:36 ` John Wiegley
2018-05-27 21:28 ` Amin Bandali
2018-05-23 17:22 ` Message's text-properties in *Messages* (was: edebug: regrettable loss of information in Emacs 26.1 when printing a variable's value) Eli Zaretskii
2018-05-23 17:41 ` Message's text-properties in *Messages* Stefan Monnier
2018-05-23 18:07 ` Eli Zaretskii
2018-05-30 17:19 ` Eli Zaretskii
2018-05-30 19:44 ` Stefan Monnier
2018-05-30 19:55 ` Eli Zaretskii
2018-05-31 2:09 ` Stefan Monnier
2018-05-31 2:40 ` Eli Zaretskii
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-_u+CeMEvFGCqyNy0jwS16+o8h7p6aBSeqLw8J4=1x=tA@mail.gmail.com' \
--to=npostavs@gmail.com \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--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 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.