From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carlos Pita 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: Tue, 1 Jan 2019 14:11:55 -0300 Message-ID: References: <87h8g2kv81.fsf@gmail.com> <87lg5ershk.fsf@nicolasgoaziou.fr> <87d0qpsc4g.fsf@nicolasgoaziou.fr> <87woo5xkgf.fsf@nicolasgoaziou.fr> <87k1k2ynsh.fsf@nicolasgoaziou.fr> <87a7kkz5p9.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000026da01057e68a18b" Return-path: Received: from eggs.gnu.org ([208.118.235.92]:59096) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1geNaZ-0000HH-Ky for emacs-orgmode@gnu.org; Tue, 01 Jan 2019 12:12:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1geNaV-0001ch-QZ for emacs-orgmode@gnu.org; Tue, 01 Jan 2019 12:12:23 -0500 Received: from mail-yw1-xc32.google.com ([2607:f8b0:4864:20::c32]:38269) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1geNaR-0001Us-9e for emacs-orgmode@gnu.org; Tue, 01 Jan 2019 12:12:16 -0500 Received: by mail-yw1-xc32.google.com with SMTP id d190so10202623ywb.5 for ; Tue, 01 Jan 2019 09:12:09 -0800 (PST) In-Reply-To: <87a7kkz5p9.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org --00000000000026da01057e68a18b Content-Type: text/plain; charset="UTF-8" > > > I'd > rather see work to integrate fontification with the parser. > I could take a look at this sometime in the next few months but I'm not sure what do you mean. In particular: 1. Is the parser doing partial parsings of every inserted/removed character or line in a more or less complete syntactical environment around the insertion/removal? 2. If the parser identifies a block how is it in a better position to flag it as outdated regarding fontification? Do you mean completely circumventing the search based font lock mechanism with its multiline property and region extensions? That is, directly setting face related properties and forcing a refresh of the region? > Meanwhile, I applied your patch in master. I also added a commit > message. > Thanks, Nicolas! Best regards -- Carlos --00000000000026da01057e68a18b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

I'd
rather see work to integrate fontification with the parser.

I could take a look at= this sometime in the next few months but I'm not sure what do you mean= . In particular:

1. Is t= he parser doing partial parsings of every inserted/removed character or lin= e in a more or less complete syntactical environment around the insertion/r= emoval?

2. If the parser= identifies a block how is it in a better position to flag it as outdated r= egarding fontification? Do you mean completely circumventing the search bas= ed font lock mechanism with its multiline property and region extensions? T= hat is, directly setting face related properties and forcing a refresh of t= he region?


Meanwhile, I applied your patch in master. I also added a commit
message.

Thanks, Nicolas!
=

Best regards
--
Carlos
--00000000000026da01057e68a18b--