Re: [O] Exporting markdown specific string

Hello, Bastien b...@gnu.org writes: Nicolas Goaziou n.goaz...@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:

[O] Exporting markdown specific string

Hi all, I'm trying to figure out how to export a line (say foo) only when exporting to markdown. For latex there is '#+LATEX: foo' and for html there is '#+HTML: foo' but neither '#+MD: foo' nor '#+MARKDOWN: foo' does the trick. Of course '#+HTML: foo' exports foo to markdown since the markdown

Re: [O] Exporting markdown specific string

Hi Ista, Ista Zahn istaz...@gmail.com writes: I'm trying to figure out how to export a line (say foo) only when exporting to markdown. #+BEGIN_MD ... #+END_MD will do. #+HTML and the likes are special shortcuts for historical export backends, we don't plan to add more. HTH, -- Bastien

Re: [O] Exporting markdown specific string

Bastien bzg at gnu.org writes: Hi Ista, Ista Zahn istazahn at gmail.com writes: I'm trying to figure out how to export a line (say foo) only when exporting to markdown. #+BEGIN_MD ... #+END_MD will do. [snip] No it won't. ox-md.el does not define a transcoder for keyword

Re: [O] Exporting markdown specific string

Charles Berry ccbe...@ucsd.edu writes: No it won't. ox-md.el does not define a transcoder for keyword and falls back to its parent: Thanks. I just added this transcoder to the master branch. -- Bastien

Re: [O] Exporting markdown specific string

Charles Berry ccberry at ucsd.edu writes: Bastien bzg at gnu.org writes: Hi Ista, Ista Zahn istazahn at gmail.com writes: I'm trying to figure out how to export a line (say foo) only when exporting to markdown. #+BEGIN_MD ... #+END_MD will do. [snip]

Re: [O] Exporting markdown specific string

Bastien bzg at gnu.org writes: Charles Berry ccberry at ucsd.edu writes: No it won't. ox-md.el does not define a transcoder for keyword and falls back to its parent: Thanks. I just added this transcoder to the master branch. Looking at org-md-export-block shouldn't it

Re: [O] Exporting markdown specific string

On Sat, Jan 4, 2014 at 1:40 PM, Charles Berry ccbe...@ucsd.edu wrote: Bastien bzg at gnu.org writes: Charles Berry ccberry at ucsd.edu writes: No it won't. ox-md.el does not define a transcoder for keyword and falls back to its parent: Thanks. I just added this transcoder to the

Re: [O] Exporting markdown specific string

Hello, Bastien b...@gnu.org writes: Ista Zahn istaz...@gmail.com writes: I'm trying to figure out how to export a line (say foo) only when exporting to markdown. #+BEGIN_MD ... #+END_MD will do. I added #+begin_markdown...#+end_markdown too, as defined by the back-end. #+HTML and

Re: [O] Exporting markdown specific string

Nicolas Goaziou n.goaziou at gmail.com writes: Hello, Bastien bzg at gnu.org writes: Ista Zahn istazahn at gmail.com writes: I'm trying to figure out how to export a line (say foo) only when exporting to markdown. #+BEGIN_MD ... #+END_MD will do. I added

Re: [O] Exporting markdown specific string

Hello, Charles Berry ccbe...@ucsd.edu writes: Doesn't org-md-export-block want (org-export-with-backend 'html export-block contents info) at its end? Done. Thank you. Regards, -- Nicolas Goaziou

Re: [O] Exporting markdown specific string

Nicolas Goaziou n.goaz...@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,