public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: <kperry-rhKcP+tiLR7by3iVrkZq2A@public.gmane.org>
To: <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: RE: listAttributes not working
Date: Tue, 21 Feb 2023 14:41:05 -0500	[thread overview]
Message-ID: <001401d9462c$70b47400$521d5c00$@blinksoft.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]

 

Ok I figured it out.  I can't find this anywhere and the sample.lua doesn't
show it.  I first tried changing the orderedList function to:

 

Function orderedList(items,listAttributes)

 

I did that as a guess.  Then it errored and told me listAttributes was a
number. When I tried to log it as an attribute list. .  I then guess that
the number would be the start.  So I changed the function to:

Function orderedList (items,start,style)

 

Then I was able to use the start and style.  

 

So if anyone else is trying to figure this out and finding the documents
very lacking The above function definition correctly gets the items, start
value, and style.  Maybe the sample.lua should be changed.

 

Ken

 

 

-- 
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/001401d9462c%2470b47400%24521d5c00%24%40blinksoft.com.

[-- Attachment #2: Type: text/html, Size: 3354 bytes --]

             reply	other threads:[~2023-02-21 19:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 19:41 kperry-rhKcP+tiLR7by3iVrkZq2A [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-21 19:21 kperry-rhKcP+tiLR7by3iVrkZq2A

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='001401d9462c$70b47400$521d5c00$@blinksoft.com' \
    --to=kperry-rhkcp+tilr7by3ivrkzq2a@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).