From: Christophe Demko <chdemko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: pandoc-latex-environment filter usage problems
Date: Mon, 22 Jul 2019 11:46:09 -0700 (PDT) [thread overview]
Message-ID: <46efe7ed-40e3-458c-8d0c-df8a8439f47a@googlegroups.com> (raw)
In-Reply-To: <9ddf0f15-1c59-4de8-bfca-ed2615e8d7a1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1619 bytes --]
could you post here what this command display:
$ echo $PATH
and if pandoc-latex-environment is in these paths?
Le dimanche 14 juillet 2019 12:44:12 UTC+2, rama prakasha a écrit :
>
> I wanted to use `pandoc-latex-environment
> <https://github.com/chdemko/pandoc-latex-environment/wiki>` but test isnt
> working after istalling it from `pip3 install pandoc-latex-environment`.
> Can somebody help me. These are output after running commands.
>
> *Running: Win 10; Cygwin; Pandoc 2.7.3*
>
> source: `a.md`
>
> ---
>
> pandoc-latex-environment:
> test: [class1, class2]
> ---
>
>
> <div class="class2 class1">content</div>
>
>
> ::: class2
> Content
> :::
>
>
>
> case1:
>
> $: pandoc -f markdown+fenced_divs -t json a.md | pandoc-latex-environment
> | pandoc -f json -t latex
>
> $: content
>
>
> $: Content
>
>
> case2:
>
> $: pandoc a.md -t latex -F pandoc-latex-environment
> Error running filter pandoc-latex-environment:
> Could not find executable pandoc-latex-environment
>
>
>
> What could be the problem?
>
>
> Are there any alternatives for parsing pandoc markdown div markup to latex
> environments. Please Help.
>
>
--
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/46efe7ed-40e3-458c-8d0c-df8a8439f47a%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 6161 bytes --]
next prev parent reply other threads:[~2019-07-22 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-14 10:44 rama prakasha
[not found] ` <9ddf0f15-1c59-4de8-bfca-ed2615e8d7a1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-07-22 18:46 ` Christophe Demko [this message]
[not found] ` <46efe7ed-40e3-458c-8d0c-df8a8439f47a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-11-17 20:21 ` rama prakasha
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=46efe7ed-40e3-458c-8d0c-df8a8439f47a@googlegroups.com \
--to=chdemko-re5jqeeqqe8avxtiumwx3w@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).