From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: emacs rendering comparisson between emacs23 and emacs26.3 Date: Wed, 08 Apr 2020 10:40:19 +0300 Message-ID: <83v9mapgrg.fsf@gnu.org> References: <671b5b41-663d-5ab9-f022-dc6c5ce54dd0@yandex.ru> <83r1x1sqkx.fsf@gnu.org> <83lfn9s63n.fsf@gnu.org> <83h7xvqsgc.fsf@gnu.org> <90749329-ccb1-f96e-29c0-b4ecbb81d1d4@yandex.ru> <837dyrqews.fsf@gnu.org> <20200407201018.GD4009@ACM> <835zeaqz8q.fsf@gnu.org> <20200408070215.GA4106@ACM> <83wo6qpi5s.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="86891"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, emacs-devel@gnu.org, rudalics@gmx.at, rrandresf@gmail.com, Stefan Monnier , dgutov@yandex.ru To: acm@muc.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Apr 08 09:41:03 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jM5KY-000MTb-P2 for ged-emacs-devel@m.gmane-mx.org; Wed, 08 Apr 2020 09:41:02 +0200 Original-Received: from localhost ([::1]:57034 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jM5KX-000090-RI for ged-emacs-devel@m.gmane-mx.org; Wed, 08 Apr 2020 03:41:01 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38899) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jM5K2-0008AP-Oa for emacs-devel@gnu.org; Wed, 08 Apr 2020 03:40:31 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:47725) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jM5K1-0007hA-Nz; Wed, 08 Apr 2020 03:40:29 -0400 Original-Received: from [176.228.60.248] (port=4226 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jM5Js-0006Xv-Bb; Wed, 08 Apr 2020 03:40:20 -0400 In-Reply-To: <83wo6qpi5s.fsf@gnu.org> (message from Eli Zaretskii on Wed, 08 Apr 2020 10:10:07 +0300) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:246643 Archived-At: > Date: Wed, 08 Apr 2020 10:10:07 +0300 > From: Eli Zaretskii > Cc: rudalics@gmx.at, rrandresf@gmail.com, emacs-devel@gnu.org, rms@gnu.org, > dgutov@yandex.ru > > > It's context fontification. I'm quite sure of that, now. To restart > > jit-lock with a new j-l-context-time involves explicitly getting rid of > > a timer and allowing it to restart. > > Then perhaps the solution is to reduce the default value of > jit-lock-context-time? Btw, I cannot wrap my head around this "deferred context fontification" stuff; never could. The doc string of jit-lock-contextually says: If t, means fontification occurs on those lines modified and all subsequent lines. This means those subsequent lines are refontified to reflect their new syntactic context, after `jit-lock-context-time' seconds. If any other value, e.g., `syntax-driven', means syntactically true fontification occurs only if syntactic fontification is performed using the buffer mode's syntax table, i.e., only if `font-lock-keywords-only' is nil. I understand what t means and does, but what does non-nil, non-t value do, and how is it different from t? in particular, does it also wait for jit-lock-context-time of idleness? The doc string of jit-lock-mode also seems to document only the t value: - Deferred context fontification if `jit-lock-contextually' is non-nil. This means fontification updates the buffer corresponding to true syntactic context, after `jit-lock-context-time' seconds of Emacs idle time, while Emacs remains idle. Otherwise, fontification occurs on modified lines only, and subsequent lines can remain fontified corresponding to previous syntactic contexts. This is useful where strings or comments span lines. The code doesn't seem to start the jit-lock-context-timer if the value is non-t, or am I missing something? Since the default value is 'syntax-driven', where does that 0.5-second delay we all see come from? I guess you (Alan) have this figured out, so please share what you've learned, and let's update the documentation to benefit from that. Thanks.