From mboxrd@z Thu Jan  1 00:00:00 1970
From: Carlos Pita <carlosjosepita@gmail.com>
Subject: Re: Bug: Add option to fontify latex blocks [9.1.9
 (release_9.1.9-65-g5e4542 @
 /home/carlos/local/stow/emacs-26/share/emacs/26.1.50/lisp/org/)]
Date: Wed, 28 Nov 2018 15:38:39 -0300
Message-ID: <CAELgYhdrFy2W_BdYOH9TUvawsVy1JY=wgHUsu4AZ8xnmkGTLvA@mail.gmail.com>
References: <87h8g2kv81.fsf@gmail.com>
	<CAELgYhe0jQTb7At0BaHGOOuRVYBeDpmgpCkX8OfdZT9KVOBwvQ@mail.gmail.com>
	<87lg5ershk.fsf@nicolasgoaziou.fr>
	<CAELgYhcDvkvur0LYh0aKn4AsSf9zWzX9PJ_Jc=8GQAiOYu-KmA@mail.gmail.com>
	<87d0qpsc4g.fsf@nicolasgoaziou.fr>
	<CAELgYhdQSNgiOuE4OCebm8u8bB-8s_4VOcE3JbEA7q4t_ksaPw@mail.gmail.com>
	<CAELgYhe+nWvo7MQEEjHsm+vXqT_dCo6jOeVqyMafjTvfEcYT1A@mail.gmail.com>
	<CAELgYhcf_gZdj_z5ixjxwEHupE+C+F5Ktj_a73sXY=G42R9YzQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:40988)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <carlosjosepita@gmail.com>) id 1gS4ji-0000Vn-NM
	for emacs-orgmode@gnu.org; Wed, 28 Nov 2018 13:38:59 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <carlosjosepita@gmail.com>) id 1gS4jg-0002qQ-S6
	for emacs-orgmode@gnu.org; Wed, 28 Nov 2018 13:38:58 -0500
Received: from mail-yb1-xb35.google.com ([2607:f8b0:4864:20::b35]:46978)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <carlosjosepita@gmail.com>)
	id 1gS4jf-0002ej-0Q
	for emacs-orgmode@gnu.org; Wed, 28 Nov 2018 13:38:55 -0500
Received: by mail-yb1-xb35.google.com with SMTP id i17-v6so11025687ybp.13
	for <emacs-orgmode@gnu.org>; Wed, 28 Nov 2018 10:38:54 -0800 (PST)
In-Reply-To: <CAELgYhcf_gZdj_z5ixjxwEHupE+C+F5Ktj_a73sXY=G42R9YzQ@mail.gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: emacs-orgmode@gnu.org

Well, now I do have found a bug ;). It's related to the limit issue I
mentioned before. Indeed the problem with rehighlighting broken
environments and highlighting new environments also happens for basic
latex fontification when org-highlight-latex-and-related is set to
'(latex), it has nothing to do with my modification in order to call
org-src-font-lock-fontify-block. It seems that once you break the
multiline structure (for example, by putting a space between "be" and
"gin") org mode syntax highlighter is unable to identify it again once
recomposed. More generally, it's unable to identify environments
entered after the initial loading of the file into the buffer, being
them slight "repairments" of previously existing ones or just brand
new environments. Of course, systematically ignoring the search bound
is not the right solution. I think some kind of region extension
function is missing here.