emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [poll] Fontify code in code blocks
Date: Wed, 15 Jan 2014 10:05:03 +0100	[thread overview]
Message-ID: <86iotlboow.fsf@somewhere.org> (raw)
In-Reply-To: 87mwiy1e5e.fsf@bzg.ath.cx

Hello Bastien,

Bastien wrote:
> 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 can share your idea that it's good to see a difference between both
types of code snippets. But, then, instead of _not_ fontifying the code
in question, it'd be better (for example) to provide them with
a different background color (other than the current
`org-block-background', shared by both types of snippets).

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

Ouf ;-)

>> That would be the same for #+HTML/LaTeX one-liners, yes!
> For this I disagree... this would encourage using such
> one-liners too much.

I don't think having highlighting or not encourages one-lines: we need
them (for their purpose) or not, with or without highlighting.

On the contrary, not highlighting one-liners would encourage to convert
them into 3-liners (if we "need" the colors):

... one-line code ...

Not sure to understand why you'd make a distinction.

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

So do I.

Best regards,

Sebastien Vauban

  reply	other threads:[~2014-01-15  9:05 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
2014-01-15  9:05           ` Sebastien Vauban [this message]
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=86iotlboow.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.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).