emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Shiyuan <gshy2014@gmail.com>
To: emacs-orgmode@gnu.org
Subject: LaTex best practice in org-mode
Date: Sat, 21 Jun 2014 23:12:49 -0700	[thread overview]
Message-ID: <CAOm4EMvcCMvdHe=tFg7qM9L71cZBgSzO9jo7xVG5Wd5WTxPzRw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]

Hi all,
Hi all,
   We can write LaTex directly in org-mode without put it in a SRC block.
When the code is exported, the latex syntax will be handled correctly to
html or pdf. That's very nice part of org mode. However, if we don't put
the latex code into a SRC block, the latex syntax is not correctly
highlighted (in the code attached below, the first equation is not
highlighted). Another benefit of putting the latex code into SRC block is
that we can easily switch to the latex mode to edit the code snippet using
C-c ' and in the latex mode, we can use some full-fleged latex package like
auctex. However, the latex code in the SRC block is ignored when exported
to html. For example, when I exported the following to html, the first
equation shows up in the html but the second seconed does not.  Any way to
make the html exporter to generated the second equation too without taking
away the BEGIN_SRC/END_SRC? What's the best practice to write latex in
org-mode. Thanks.

\begin{equation}
    \label{eq:test}
    Bx=b
\end{equation}

#+BEGIN_SRC latex

  \begin{equation}
    \label{eq:test}
    Ax=b
  \end{equation}
#+END_SRC

[-- Attachment #2: Type: text/html, Size: 1383 bytes --]

             reply	other threads:[~2014-06-22  6:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-22  6:12 Shiyuan [this message]
2014-06-22  8:20 ` LaTex best practice in org-mode Thorsten Jolitz
2014-06-24  6:02   ` Shiyuan
2014-06-24  8:52     ` Thorsten Jolitz

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='CAOm4EMvcCMvdHe=tFg7qM9L71cZBgSzO9jo7xVG5Wd5WTxPzRw@mail.gmail.com' \
    --to=gshy2014@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).