emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [poll] Fontify code in code blocks
Date: Thu, 09 Jan 2014 14:01:51 +0100	[thread overview]
Message-ID: <87wqi9ia0w.fsf@gmail.com> (raw)
In-Reply-To: <86sisxz6ns.fsf@somewhere.org> (Sebastien Vauban's message of "Thu, 09 Jan 2014 13:22:31 +0100")

Le   jeu.   09   janv.   2014    à   01:22:31   ,   "Sebastien   Vauban"
<sva-news@mygooglest.com> a envoyé ce message:
> Hello,
> Currently, to get "code highlighting" (which is contextual to the
> language of the code block) enabled within your Org buffers, you need to
> add the following line to your Emacs config file:
>   (setq org-src-fontify-natively t)
> as the default value of `org-src-fontify-natively' is `nil'.
> WDYT if we turn it on by default?
> Are there users explicitly wanting to keep that variable turned off. If
> yes, can you explain why: performance reasons, others?
> Best regards,
>   Seb


I must  add that  the highlighting  works only  in code  with begin_src-
... end_src à la org. But then,  at least in my configuration, it blocks
the export in LaTeX or in HTML. 

I have not succeeded to get the same highlighting of the latex syntax at
the moment in an org file with all the correct export functions. 

But in comparison of the advantages of org-mode, it is a very small problem. 

Best wishes,


  parent reply	other threads:[~2014-01-09 13:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 12:22 [poll] Fontify code in code blocks Sebastien Vauban
2014-01-09 12:56 ` Thierry Banel
2014-01-09 13:01 ` Joseph Vidal-Rosset [this message]
2014-01-11  9:25   ` Bastien
2014-01-11  9:48     ` Nicolas Goaziou
2014-01-11 11:35       ` Sebastien Vauban
2014-01-14 20:50         ` Bastien
2014-01-15  9:05           ` Sebastien Vauban
2014-01-09 17:10 ` Rick Frankel
2014-01-09 23:16 ` Alexander Baier
2014-01-13 16:33 ` Eric S Fraga
2014-01-13 20:26   ` Sebastien Vauban
2014-01-14 20:47     ` Bastien
2014-01-15 10:31       ` Carsten Dominik
2014-01-16  0:12         ` Bastien

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:

  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=87wqi9ia0w.fsf@gmail.com \
    --to=joseph.vidal.rosset@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sva-news@mygooglest.com \


* 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


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).