From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Selective font-locking? Date: Sun, 11 Apr 2021 17:10:38 -0400 Message-ID: References: <7A948673-E156-42BA-BA50-E91986908BB5@gmail.com> <65B869A0-CB0B-43C1-90EA-E2B259A74589@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7326"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: JD Smith Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Apr 11 23:12:02 2021 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 1lVhNC-0001pU-Ef for ged-emacs-devel@m.gmane-mx.org; Sun, 11 Apr 2021 23:12:02 +0200 Original-Received: from localhost ([::1]:60954 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lVhNB-0005Dr-GC for ged-emacs-devel@m.gmane-mx.org; Sun, 11 Apr 2021 17:12:01 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41442) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lVhMC-0004m8-4a for emacs-devel@gnu.org; Sun, 11 Apr 2021 17:11:00 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:37517) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lVhM8-0004Df-51 for emacs-devel@gnu.org; Sun, 11 Apr 2021 17:10:59 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 54C1580284; Sun, 11 Apr 2021 17:10:54 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 62E0280853; Sun, 11 Apr 2021 17:10:52 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1618175452; bh=ERM8aqn4vx9lsYiB1AKXqY82drLYeo2/S0HgPZOev6I=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=Y4/etMvwY65aaifCUuT5RWq9TEzLw02BxwyViL4VLjJ21QYAKE1lhAMM6Ma9iErhm JKwnZ9eIVdWwMe93yyQE7xwk8phEwcp4ACKIV3/fY/eJ/LT6Eytn5n0D5rgORcLQid QcQndQSTHG2ujm0RbssCYrt7VLcrtNHm2ruCgQ740YuHQ1ZbxvdFgM84wL0TFHcviX FEtVdeicfg8bk7KaPFw0EW3ZxmmCmOPhAwSPAPbds0Ahr/t94YErNjBGHXonXA8Vmq 34ZppaQxO4PRGbgFg0xLGnVIBzUmxpSxazzbYojqfJ5lxu2Gcc3AeAn7iMKBblpR37 FD6wtyy8VP6RA== Original-Received: from alfajor (104-222-126-84.cpe.teksavvy.com [104.222.126.84]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id EB0481208A6; Sun, 11 Apr 2021 17:10:51 -0400 (EDT) In-Reply-To: <65B869A0-CB0B-43C1-90EA-E2B259A74589@gmail.com> (JD Smith's message of "Sun, 11 Apr 2021 16:54:28 -0400") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:267914 Archived-At: > Python-font-lock-keywords is a variable defined in =E2=80=98python.el=E2= =80=99. > Its value is > (python-font-lock-keywords-level-1 python-font-lock-keywords-level-1 pyth= on-font-lock-keywords-level-2 python-font-lock-keywords-maximum-decoration) > > Not sure why jit-lock-function would be evaluating it like an sexp. `python-font-lock-keywords` does not hold a valid value for use on `font-lock-keywords` but a value to be used as the first element of `font-lock-defaults`. This "first element" is used to initialize `font-lock-keywords` but it depends on things like the `font-lock-maximum-decoration`. Stefan >> On Apr 11, 2021, at 12:31 PM, Stefan Monnier = wrote: >>=20 >>> But then, why bother round-tripping text out to a special-use buffer an= yway, >>> vs. just letting font-lock operate in-situ in the shell buffer itself u= sing >>> python-mode=E2=80=99s fairly simple font-lock-defaults. The only thing = needed to >>> make this work is asking font-lock to ignore all the text with =E2=80= =98field of >>> =E2=80=98output?=20=20 >>=20 >> Maybe you can try something like the following? >>=20 >> (defvar python--font-lock-keywords ...) >> (defvar python-font-lock-keywords >> '(python--apply-font-lock)) >> (defun python--apply-font-lock (limit) >> (while (< (point) limit) >> (let ((next-boundary (find-next-boundary limit))) >> (if (we-should-skip-this-block) >> (goto-char next-boundary) >> (let ((font-lock-keywords python--font-lock-keywords)) >> (font-lock-ensure (point) limit)))))) >>=20 >>=20 >> -- Stefan >>=20