From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Mark Edgington <edgimar@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Need to update documentation to reflect export block syntax
Date: Thu, 30 Jun 2016 17:14:08 +0200 [thread overview]
Message-ID: <877fd61zgf.fsf@saiph.selenimh> (raw)
In-Reply-To: <CAMsBe8rhw-RNqFLAea3ctsgK2Hf1HvXdKBRTZcqZMDxmveEMVA@mail.gmail.com> (Mark Edgington's message of "Thu, 30 Jun 2016 10:53:36 -0400")
Hello,
Mark Edgington <edgimar@gmail.com> 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 <mail@nicolasgoaziou.fr>
> 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
prev parent reply other threads:[~2016-06-30 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 14:53 Need to update documentation to reflect export block syntax Mark Edgington
2016-06-30 14:58 ` Mark Edgington
2016-06-30 15:14 ` Nicolas Goaziou
2016-06-30 15:21 ` Kaushal Modi
2016-06-30 20:10 ` Mark Edgington
2016-06-30 15:14 ` 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=877fd61zgf.fsf@saiph.selenimh \
--to=mail@nicolasgoaziou.fr \
--cc=edgimar@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).