emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [bug] [babel] fontification of source code blocks lost if using #+header(s)
Date: Fri, 01 Jul 2011 13:12:37 -0700	[thread overview]
Message-ID: <87ei29lpx5.fsf@gmail.com> (raw)
In-Reply-To: 878vsim4vj.fsf@ucl.ac.uk

Hi Eric,

Thanks for pointing this out, I've just pushed up a patch which should
fix this fontificaiton.  Please let me know if something is not working.

Best -- Eric

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> Hello again,
> For source code blocks with long header lines, org allows the use of
> the #+header: or #+headers: alternative for specifying these.  Attached
> is an example.  
> The problem is that using these seems to cause fontification to stop
> working and, unfortunately in a non-reproducible manner, also causes
> some problems with C-c' working for allowing me to edit the code in a
> code specific mode.  Fontification works just fine if the header
> arguments are on the #+begin_src line, however.
> thanks,
> eric

Eric Schulte

  reply	other threads:[~2011-07-01 20:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01 14:50 [bug] [babel] fontification of source code blocks lost if using #+header(s) Eric S Fraga
2011-07-01 20:12 ` Eric Schulte [this message]
2011-07-03 18:09   ` Eric S Fraga

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=87ei29lpx5.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.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).