From: Matt Price <moptop99@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: standardizing slideshow outpout, a la pandoc
Date: Tue, 22 Sep 2015 16:26:50 -0400 [thread overview]
Message-ID: <CAN_Dec_WixF5b6mD8uueY2OLL_n_k=8CY32wi6Vo+FSZ8_i9jg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1667 bytes --]
Hi everyone,
I'm co-teaching a class this term and my co-instructor is a markdown user,
so I am getting to know a little bit about pandoc. One feature I really
love is the unified slideshow export:
http://pandoc.org/demo/example19/Producing-slide-shows-with-Pandoc.html
All the export filters use the same syntax for slide divisions, slide
"builds" (dynamic appearance of slide contents), and sub-slides (reveal.js
creates two-dimensional slideshows), as well as for speaker notes. The use
of standard markdown features also makes the writing process very
convenient.
By contrast, some of these features can be a little confusing in Org, and
moving from one export format to another can take a certain amount of
work. If I want a "build" to work properly in both deck.js and reveal.js,
for instance, I need both a properties drawer and an #+ATTR_HTML line. In
pandoc I need neither.
Does anyone else think it would be worthwhile to standardize some of these
features within org itself -- either by adding new syntax/options, or by
interpreting existing syntax in a uniform way across export filters? The
first option is less invasive, I think, while the second option would be
slightly more convenient going forward (for new users at least). Pandoc
chooses the second option -- new slides are indicated by a horizontal rule,
for instance.
If other people like the idea I would be willing to draw up a more complete
proposal and write some preliminary code for the export back-ends I'm
familiar with. I am unfortunately a slow coder though, so a positive
resolution would still be a ways away.
Looking forward to hearing what you all think.
Thanks!
Matt
[-- Attachment #2: Type: text/html, Size: 2079 bytes --]
reply other threads:[~2015-09-22 20:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN_Dec_WixF5b6mD8uueY2OLL_n_k=8CY32wi6Vo+FSZ8_i9jg@mail.gmail.com' \
--to=moptop99@gmail.com \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).