From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>,
Ista Zahn <istazahn@gmail.com>
Subject: Re: Exporting markdown specific string
Date: Mon, 06 Jan 2014 12:30:09 +0100 [thread overview]
Message-ID: <87sit1cpq6.fsf@gmail.com> (raw)
In-Reply-To: <87bnzrvsoe.fsf@bzg.ath.cx> (Bastien's message of "Sun, 05 Jan 2014 07:39:13 +0100")
Hello,
Bastien <bzg@gnu.org> writes:
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>>> #+HTML and the likes are special shortcuts for historical export
>>> backends, we don't plan to add more.
>>
>> What? Every back-end introduces its own specific keyword
>> (#+beamer: #+ascii ...). I just added them (#+md: and #+markdown:) for
>> md back-end.
>
> Ah, my mistake.
>
> (I had a memory of a conversation about #+HTML looked too ad hoc,
> and in my memories you convinced me that we should not add more of
> these keywords. But maybe you didn't convince me then!)
I don't like them much (as they are redundant) so it's well possible we
had this conversation. For some reason they now exist, for the worse or
the better, in every core back-end.
Though, they are not mandatory for new back-ends. Only documentation can
tell if such a keyword exists for a given back-end (which reminds me
that the recently introduced keywords are not documented yet).
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2014-01-06 11:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 15:48 Exporting markdown specific string Ista Zahn
2014-01-04 17:22 ` Bastien
2014-01-04 18:09 ` Charles Berry
2014-01-04 18:21 ` Bastien
2014-01-04 18:40 ` Charles Berry
2014-01-04 18:50 ` Ista Zahn
2014-01-04 18:24 ` Charles Berry
2014-01-04 19:24 ` Nicolas Goaziou
2014-01-04 20:55 ` Charles Berry
2014-01-04 23:50 ` Nicolas Goaziou
2014-01-05 6:39 ` Bastien
2014-01-06 11:30 ` 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=87sit1cpq6.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=istazahn@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).