public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Aaron Leonard <aj.leonard8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: typst writer
Date: Fri, 9 Jun 2023 22:39:32 -0700 (PDT)	[thread overview]
Message-ID: <7696e6b2-40ee-4f75-a487-a3853db56edbn@googlegroups.com> (raw)
In-Reply-To: <8634f40f-135b-4b6c-8b95-810d4506c351n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1646 bytes --]

note that im running this on my terminal and followed the basic pandoc 
intstructions to convert a rtf to latex file as an example

On Saturday, June 10, 2023 at 1:37:05 AM UTC-4 Aaron Leonard wrote:

> hello everyone, im having trouble setting up the typst writer on pandoc. 
> note im a new user so its likely my issue is extremely simple and an easy 
> fix (fingers crossed!)
>
> I downloaded this: https://github.com/lvignoli/typst-pandoc
>
> when I run the command "pandoc -t writer.lua input.tex -o output.typ" for 
> my relevant files I was getting the error that no file or directory is 
> found. 
>
> I changed the path to ~/writer.lua but now am getting the error :
>
> Error running Lua:
>
> No render function for Inline value 'Note';
>
> define a function `Writer.Inline.Note` that returns a string or Doc.
>
> stack traceback:
>
> ~/writer.lua:75: in function 'pandoc.scaffolding.Writer.Block.Para'
>
> [C]: in function 'pandoc.scaffolding.Writer.Blocks'
>
> [C]: in function 'pandoc.scaffolding.Writer.Pandoc'
>
> while rendering Block `Para`
>
> while rendering Blocks
>
> while rendering Pandoc
>
> stack traceback:
>
>
> Is anyone able to help with this? thanks !!!
>

-- 
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/7696e6b2-40ee-4f75-a487-a3853db56edbn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 5615 bytes --]

  parent reply	other threads:[~2023-06-10  5:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-10  5:37 Aaron Leonard
     [not found] ` <8634f40f-135b-4b6c-8b95-810d4506c351n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-10  5:39   ` Aaron Leonard [this message]
     [not found]     ` <7696e6b2-40ee-4f75-a487-a3853db56edbn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-10  5:47       ` Aaron Leonard
     [not found]         ` <0bc1003d-c941-431f-a742-930e92ec0d30n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-10  5:50           ` Aaron Leonard
2023-06-10 15:18   ` John MacFarlane
  -- strict thread matches above, loose matches on Subject: below --
2023-03-31 23:45 Typst writer Norman Lorrain

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=7696e6b2-40ee-4f75-a487-a3853db56edbn@googlegroups.com \
    --to=aj.leonard8-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).