Carsten, I'll look into it when I get a chance, even though I doubt
I'll be able to fix it if you describe it as tricky yourself ;)
Any pointers on where to start looking though ?
Cheers
On Fri, Sep 3, 2010 at 7:56 PM, Carsten Dominik
wrote:
>
> On Sep 3, 2010, at 5:23 PM, Dan Davison wrote:
>
On Sep 3, 2010, at 5:23 PM, Dan Davison wrote:
Julien Fantin writes:
I tried opening the file with a bare emacs and the problem persists.
I use true indentation in my files, which I think isn't what most
people do, so maybe the parser gets confused by a combination of
blocks not starting at
I'm sorry if I implied that this issue appeared since your changes
Dan, as it's not the case indeed.
I tried un-indenting the scr block headers, and the problem goes away,
so I'd say it's definitely related to the handling of indented
headers.
I looked at that commit and the regexps do take care
Julien Fantin writes:
> I tried opening the file with a bare emacs and the problem persists.
>
> I use true indentation in my files, which I think isn't what most
> people do, so maybe the parser gets confused by a combination of
> blocks not starting at column 0, and some other formatting, but I
Hi Dan,
thanks for the answer and the unsollicited tip :)
I tried opening the file with a bare emacs and the problem persists.
I use true indentation in my files, which I think isn't what most
people do, so maybe the parser gets confused by a combination of
blocks not starting at column 0, and so
Julien Fantin writes:
> First congratulations on adding in-line fontification to source
> blocks, that's a great addition.
>
> However, since I pulled those changes, a recurring issue I've been
> having has become even more annoying.
>
> When opening an org file, some src blocks headers don't see
