Re: [PATCH] Interpret #r"..." as a raw string

[Alan Mackenzie]

Hello, Dmitry.

On Tue, Mar 02, 2021 at 16:32:45 +0200, Dmitry Gutov wrote:
> On 02.03.2021 16:14, Alan Mackenzie wrote:
> >> Both are supported by ruby-mode with syntax-propertize-function without
> >> too much trouble.
> > I've just tried this out, looking up some ruby syntax on Wikipedia.
> > Adapting its example, start out with this in ruby-mode:

> > #########################################################################
> > a = <<-BLOCK

> > This is a double-quoted string
> > BLCK
> > BLOCK
> > b
> > #########################################################################

> > Now everything down to and including the second BLOCK has string face.
> > This seems correct.  Delete the O from the first BLOCK, so that the
> > string is now terminated by BLCK.  The second BLOCK still has string
> > face, although it is no longer in the string.  Is this a bug?

> Would be a bug, but I can't exactly reproduce it.

Sorry, my mistake.  On my terminal, string face and type face are both
green.  Hence the confusion.

> I delete the O, then wait 2 seconds (because of 
> jit-lock-antiblink-grace, I guess?), and the second block gets fontified 
> with font-lock-type-face.

> Set jit-lock-antiblink-grace to nil to make this happen faster. Still 
> dependent on jit-lock-context-time, though.

-- 
Alan Mackenzie (Nuremberg, Germany).