>> For syntax highlighting in LaTeX environments you can use
>>
>> (setq org-highlight-latex-and-related '(native))
>
> Ok, thanks, that works nicely. Why isn't that the default?
Ihor, I'm curious to know if the fontification of LaTeX export blocks
suffers from the same performance issues as setting
org-highlight-latex-and-related to '(native).
>> I don't understand how this can be faster if it involves typing more
>> text. Could you explain?
> Now that you have asked me to explain, I realized that I could:
> - define a bunch of abbreviations for the most commonly-used
> environments and save even more typing; or
> - simply type M-x latex-in-b RET al TAB * RET which would cost 17
> keystrokes; or
> - play around with keymaps so that I access the `latex-insert-block'.
>
> So this observation is really about my work-style, and why I prefer to
> use export latex blocks.
`org-cdlatex-mode' provides several ways to quick-insert environments
and LaTeX macros. With this mode enabled, there are many equivalents of
C-c C-e in LaTeX buffers:
- C-c {
- Type in "beg" and press TAB
- Type in "env" and press TAB
> The question about why export latex blocks are not available for preview
> remains.
This requires changes in several places across org-latex-preview.el, but
they can be made available if Ihor thinks they should. To minimize
breaking changes, in the LaTeX preview rewrite we are following the
previous org-latex-preview behavior, which ignores export LaTeX blocks.
Karthik
