From: Matt Price <moptop99@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: feature request: best practices for speaker notes and incremental lists/elements
Date: Sat, 24 Oct 2015 08:16:37 -0400 [thread overview]
Message-ID: <CAN_Dec8DL-pq9TcMmGw_soMrJEQ+VeFnNOFcnnAafmCCi3X-Yg@mail.gmail.com> (raw)
In-Reply-To: <87h9lgcwij.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]
On Sat, Oct 24, 2015 at 7:54 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> 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).
>
Yes, certainly -- there would doubtless still be a need for some
backend-specific hacks, just not as many as we currently have.
>
> 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.
>
That does sound like a good idea. Can I ask, what syntactical structures
seem best to you?
> Regards,
>
> --
> Nicolas Goaziou
>
>
[-- Attachment #2: Type: text/html, Size: 2422 bytes --]
prev parent reply other threads:[~2015-10-24 12:16 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
2015-10-24 12:16 ` Matt Price [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=CAN_Dec8DL-pq9TcMmGw_soMrJEQ+VeFnNOFcnnAafmCCi3X-Yg@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.