From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: feature request: best practices for speaker notes and incremental lists/elements
Date: Sat, 24 Oct 2015 13:54:12 +0200 [thread overview]
Message-ID: <87h9lgcwij.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87ziz8zdyh.fsf@gmx.us> (rasmus@gmx.us's message of "Sat, 24 Oct 2015 13:46:30 +0200")
Hello,
Rasmus <rasmus@gmx.us> writes:
> Matt Price <moptop99@gmail.com> writes:
>
>> I think the two exporters should use the same syntax! I especially think
>> that any future exporters should use a single, unified syntax, and that
>> the older exporters should eventualyl be changed to support that new
>> syntax. And finally, I think the new syntax should be as simple as
>> humanly possible. So I'd like to suggest that the community decide on
>> the best way forward.
>
> We can try to make a common syntax across our exporter, namely ox-desk,
> ox-beamer and ox-s5 to the extend that these support "speaker notes". A
> "pull request" can then be made to ox-reveal.el, which AFAIK is neither
> part of lisp or contrib/lisp.
Note that "common syntax" probably means less features (i.e., we are
limited to common features).
As suggested, I think, it seems better to create a generic export
back-end from scratch, which would allow to select a target (e.g.,
beamer, reveal.js...), than altering current back-ends and enter
backward-compatibility's hell.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2015-10-24 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 0:56 feature request: best practices for speaker notes and incremental lists/elements Matt Price
2015-10-24 11:46 ` Rasmus
2015-10-24 11:54 ` Nicolas Goaziou [this message]
2015-10-24 12:16 ` Matt Price
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=87h9lgcwij.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).