From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier via Users list for the GNU Emacs text editor Newsgroups: gmane.emacs.help Subject: Re: When is a syntax-propertize-function called when parse-sexp-lookup-properties is t for a current buffer? Date: Tue, 05 Oct 2021 21:55:23 -0400 Message-ID: References: Reply-To: Stefan Monnier Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23288"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Cancel-Lock: sha1:N6bedTzmn1fPooy+R5Ej0j9P/TM= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Wed Oct 06 03:56:13 2021 Return-path: Envelope-to: geh-help-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 1mXwAG-0005vX-Bj for geh-help-gnu-emacs@m.gmane-mx.org; Wed, 06 Oct 2021 03:56:12 +0200 Original-Received: from localhost ([::1]:56010 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mXwAF-0004tv-BT for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 05 Oct 2021 21:56:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53702) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mXw9c-0004tn-Qw for help-gnu-emacs@gnu.org; Tue, 05 Oct 2021 21:55:32 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:52102) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mXw9b-0000SS-3d for help-gnu-emacs@gnu.org; Tue, 05 Oct 2021 21:55:32 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1mXw9Y-000530-EY for help-gnu-emacs@gnu.org; Wed, 06 Oct 2021 03:55:28 +0200 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=geh-help-gnu-emacs@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:133592 Archived-At: > 1 -> (my-syntax-propertize 980 1555) > 1 <- my-syntax-propertize: nil > ====================================================================== > 1 -> (my-syntax-propertize 980 1556) > 1 <- my-syntax-propertize: nil > ====================================================================== > 1 -> (my-syntax-propertize 1043 1616) > 1 <- my-syntax-propertize: nil > ====================================================================== > 1 -> (my-syntax-propertize 1043 1617) > 1 <- my-syntax-propertize: nil So, IIUC even though the function is called, the relevant char doesn't get the corresponding `syntax-table` text property? Maybe the major-mode is getting in the way? You can try to use: (defun my-syntax-propertize (beg end) (funcall (syntax-propertize-rules ("\\(<\\)<" (1 (progn (message "OPEN at %S" (match-beginning 1)) (string-to-syntax "(>"))))) (">\\(>\\)" (1 (progn (message "CLOSE at %S" (match-beginning 1)) (string-to-syntax "(>"))))) beg end)) Then check your *Messages* buffer to see where the function placed the property, then look at these positions (e.g. with `C-u C-x =`) to see if the `syntax-table` text property is still present. If the property is absent (i.e. has been removed after your function added it), then you may want to check your `syntax-propertize-function` and search for `syntax-table` in erlong-mode's code to see what might be interfering (e.g. maybe this property is added to `font-lock-extra-properties`?). Stefan