Re: When is a syntax-propertize-function called when parse-sexp-lookup-properties is t for a current buffer?

[Emanuel Berg]

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>> || 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