PR# 19527 [er] EiffelStudio editor lost with verbatim strings in large class text files

It happens often that when we have a verbatim string in a large class text file in the editor, Eiffel Studio is lost: everything which follows this verbatim string is wrongly considered as part of the string (with the same color highlighting), and dropping a feature which is declared below this verbatim string (or clicking on the corresponding name in the Features panel) will not move the cursor to the text of this feature (in fact it does not move the cursor at all if I remember correctly). If I remember correctly, recompiling from scratch does not solve the issue, although I did not check recently.

--
Eric Bezault

Those issues should be fixed by revision rev#103346 and rev#103347 
The correction will be available in next release 19.11 (and beta version 19.07)

Can you add more information about "foo bar %%" 
I tried, and on my side, I don't see any "style" issue.
either with 
var := "foo bar %%" 
or 
print ("foo bar %%" )

I found a similar issue. EiffelStudio's editor gets confused after a string of the form "foo bar %%". Adding a space after the second % (before the closing ") solves the problem, but the string is not what I want.

I found two workarounds:

"foo bar %/25/"
"foo bar" + ('%%').out

I'm happy with neither of them, because they make the code more difficult to read than it was before.
Using a verbatim string would mean 3 lines, which is too verbose.

--
Eric Bezault

It looks like this had nothing to do with the size of the class text.
It is the same issue as reported by Roger Osmond: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/eiffel-users/6cZe_8JVbEg/r5QEXsc2CgAJ
In our case we are using "[  ... ]", not "{ ... }".
Adding a space after the closing quote works as a workaround.

--
Eric Bezault

It does not work in that case, which is not a surprise since we get the problem even when compiling from scratch.

--
Eric Bezault

When you have such editor trouble, can you try to reload the tab using Ctrl+R , and tell us if this solves (temporary) the trouble or not.

I confirm that the problem occurs even when compiling from scratch.

--
Eric Bezault