Re: [O] Need to update documentation to reflect export block syntax

[Mark Edgington]

Kaushal Modi  gmail.com> writes: 
>   Mark The online documentation corresponds to the stable releases of
org-mode only.
> The master branch is the dev branch. The only way to access the latest
documentation is via the Info manual (M-x info in emacs to access that is
the best way IMO).

Thanks, I see that now -- I had mistakenly assumed that because the current
stable release date was later than the date of Nicolas' commit, that it had
been included in the release.

Re: [O] Need to update documentation to reflect export block syntax

[Nicolas Goaziou]

Mark Edgington  writes:

> It also might be worthwhile to have org-mode warn users (at least for a
> number of new releases) who happen to be using the old format, explaining
> that they need to use the new one to avoid problems when exporting.

This already done in ORG-NEWS.

Regards,

Re: [O] Need to update documentation to reflect export block syntax

[Kaushal Modi]

@Mark The online documentation corresponds to the stable releases of
org-mode only.

The master branch is the dev branch. The only way to access the latest
documentation is via the Info manual (M-x info in emacs to access that is
the best way IMO).
-- 

-- 
Kaushal Modi

Re: [O] Need to update documentation to reflect export block syntax

[Nicolas Goaziou]

Hello,

Mark Edgington  writes:

> I recently updated my org-mode git repository (for a long time I've
> had an older git version that I was using), and I am now having
> problems when doing latex exports.
>
> I bisected with git to find that the "problem" starts with this revision:
>
> commit 54318add34f09ff39d3fd034a4c1a89f60fd8759
> Author: Nicolas Goaziou 
> Date:   Tue Feb 3 16:16:54 2015 +0100
>
> Change export block syntax
>
> It seems that #+begin_latex is no longer supported, and that when
> using it, it results in escaped latex comment symbols (e.g. \% in the
> tex file instead of just %), as well as \begin{latex} and \end{latex}
> in the exported code.
>
> If it is no longer supported, then it is important that the org-mode
> documentation be updated (see e.g.
> http://orgmode.org/manual/Quoting-LaTeX-code.html ), since those using
> the latest release will have trouble exporting using the old syntax.

Manual is already updated. You are probably looking at an old manual
version.

Regards,

-- 
Nicolas Goaziou

Re: [O] Need to update documentation to reflect export block syntax

[Mark Edgington]

It also might be worthwhile to have org-mode warn users (at least for a
number of new releases) who happen to be using the old format, explaining
that they need to use the new one to avoid problems when exporting.

[O] Need to update documentation to reflect export block syntax

[Mark Edgington]

I recently updated my org-mode git repository (for a long time I've
had an older git version that I was using), and I am now having
problems when doing latex exports.

I bisected with git to find that the "problem" starts with this revision:

commit 54318add34f09ff39d3fd034a4c1a89f60fd8759
Author: Nicolas Goaziou 
Date:   Tue Feb 3 16:16:54 2015 +0100

Change export block syntax

It seems that #+begin_latex is no longer supported, and that when
using it, it results in escaped latex comment symbols (e.g. \% in the
tex file instead of just %), as well as \begin{latex} and \end{latex}
in the exported code.

If it is no longer supported, then it is important that the org-mode
documentation be updated (see e.g.
http://orgmode.org/manual/Quoting-LaTeX-code.html ), since those using
the latest release will have trouble exporting using the old syntax.