Hello,
Kaushal Modi writes:
> Out of curiosity, which org-mode version will see this change in
> export-block syntax?
Org 9.0. See ORG-NEWS in development branch.
Regards,
--
Nicolas Goaziou
Out of curiosity, which org-mode version will see this change in
export-block syntax?
> I removed all of them but the last one.
Of course :)
Thanks.
Kaushal Modi writes:
> I agged the org-mode git repo for ":export-block" and found these
> references:
>
> contrib/lisp/ox-gfm.el
> 54: :export-block '("GFM" "GITHUB FLAVORED MARKDOWN")
>
> (Copied Lars for above)
>
> contrib/lisp/ox-freemind.el
> 46: :export-block "FREEMIND"
>
> (Copied Jambun
Thanks Nicolas.
I agged the org-mode git repo for ":export-block" and found these
references:
contrib/lisp/ox-gfm.el
54: :export-block '("GFM" "GITHUB FLAVORED MARKDOWN")
(Copied Lars for above)
contrib/lisp/ox-freemind.el
46: :export-block "FREEMIND"
(Copied Jambunathan for above)
(And cop
Hello,
Kaushal Modi writes:
> I believe this change is breaking the ox-twbs package.
>
> The error shown is:
>
> Debugger entered--Lisp error: (error "Unknown keyword: :export-block")
[...]
> The error goes away after I comment out the line with :export-block keyword
> in the org-export-define
Hi all,
I believe this change is breaking the ox-twbs package.
The error shown is:
Debugger entered--Lisp error: (error "Unknown keyword: :export-block")
signal(error ("Unknown keyword: :export-block"))
error("Unknown keyword: %s" :export-block)
org-export-define-backend(twbs ((bold . org-
On Sat, Jan 02, 2016 at 11:54:42AM +0100, Nicolas Goaziou wrote:
> Hello,
>
> Suvayu Ali writes:
>
>
> > On Sun, Dec 20, 2015 at 10:06:44PM +0100, Nicolas Goaziou wrote:
> >>
> >> I just finalized the syntax change for export blocks. As a reminder, the
> >> new syntax is:
> >>
> >> #+BEGIN_
Hello,
Suvayu Ali writes:
> On Sun, Dec 20, 2015 at 10:06:44PM +0100, Nicolas Goaziou wrote:
>>
>> I just finalized the syntax change for export blocks. As a reminder, the
>> new syntax is:
>>
>> #+BEGIN_EXPORT backend
>> ...
>> #+END_EXPORT
>>
>> instead of
>>
>> #+BEGIN_backend
>>
On Sat, Jan 2, 2016 at 1:54 AM, Suvayu Ali wrote:
> Hi,
>
> On Sun, Dec 20, 2015 at 10:06:44PM +0100, Nicolas Goaziou wrote:
>>
>> I just finalized the syntax change for export blocks. As a reminder, the
>> new syntax is:
>>
>> #+BEGIN_EXPORT backend
>> ...
>> #+END_EXPORT
>>
>> instead of
>
Hi,
On Sun, Dec 20, 2015 at 10:06:44PM +0100, Nicolas Goaziou wrote:
>
> I just finalized the syntax change for export blocks. As a reminder, the
> new syntax is:
>
> #+BEGIN_EXPORT backend
> ...
> #+END_EXPORT
>
> instead of
>
> #+BEGIN_backend
> ...
> #+END_backend
This seems to
Hello,
Ken Mankoff writes:
> Does this new syntax support that oft (or occasionally?) requested
> LaTeX header export?
This syntax doesn't introduce any new feature.
> I don't think so out of the box, because while LaTeX is a valid export word,
> LaTeX_preamble is not.
>
> But, can the new sy
Does this new syntax support that oft (or occasionally?) requested LaTeX header
export?
I don't think so out of the box, because while LaTeX is a valid export word,
LaTeX_preamble is not.
But, can the new syntax be used like this?
\include{preamble}
#+BEGIN_EXPORT LaTeX :file preamble
Hello,
Rasmus writes:
> Will org-lint be able to detect and repair documents automatically?
`org-lint' detects it already, but it doesn't repair anything, hence the
additional function in ORG-NEWS.
Regards,
--
Nicolas Goaziou
Hi,
Nicolas Goaziou writes:
Thanks for the work.
> The following function, included in ORG-NEWS, updates any Org document
> to the new syntax. It is meant to be applied after applying the patch.
Will org-lint be able to detect and repair documents automatically?
Rasmus
--
Spil noget med Sla
Hello,
I just finalized the syntax change for export blocks. As a reminder, the
new syntax is:
#+BEGIN_EXPORT backend
...
#+END_EXPORT
instead of
#+BEGIN_backend
...
#+END_backend
So, basically, "export" is a reserved block type, much like "src". As
a consequence, INCLUDE keywords
16 matches
Mail list logo
