emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Julien Cubizolles <j.cubizolles@free.fr>
To: emacs-orgmode@gnu.org
Subject: Re: no fontification of #+BEGIN_LaTeX blocks
Date: Mon, 16 Sep 2013 23:26:48 +0200	[thread overview]
Message-ID: <87r4co790n.fsf@free.fr> (raw)
In-Reply-To: 868uywpp4q.fsf@somewhere.org

"Sebastien Vauban" <sva-news@mygooglest.com>
writes:


> No, you could just have the same color as the default (unfontified) from
> source blocks. I mean: fontified source blocks add extra text properties, such
> as "comment", "string", "type", etc.
>
> You could have the same default one, with the same background color, if that's
> what annoys you.

No, that's not the background color that bothers me.

> But I'm not really sure to understand what you try to achieve. Could
>you be
> more explicit?  Could you give a minimal example file?


In the following, begin, center, and braces get different colors
#+BEGIN_SRC latex
 \begin{center}
    \includegraphics[width=0.5\textwidth]{figures/fresnel}
  \end{center}
#+END_SRC

Here everything is the same color, not very good for readability.
#+BEGIN_LaTeX
  \begin{center}
    \includegraphics[width=0.5\textwidth]{figures/fresnel}
  \end{center}
#+END_LaTeX

Since I use them for pieces of code to be exported to Beamer, the latex
block is easier to use (no export options to take care of) but less
readable. Anyway I can edit both with org-edit-src-code, with
fontification, and I'm happy with that so far.

Julien.

  reply	other threads:[~2013-09-16 21:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-14 15:57 no fontification of #+BEGIN_LaTeX blocks Julien Cubizolles
2013-09-15 19:28 ` Sebastien Vauban
2013-09-16 16:53   ` Julien Cubizolles
2013-09-16 19:01     ` Sebastien Vauban
2013-09-16 21:26       ` Julien Cubizolles [this message]
2013-09-17  7:03         ` Sebastien Vauban
2013-09-17  7:15           ` Julien Cubizolles
2013-09-16 15:05 ` Bastien
2013-09-16 21:07   ` Julien Cubizolles

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=87r4co790n.fsf@free.fr \
    --to=j.cubizolles@free.fr \
    --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).