public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Paul Kelleher <paul-JZTKsBFbLNkkm2bSNb+QWw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Beamer slide numbering
Date: Fri, 23 Sep 2022 15:05:16 -0700 (PDT)	[thread overview]
Message-ID: <dd0131f3-943d-4713-9277-f8e9b33a4602n@googlegroups.com> (raw)
In-Reply-To: <eec3d9ff-b1a6-4a64-a27c-02823275dfe8n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


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

Also, it'd be great if I could start the numbering on the second slide 
(since the first slide is the title slide). Thanks!

On Friday, September 23, 2022 at 2:59:28 PM UTC-5 Paul Kelleher wrote:

> I've just started using Pandoc to convert markdown to slides with Beamer. 
> Upon compile, the pdf of the slides lacks any slide numbers. Is there an 
> easy way to an output that has each slide numbered sequentially?

-- 
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/dd0131f3-943d-4713-9277-f8e9b33a4602n%40googlegroups.com.

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

  parent reply	other threads:[~2022-09-23 22:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 19:59 Paul Kelleher
     [not found] ` <eec3d9ff-b1a6-4a64-a27c-02823275dfe8n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-09-23 22:05   ` Paul Kelleher [this message]
     [not found]     ` <dd0131f3-943d-4713-9277-f8e9b33a4602n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-09-24  5:03       ` Paul Kelleher

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=dd0131f3-943d-4713-9277-f8e9b33a4602n@googlegroups.com \
    --to=paul-jztksbfblnkkm2bsnb+qww@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).