From: tsd@tsdye.com (Thomas S. Dye)
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [RFC] Make QUOTE an export keyword instead of an element type
Date: Sun, 26 Jan 2014 05:41:08 -1000 [thread overview]
Message-ID: <m161p6lpij.fsf@tsdye.com> (raw)
In-Reply-To: <87zjmiyhfd.fsf@gmail.com> (Nicolas Goaziou's message of "Sun, 26 Jan 2014 14:57:26 +0100")
Aloha Nicolas,
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> At the moment, they are parsed specially by Org Elements, but I think it
> is a mistake. Like "COMMENT" keyword in headlines, "QUOTE" is more an
> instruction for the export framework. Therefore, they should be parsed
> as regular sections, and treated specially during export. The following
> patches permit it, in 3 steps:
>
> 1. Remove special parsing from "org-element.el",
> 2. Turn section contents into a big example block.
> 3. Remove quote section translators from export back-ends (contrib
> directory handled separately)
>
> This change implies that any quote-section translator and filter is
> ignored (but it will not generate an error if present). It also means
> that an export back-end cannot tell the difference between an example
> block and a quote section.
>
> Since quote sections were treated as example blocks (except in
> ox-ascii.el), the export behaviour will remain unchanged (except in
> ox-ascii.el).
>
> Alternatives:
>
> - Treat their contents as `quote-blocks' instead of `example-block'
> - Remove them altogether, since they don't bring anything new.
I didn't know about this undocumented feature. Since it doesn't bring
anything new, I'm fine with removing it altogether.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2014-01-26 15:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 13:57 [RFC] Make QUOTE an export keyword instead of an element type Nicolas Goaziou
2014-01-26 15:41 ` Thomas S. Dye [this message]
2014-01-26 16:58 ` Rasmus
2014-01-26 21:07 ` Nick Dokos
2014-01-26 21:42 ` Samuel Wales
2014-01-26 22:03 ` Bastien
2014-01-26 23:42 ` Nick Dokos
2014-01-27 1:29 ` Rasmus
2014-01-27 10:06 ` Sebastien Vauban
2014-01-27 10:20 ` Thorsten Jolitz
2014-01-27 5:46 ` Carsten Dominik
2014-01-27 11:12 ` Nicolas Goaziou
2014-01-27 11:21 ` Bastien
2014-01-27 20:45 ` Nicolas Goaziou
2014-01-28 8:52 ` Bastien
2014-01-31 15:44 ` Bastien
2014-02-01 13:24 ` Nicolas Goaziou
2014-02-01 22:43 ` Bastien
2014-02-02 21:40 ` Nicolas Goaziou
2014-02-02 22:20 ` Bastien
2014-02-03 11:20 ` Nicolas Goaziou
2014-02-03 14:59 ` Bastien
2014-02-03 15:08 ` Nicolas Goaziou
2014-02-03 15:36 ` Bastien
2014-02-03 15:45 ` Nicolas Goaziou
2014-02-03 22:41 ` Nicolas Goaziou
2014-02-05 10:12 ` Bastien
2014-02-06 17:56 ` Nicolas Goaziou
2014-02-06 22:00 ` Bastien
2014-02-07 8:51 ` Nicolas Goaziou
2014-02-07 9:10 ` Bastien
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=m161p6lpij.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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).