From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Emanuel Berg 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:08:02 +0200 Message-ID: <87wnmrxpbh.fsf@zoho.eu> References: <874k9vz8fx.fsf@zoho.eu> Reply-To: Emanuel Berg Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24470"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Cancel-Lock: sha1:cfez7PEKR8Q6ROdleV7aAOAz5Os= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Tue Oct 05 21:10:22 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 1mXppV-00069W-DY for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 05 Oct 2021 21:10:21 +0200 Original-Received: from localhost ([::1]:42420 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mXppS-0002TU-5K for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 05 Oct 2021 15:10:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36668) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mXpnT-0000Qu-N4 for help-gnu-emacs@gnu.org; Tue, 05 Oct 2021 15:08:15 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:35940) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mXpnQ-0005hX-QR for help-gnu-emacs@gnu.org; Tue, 05 Oct 2021 15:08:15 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1mXpnN-0003Rt-Il for help-gnu-emacs@gnu.org; Tue, 05 Oct 2021 21:08:09 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: help-gnu-emacs@gnu.org Mail-Copies-To: never 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:133585 Archived-At: Pierre Rouleau wrote: > I know the following is long, but I think I need to give some context... > > I’m trying to add navigation with forward-sexp and > backward-sexp inside erlang-mode buffers to support the > Erlang Bit Syntax expressions ( > https://erlang.org/doc/reference_manual/expressions.html#bit-syntax-expressions > ). > > Currently, with the latest version of erlang.el, the > erlang-mode activates the ability to move to the >> matching > the << just after point, but *only* after you just write the > Erlang code. > > So let's say you just wrote the following Erlang statement > inside an erlang-mode buffer: > > Abc = << <> || Bin <- [<<3,7,5,4,7>>] >> [...] OK, I get it! Did you read this Only single-character comment start and end sequences are represented thus. Two-character sequences are represented as described below. The second character of NEWENTRY is the matching parenthesis, used only if the first character is ‘(’ or ‘)’. Any additional characters are flags. Defined flags are the characters 1, 2, 3, 4, b, p, and n. 1 means CHAR is the start of a two-char comment start sequence. 2 means CHAR is the second character of such a sequence. 3 means CHAR is the start of a two-char comment end sequence. 4 means CHAR is the second character of such a sequence. in `modify-syntax-entry'? Weird/bad this isn't already in the mode BTW ... -- underground experts united https://dataswamp.org/~incal