From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 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 20:58:27 +0300 [thread overview]
Message-ID: <83vabgevr0.fsf@gnu.org> (raw)
In-Reply-To: <20180521171019.GA5750@ACM> (message from Alan Mackenzie on Mon, 21 May 2018 17:10:19 +0000)
> Date: Mon, 21 May 2018 17:10:19 +0000
> From: Alan Mackenzie <acm@muc.de>
>
> In the upcoming Emacs 26.1, I'm in edebug. In the program I'm
> debugging, there is something nasty in the variable
> `syntax-propertize-function', and I need to find out what.
>
> So I do "e" and type in that variable name.
>
> What comes back is this:
>
> #f(compiled-function (start end) #<bytecode 0x191eb39>)
>
> . This is thoroughly unhelpful. In previous versions of Emacs, this
> would have printed out the function in enough detail to give variable
> names, function names, etc., which could be used to search through the
> Emacs source with.
Did you try setting cl-print-compiled to the value 'disassemble' or
'static'?
next prev parent reply other threads:[~2018-05-21 17:58 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
2018-05-22 16:53 ` Eli Zaretskii
2018-05-21 17:58 ` Eli Zaretskii [this message]
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
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=83vabgevr0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--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).