From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.bugs Subject: bug#56393: Actually fix the long lines display bug Date: Thu, 07 Jul 2022 08:28:07 +0800 Message-ID: <87k08ppy08.fsf@localhost> References: <38c1a31040d2d2bc47ae@heytings.org> <87a69n98yy.fsf@yahoo.com> <38c1a31040f5546dbd3a@heytings.org> <83a69n90t8.fsf@gnu.org> <38c1a31040ad21b41adc@heytings.org> <835ykb8x3z.fsf@gnu.org> <38c1a310403dbabc7270@heytings.org> <834jzv8sv4.fsf@gnu.org> <38c1a31040ba2976eb4d@heytings.org> <83y1x77c2w.fsf@gnu.org> <87k08rkvgb.fsf@gnus.org> <38c1a31040e94458bd3d@heytings.org> <83o7y277b8.fsf@gnu.org> <762d224809bcab0d6bbc@heytings.org> <83fsje74pz.fsf@gnu.org> <762d224809bc038d2030@heytings.org> <838rp672p7.fsf@gnu.org> <762d224809114fbaf4af@heytings.org> <834jzu6wnu.fsf@gnu.org> <762d224809c7a439895e@heytings.org> <83wncq5dvu.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8198"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Gregory Heytings , larsi@gnus.org, 56393@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Jul 07 02:28:21 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1o9FNV-000230-It for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 07 Jul 2022 02:28:21 +0200 Original-Received: from localhost ([::1]:49430 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o9FNU-0005Xe-9N for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 06 Jul 2022 20:28:20 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57696) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o9FNC-0005X0-Uo for bug-gnu-emacs@gnu.org; Wed, 06 Jul 2022 20:28:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:33235) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o9FNC-0003S8-Ko for bug-gnu-emacs@gnu.org; Wed, 06 Jul 2022 20:28:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1o9FNC-0005iF-BS for bug-gnu-emacs@gnu.org; Wed, 06 Jul 2022 20:28:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Ihor Radchenko Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 07 Jul 2022 00:28:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56393 X-GNU-PR-Package: emacs Original-Received: via spool by 56393-submit@debbugs.gnu.org id=B56393.165715363121900 (code B ref 56393); Thu, 07 Jul 2022 00:28:02 +0000 Original-Received: (at 56393) by debbugs.gnu.org; 7 Jul 2022 00:27:11 +0000 Original-Received: from localhost ([127.0.0.1]:55365 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o9FMN-0005hA-Hx for submit@debbugs.gnu.org; Wed, 06 Jul 2022 20:27:11 -0400 Original-Received: from mail-pg1-f169.google.com ([209.85.215.169]:36541) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o9FMJ-0005gk-M4 for 56393@debbugs.gnu.org; Wed, 06 Jul 2022 20:27:10 -0400 Original-Received: by mail-pg1-f169.google.com with SMTP id s206so15580934pgs.3 for <56393@debbugs.gnu.org>; Wed, 06 Jul 2022 17:27:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=DQqZ9YSVoBCdq+A2B7DDRuNv0eIBIwel/PeqkXBrGJA=; b=ToKcqMwE58KtJlu4tYSJQoidCJByCzIraI6sQ737PDduUVF8N0OMdidaQ5SrwaCwex EUJ4Zi44qyasOpDkWtm2XdHciNfK4cwcNE9aob2uKMQ4PqmNm8h10RJwTAM4GjEkh8FO MAotDhtJO/Jimqt+GyBJzYRQfc0odeaEgHsrXOaMXZps9vTK6bnSaagwq0UXaTcqoOzk AyynTW4SbjNzLDde1Lp0k6aov2AJMKUScZCekXRGidIK7aihpeO/S+R95f0hqMz/HWjU 5aV9mhADNt9gsSWKKN5fycSVk6hYRquulJj0bzuRk8SUR3o0CH8Utsv4DFCIka5ekv8B 8K+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=DQqZ9YSVoBCdq+A2B7DDRuNv0eIBIwel/PeqkXBrGJA=; b=dr9IBR4MRGyfS6R92iJn+Fe4jwH+82KIyIWjxLOhucSdRc9lhruUJLTR6kWn0oQttE JdSsh6C+aYTvoAhe3v994x7LlY95xuGcPuSVbarLEeVqop417Xv3ILMfzjtJ2quTuW/c 4/7gED8Q6fnxfvQkPLS9j7J6qnBXwiwl5/A4EUPs3Pa46OgD1xqewbvsH59bt1+I8Mhr q/hYhzrmqrM6/IawrMDWdSF+6mWudG7ofVrqB4YIlUxODsa/+GU5SyqMywhLdrSKVq8Q qgjCrL8pk72X3ikkhVSuFEJPx9kn+9IST1ZnqFShP1a+JWp6OUgYFPE8J0UjdrMcz08o YP2g== X-Gm-Message-State: AJIora8NKDwywA6iCsuJngaif2/R6jOYILC8STKVr+C4RNSy/xrn9zP3 6iaNhsKDV69anHBNvRGZsLU= X-Google-Smtp-Source: AGRyM1tNq+FVy9e1BXqArydSkeqQNlWfBlbnL6gGcdEz9gj9o15TQueKY6Ei+Ob2PPr9fHZn1R/JBA== X-Received: by 2002:a17:90b:38cd:b0:1ef:b4c2:3624 with SMTP id nn13-20020a17090b38cd00b001efb4c23624mr1697272pjb.168.1657153621662; Wed, 06 Jul 2022 17:27:01 -0700 (PDT) Original-Received: from localhost ([209.95.60.151]) by smtp.gmail.com with ESMTPSA id y7-20020aa78f27000000b00522c0a75c39sm25510054pfr.196.2022.07.06.17.26.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 06 Jul 2022 17:27:00 -0700 (PDT) In-Reply-To: <83wncq5dvu.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:236305 Archived-At: Eli Zaretskii writes: >> Again, I don't know (my understanding of the font-lock machinery is very >> limited). > > Your understanding of font-lock, or your understanding how it is > invoked from the display code? > > I can help with the latter. When Emacs is about to display some chunk > of text, it checks whether the text has a non-nil 'fontified' > property. If it does, that chunk of text was already fontified, but > if not, the display engine calls font-lock (via jit-lock.el) to > fontify the next 1500 characters, and puts a non-nil 'fontified' > property on those 1500 characters. The result is face properties, > which are then actually displayed. Doesn't font-lock extend the region to be fontified to at least the full current line? (see font-lock-extend-region-functions and font-lock-extend-region-wholelines) Best, Ihor