From: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: lists in notes doesn't work
Date: Sat, 12 Oct 2019 10:23:07 +0200 [thread overview]
Message-ID: <CADAJKhAzHAT-xi_kQb6hRdEBz57rsLktPt-idkQaYvin1QZdzw@mail.gmail.com> (raw)
In-Reply-To: <f7d1dd93-0769-4ae6-35f2-40e072f9a375-S0/GAf8tV78@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2343 bytes --]
Also if your output format is LaTeX things will probably look better if you
wrap the text of any footnotes containing lists, tables or code blocks in a
minipage:
````markdown
[^fancy_note]: `\begin{minipage}{0.8\textwidth}`{=latex}
* List
```code
a = b
```
More
`\end{minipage}`{=latex}
````
To make writing easier and to make output more uniform you may want to use
a Lua filter to "automatically" wrap the text of all footnotes in such a
minipage:
````lua
local before_note = pandoc.RawBlock('latex',
'\\begin{minipage}{0.8\textwidth}')
local after_note = pandoc.RawBlock('latex', '\\end{minipage}')
function Note (note)
-- arg #2 is position to insert before
table.insert(note.content, 1, before_note)
-- no position == append at end
table.insert(note.content, after_note)
return note
end
````
Den lör 12 okt. 2019 09:12Pablo Rodríguez <oinos-S0/GAf8tV78@public.gmane.org> skrev:
> On 10/12/19 12:20 AM, Marc Chantreux wrote:
> > hello people,
> >
> > this exemple doesn't work ^[because
> >
> > * footnotes doesn't allow empty line
> > * empty line is a way to start a list
> >
> > ]
>
> Hi Marc,
>
> here you have the difference:
>
> This^[One--line footnote]
>
> That[^multiple-lines]
>
> [^multiple-lines]: here you can have
>
> * lists
>
> And other paragraphs as well.
>
> I hope it helps,
>
> Pablo
> --
> http://www.ousia.tk
>
> --
> 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/f7d1dd93-0769-4ae6-35f2-40e072f9a375%40web.de
> .
>
--
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/CADAJKhAzHAT-xi_kQb6hRdEBz57rsLktPt-idkQaYvin1QZdzw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 4122 bytes --]
prev parent reply other threads:[~2019-10-12 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 22:20 Marc Chantreux
[not found] ` <20191011222032.GA32393-AWr1gsF+PRs9Vg2ZJzWmxBLO4URiXwcH@public.gmane.org>
2019-10-12 7:12 ` Pablo Rodríguez
[not found] ` <f7d1dd93-0769-4ae6-35f2-40e072f9a375-S0/GAf8tV78@public.gmane.org>
2019-10-12 8:23 ` BPJ [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=CADAJKhAzHAT-xi_kQb6hRdEBz57rsLktPt-idkQaYvin1QZdzw@mail.gmail.com \
--to=melroch-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).