From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: KDr2 <killy.draw@gmail.com>
Cc: Bastien Guerry <bzg@gnu.org>, Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [ANN] Merge export-block type within special-block
Date: Sun, 28 Sep 2014 09:26:55 +0200 [thread overview]
Message-ID: <87r3yww6gw.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87r3ywl13l.fsf@gmail.com> (Aaron Ecay's message of "Sun, 28 Sep 2014 02:18:22 -0400")
Hello,
Aaron Ecay <aaronecay@gmail.com> writes:
> I have a hunch that this is backwards. It seems like the convention
> has been to allow arbitrary special blocks in org files. Sticking to
> what I know best, these create arbitrarily-named environments in Latex.
> Export blocks seem like the special case (e.g. the number of types is
> constrained by the available export modules), and so they should have
> to bear special marking.
Historically (i.e. pre-8.0), so-called export blocks were a core
feature, whereas special blocks were defined in an optional library
(IIRC "org-special-blocks.el"). That explains why my proposal was to
optionally activate special blocks and not the other way round.
We can instead use
#+begin_latex :raw t
...
#+end_latex
to optionally activate an export block instead of a special block.
I don't mind either way.
> What if you used the convention that all export blocks had the form
> #+begin_export_latex, #+begin_export_html, etc.? This should be
> unambiguous to parse. (It’s possible to bikeshed about the name, of
> course: perhaps #+begin_literal_latex etc.)
One drawback, however, is that is prevents any special block name from
starting with "export" (or any post-bikeshedding name that could be
issued).
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2014-09-28 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 12:37 [ANN] Merge export-block type within special-block Nicolas Goaziou
2014-07-27 22:13 ` Bastien
2014-08-29 14:02 ` KDr2
2014-08-31 12:56 ` Nicolas Goaziou
2014-09-25 15:12 ` KDr2
2014-09-26 9:09 ` Nicolas Goaziou
2014-09-28 6:18 ` Aaron Ecay
2014-09-28 7:26 ` Nicolas Goaziou [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
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=87r3yww6gw.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=killy.draw@gmail.com \
/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).