From: Andrew Dunning <andunning-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: reveal.js users: Lost reveal.js fragment IDs in address bar
Date: Sat, 11 Feb 2017 15:09:08 -0800 (PST) [thread overview]
Message-ID: <850eb87f-a683-492e-8490-457726f6dae9@googlegroups.com> (raw)
In-Reply-To: <b7b9edb5-345c-4b30-b135-a99c1642325a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 188 bytes --]
This sounds to me a recent change in the reveal.js defaults, since it's been awhile since we overhauled the template. Might be worth investigating and filing an issue on their repository.
next prev parent reply other threads:[~2017-02-11 23:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 16:13 Joseph Reagle
[not found] ` <e7f95a02-0de4-8d66-6275-cee3aac11f68-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2017-02-09 20:06 ` John MacFarlane
[not found] ` <20170209200547.GB18015-l/d5Ua9yGnz4dOG0aB8Qgv8+0UxHXcjY@public.gmane.org>
2017-02-11 14:15 ` Joseph
[not found] ` <b7b9edb5-345c-4b30-b135-a99c1642325a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-02-11 23:09 ` Andrew Dunning [this message]
[not found] ` <850eb87f-a683-492e-8490-457726f6dae9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-02-20 21:27 ` John MacFarlane
[not found] ` <20170220212736.GA4306-l/d5Ua9yGnxXsXJlQylH7w@public.gmane.org>
2017-02-21 0:36 ` Joseph Reagle
[not found] ` <ce371313-c70a-1f76-3a5b-2ab68475c848-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2017-02-22 14:06 ` John MacFarlane
[not found] ` <20170222140642.GH32046-BKjuZOBx5Kn2N3qrpRCZGbhGAdq7xJNKhPhL2mjWHbk@public.gmane.org>
2017-02-22 14:12 ` Joseph Reagle
[not found] ` <c8fda815-0c24-6352-c783-52017281edec-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2017-02-22 15:15 ` BP Jonsson
2017-02-10 8:29 ` Joost Kremers
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=850eb87f-a683-492e-8490-457726f6dae9@googlegroups.com \
--to=andunning-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).