emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: s j <jsj.register@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: Kai von Fintel <geek@fintel.mailworks.org>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Embedded LaTeX fontification
Date: Sat, 10 Sep 2016 03:17:31 +0000	[thread overview]
Message-ID: <1wnmhk9c0qeur87tkc7r7jbka-0@mailer.nylas.com> (raw)
In-Reply-To: <87h99p2hxh.fsf@delle7240.chemeng.ucl.ac.uk>

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

I am using the org-plus-contrib package in org ELPA.

  

The export block

  

#+begin_export latex

...

#+end_export

  

does not work properly.

It produces

  

\begin{export}

...

\end{export}

  

in the .tex file and causes error.

  

Instead, I still need to use

  

#+begin_latex

...

#+end_latex

.

  

Is the version in org EPLA an out-dated one?

  

Jiang

  

  
On Sep 9 2016, at 12:23 pm, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:  

> On Friday, 9 Sep 2016 at 12:06, Kai von Fintel wrote:  
> When I embed LaTeX code in a #+BEGIN_SRC latex block and  
> org-src-fontify-natively is set to t, the code is fontified as LaTeX  
> code. But when the code is embedded in a #+BEGIN_LaTeX block, there's  
> no fontification. Is that as intended? Am I missing some setting? Or  
> could that functionality be added?

>

> What version of org are you using? In latest versions, begin_latex is  
now  
#+begin_export latex  
...  
#+end_export  
and this does fontify correctly for me.

>

> \--  
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.90.1, Org release_8.3.3-535-g7213aa


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

  parent reply	other threads:[~2016-09-10  3:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e7d95743181c4e59ba6e775ad3124659@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-09-09 15:48 ` Embedded LaTeX fontification Eric S Fraga
2016-09-09 16:44   ` Kai von Fintel
2016-09-10  3:17   ` s j [this message]
2016-09-10  3:40     ` Nick Dokos
2016-09-10  6:50       ` s j
2016-09-09 12:06 Kai von Fintel
2016-09-09 15:42 ` Charles C. Berry

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=1wnmhk9c0qeur87tkc7r7jbka-0@mailer.nylas.com \
    --to=jsj.register@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=geek@fintel.mailworks.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).