emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Sebastien Vauban
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: [poll] Fontify code in code blocks
Date: Tue, 14 Jan 2014 21:50:37 +0100	[thread overview]
Message-ID: <87mwiy1e5e.fsf@bzg.ath.cx> (raw)
In-Reply-To: <86mwj2g39q.fsf@somewhere.org> (Sebastien Vauban's message of "Sat, 11 Jan 2014 12:35:13 +0100")

When `org-src-fontify-natively' will be `t' by default,
it will be important to keep the distinction between source
blocks and HTML/LaTeX blocks.

So HTML blocks should remain unfontified by default, just
to mark the difference with "active" source blocks.

I still think an option to highlight them would be nice.

> That would be the same for #+HTML/LaTeX one-liners, yes!

For this I disagree... this would encourage using such
one-liners too much.

> Now, I have no idea about what's the work required. But I definitely
> would love to see that implemented.

Well, it's not hard but not straightforward -- and I'd rather
be sure that the decision is to take that route before I try to
implement this.

Waiting to read what other think.


  reply	other threads:[~2014-01-14 20:51 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
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 [this message]
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=87mwiy1e5e.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
    --cc=public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org \


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