From: Drew Adams <drew.adams@oracle.com>
To: Marcin Borkowski <mbork@wmi.amu.edu.pl>, help-gnu-emacs@gnu.org
Subject: RE: Inspecting functions returning complicated values
Date: Tue, 30 Sep 2014 17:46:01 -0700 (PDT) [thread overview]
Message-ID: <109c53cd-7e86-4153-b2cc-21261bd9dadc@default> (raw)
In-Reply-To: <87lhp0hd9m.fsf@wmi.amu.edu.pl>
> assume that I want to inspect a function whose return value is a
> long, deeply nested list. I found this way to present it in a
> readable way:
>
> M-: (setq blah-blah (function-returning-hairy-stuff))
> C-h C-v blah-blah
>
> This seems a bit awkward, however. Is there a better/cleaner way?
M-x pp-eval-expression
next prev parent reply other threads:[~2014-10-01 0:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 23:58 Inspecting functions returning complicated values Marcin Borkowski
2014-10-01 0:46 ` Drew Adams [this message]
2014-10-01 1:59 ` Eric Abrahamsen
[not found] ` <mailman.10126.1412124387.1147.help-gnu-emacs@gnu.org>
2014-10-02 0:35 ` Emanuel Berg
2014-10-02 3:06 ` Drew Adams
[not found] <mailman.10124.1412121528.1147.help-gnu-emacs@gnu.org>
2014-10-01 0:36 ` Emanuel Berg
2014-10-01 14:43 ` Pascal J. Bourguignon
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=109c53cd-7e86-4153-b2cc-21261bd9dadc@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mbork@wmi.amu.edu.pl \
/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.
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).