From: Fredrik Salomonsson <plattfot@posteo.net>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Debug setup in emacs
Date: Tue, 08 Sep 2020 10:18:16 -0700 [thread overview]
Message-ID: <87a6y0kx0n.fsf@posteo.net> (raw)
In-Reply-To: <c4b46773-2fe1-0f13-343f-b273dfdc3d84@posteo.de>
Hi Zelphir,
Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> writes:
> I usually find myself using (display (simple-format #f "blablabla: ~a\n
> some-binding)) or a custom procedure wrapping it.
You might want to try (simple-format #t "blablabla: ~a\n some-binding)
instead. The #t will send it to the current output port, so it will
do the same as the above. just less to type :).
> At some point it becomes too much and I switch to the REPL and trying
> things in there, if the setup or situation is not too hard to reproduce.
> Also used (pk ...) sometimes, when I am not sure an expression is ever
> evaluated.
Yeah, definetly need to check out the "pk" procedure. Seems quite
useful.
> If this fails me, I sometimes try to think about all the custom
> procedures involved and start writing tests.
>
> If I am too lazy to do that, I find myself thinking about the problem
> real hard and then usually facepalming about my own silly mistakes.
Writing tests + sprinkle (format #t ...) and thinking hard about the
problem is what I've been doing to find all my own silly mistakes.
> If I still don't know what's going on, I might ask on the mailing list
> for help.
Thanks for the input!
--
s/Fred[re]+i[ck]+/Fredrik/g
next prev parent reply other threads:[~2020-09-08 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 23:37 Debug setup in emacs Fredrik Salomonsson
2020-09-05 6:23 ` Joshua Branson via General Guile related discussions
2020-09-05 7:27 ` Jan Nieuwenhuizen
2020-09-05 22:17 ` Fredrik Salomonsson
2020-09-06 5:43 ` Jan Nieuwenhuizen
2020-09-07 19:50 ` Fredrik Salomonsson
2020-09-06 7:19 ` Catonano
2020-09-07 20:01 ` Fredrik Salomonsson
2020-09-08 6:15 ` Catonano
2020-09-08 6:45 ` Zelphir Kaltstahl
2020-09-08 17:18 ` Fredrik Salomonsson [this message]
2020-09-08 17:07 ` Fredrik Salomonsson
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=87a6y0kx0n.fsf@posteo.net \
--to=plattfot@posteo.net \
--cc=guile-user@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/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).