From: Philipp <philipp.kupferschmied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Use pause within bullet list
Date: Thu, 3 Sep 2020 06:49:48 -0700 (PDT) [thread overview]
Message-ID: <7d2c6f37-f4c6-4488-873b-c3073e5e5280n@googlegroups.com> (raw)
In-Reply-To: <m2r1rlv5s4.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2128 bytes --]
Thank you for your help - that's a much easier way to create an incremental
list compared to inserting pauses after every item.
However, this solution unfortunately isn't suited for my problem, because
I don't want the entire list to be incremental, but need pauses only at
certain points (sorry for not having made this clearer in my original
question).
I guess I have to keep using . . . where needed and live with the wider
spacing.
John MacFarlane schrieb am Dienstag, 1. September 2020 um 18:08:46 UTC+2:
>
> Try putting the bullet list inside a block quote.
>
> > * A
> > * B
> > * C
>
> That should make the list incremental.
>
>
> Philipp <philipp.ku...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > Hi,
> > I want to generate LaTeX beamer slides from Pandoc markdown. I use
> pauses
> > (. . .) relatively often, but recently noticed that using a pause within
> a
> > bullet list seems to change spacing between list items.
> > If I use
> > * Item A
> >
> > . . .
> >
> > * Item B
> > * Item C
> > I get a loose list, if I don't indent the . . ., the spacing between
> item A
> > and item B is bigger than the spacing between item B and item C.
> >
> > Is there a way to uses pauses but preserve a compact list?
> >
> > Thanks in advance,
> > Philipp
> >
> > --
> > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/a7c8641d-b54c-47a0-876e-e8201c0b1a74n%40googlegroups.com
> .
>
--
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/7d2c6f37-f4c6-4488-873b-c3073e5e5280n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3275 bytes --]
prev parent reply other threads:[~2020-09-03 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 14:59 Philipp
[not found] ` <a7c8641d-b54c-47a0-876e-e8201c0b1a74n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-01 16:08 ` John MacFarlane
[not found] ` <m2r1rlv5s4.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-09-03 13:49 ` Philipp [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=7d2c6f37-f4c6-4488-873b-c3073e5e5280n@googlegroups.com \
--to=philipp.kupferschmied-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).