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: Sat, 11 Jan 2014 12:35:13 +0100	[thread overview]
Message-ID: <86mwj2g39q.fsf@somewhere.org> (raw)
In-Reply-To: 87y52m7st7.fsf@gmail.com

Nicolas Goaziou wrote:
>> Oh, maybe I see.  You want highlighting in #+BEGIN_LaTeX
>> and #+BEGIN_HTML.
>> Actually it makes sense.
>> So that #+BEGIN_HTML would really be short for #+BEGIN_SRC html-mode
>> but with no need for header vars and all the plumbing.
>> Nicolas, what do you think?
> I don't think it's a good idea.
> #+begin_html is /very/ different from #+begin_src html-mode. The former
> is raw html code that will be inserted in the output upon exporting. The
> latter is handled by Babel and is not an export-only feature (more often
> than not, it will not appear in the export output). Fontifying both the
> same way could introduce confusion between them.
> Additionally, some export back-ends allow multiple export block names
> (e.g. #+begin_markdown and #+begin_md), which could add to the
> confusion. And export one-liners, e.g. "#+HTML:" would probably need to
> be also fontified since they really are a shorthand for
> "#+begin_html...#+end_html". Too much trouble, IMO.
>> Would it be okay to enable syntax highlighting in #+BEGIN_{HTML,...}
>> blocks?
> It is possible to get syntax highlighting with C-c ' on such blocks.
> FWIW, I think this is enough.

FWIW, I think this would be great. As soon as we have to type real
HTML/LaTeX or whatever code inside the Org document, it's a great
addition to see the code we type with correct syntax highlighting. That
helps preventing errors, and allows quicker and easier understanding of
what the code does.

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

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

Best regards,

Sebastien Vauban

  reply	other threads:[~2014-01-11 11:35 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 [this message]
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=86mwj2g39q.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).