From: Munyoki Kilyungi <me@bonfacemunyoki.com>
To: <guile-user@gnu.org>
Subject: Pretty Printing values from a hashmap
Date: Thu, 21 Jul 2022 12:13:52 +0300 [thread overview]
Message-ID: <86sfmuvne7.fsf@bonfacemunyoki.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
Hi! Say I have a hashmap that has nested hashmaps
that I want to inspect. Is there a way to just
printing it out on my display in a
straight-forward way without having to loop inside
the key-value pairs? Printing a hashmap outputs
something like this:
--8<---------------cut here---------------start------------->8---
#<hash-table 7f56164e9340 2/31>
--8<---------------cut here---------------end--------------->8---
--
(Life is like a pencil that will surely run out,
but will leave the beautiful writing of life.)
(D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
(hkp://keys.gnupg.net))
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 865 bytes --]
next reply other threads:[~2022-07-21 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 9:13 Munyoki Kilyungi [this message]
2022-07-21 10:14 ` Pretty Printing values from a hashmap Munyoki Kilyungi
2022-07-21 11:28 ` adriano
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86sfmuvne7.fsf@bonfacemunyoki.com \
--to=me@bonfacemunyoki.com \
--cc=guile-user@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.
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).