public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Specifying Raw Block Elements
Date: Tue, 10 Oct 2017 20:36:29 -0700	[thread overview]
Message-ID: <20171011033629.GA29983@Johns-MacBook-Pro.local> (raw)
In-Reply-To: <f81758a8-93c5-4d35-bb61-d4255d248339-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Easiest way to install the dev version from source is to
install the Haskell 'stack' tool, then clone the pandoc repository,
cd to it, and

    stack install

You could also try grabbing a binary from

https://github.com/pandoc-extras/pandoc-nightly/releases

+++ Saivan Hamama [Oct 10 17 17:52 ]:
>   Awesome!
>   Are there any instructions anywhere about how to compile the dev
>   version?
>   Sorry John.
>   That is very useful information to me at the moment :)
>   Saivan.
>   On Wednesday, October 11, 2017 at 2:24:01 AM UTC+10, John MacFarlane
>   wrote:
>
>     In the dev version, you can specify raw blocks or inline for
>     a given output format:
>     ```{=html}
>     This is an HTML block.
>     ```
>     And `this is inline HTML`{=html}.
>     +++ Saivan Hamama [Oct 09 17 19:57 ]:
>     >   It seems almost all of the issues I've been wrestling with for
>     the last
>     >   two days are stemming from this problem. Is it possible to have
>     a way
>     >   to specify that we want to pass html verbatim, without having
>     pandoc
>     >   modify it at all? It seems that particular tags have been
>     excluded, but
>     >   having a Block level object that allows us to input html would
>     be a
>     >   godsend!
>     >   Is there some reason why this wouldn't work? Maybe something as
>     simple
>     >   as:
>     >   <<>>
>     >       ... html goes here
>     >   <<>>
>     >   Or even a command line option that allows us to specify which
>     tags we
>     >   don't want pandoc to treat as verbatim blocks?
>     >   Eg, Svg's, myowncanvas above etc (which can be set along with
>     the
>     >   default ones provided in pandoc)
>     >
>     >   --
>     >   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 [1][1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>     >   To post to this group, send email to
>     >   [2][2]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>     >   To view this discussion on the web visit
>     >   [3][3]https://groups.google.com/d/msgid/pandoc-discuss/
>     ae0ccc2e-6c5c-4d64-
>     >   9a0f-33f27b8e028b%[4]40googlegroups.com.
>     >   For more options, visit [4][5]https://groups.google.com/
>     d/optout.
>     >
>     >References
>     >
>     >   1. mailto:[6]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>     >   2. mailto:[7]pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>     >   3. [8]https://groups.google.com/d/msgid/pandoc-discuss/ae0ccc2e-
>     6c5c-4d64-9a0f-33f27b8e028b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=
>     email&utm_source=footer
>     >   4. [9]https://groups.google.com/d/optout
>
>   --
>   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 [10]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [11]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [12]https://groups.google.com/d/msgid/pandoc-discuss/f81758a8-93c5-4d35
>   -bb61-d4255d248339%40googlegroups.com.
>   For more options, visit [13]https://groups.google.com/d/optout.
>
>References
>
>   1. javascript:/
>   2. javascript:/
>   3. https://groups.google.com/d/msgid/pandoc-discuss/ae0ccc2e-6c5c-4d64-
>   4. http://40googlegroups.com/
>   5. https://groups.google.com/d/optout
>   6. javascript:/
>   7. javascript:/
>   8. https://groups.google.com/d/msgid/pandoc-discuss/ae0ccc2e-6c5c-4d64-9a0f-33f27b8e028b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   9. https://groups.google.com/d/optout
>  10. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>  11. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>  12. https://groups.google.com/d/msgid/pandoc-discuss/f81758a8-93c5-4d35-bb61-d4255d248339-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>  13. https://groups.google.com/d/optout


  parent reply	other threads:[~2017-10-11  3:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09  3:58 Saivan Hamama
     [not found] ` <bed5a293-ddf6-4ef6-9e8c-c55f5e4aced2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-10  2:57   ` Saivan Hamama
     [not found]     ` <ae0ccc2e-6c5c-4d64-9a0f-33f27b8e028b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-10 16:24       ` John MACFARLANE
2017-10-11  0:52         ` Saivan Hamama
     [not found]           ` <f81758a8-93c5-4d35-bb61-d4255d248339-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-11  0:53             ` Saivan Hamama
2017-10-11  3:36             ` John MacFarlane [this message]
     [not found]               ` <20171011033629.GA29983-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-10-12  3:58                 ` Saivan Hamama
     [not found]                   ` <ce0b4c71-f89e-48ce-a0f1-d49f4edebbf0-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-12 15:08                     ` John MacFarlane

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=20171011033629.GA29983@Johns-MacBook-Pro.local \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).