public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Leonard Rosenthol
	<leonardr-bM6h3K5UM15l57MIdRCFDg@public.gmane.org>,
	pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Debugging and/or logging/println() a Writer?
Date: Wed, 12 Aug 2020 17:22:55 -0700	[thread overview]
Message-ID: <m2eeobfl7k.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <CALu=v3JuXzR7LpFdKLyhQvvUeuCh_SrPF6Lw0+QsYNDuvauY3g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


You can use Debug.Trace.

I often just import this module and put a traceShowId around
a value I'm interested in.

Leonard Rosenthol <leonardr-bM6h3K5UM15l57MIdRCFDg@public.gmane.org> writes:

> As I continue to work on native writers in Pandoc, the one big thing I am
> missing is a form of logging or source debugging.
>
> What does everyone else working on the core app (in Haskell) use??
>
> Thanks,
> Leonard
>
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CALu%3Dv3JuXzR7LpFdKLyhQvvUeuCh_SrPF6Lw0%2BQsYNDuvauY3g%40mail.gmail.com.


      parent reply	other threads:[~2020-08-13  0:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-12 18:21 Leonard Rosenthol
     [not found] ` <CALu=v3JuXzR7LpFdKLyhQvvUeuCh_SrPF6Lw0+QsYNDuvauY3g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-08-13  0:22   ` John MacFarlane [this message]

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=m2eeobfl7k.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=leonardr-bM6h3K5UM15l57MIdRCFDg@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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 NNTP newsgroup(s).