Philippe Berthault

Hello, You are right, the backquoted property is benign for C/C++ and it works well for Go since I turned on this property in my cpp.properties file. So you can close this ticket. Perhaps these properties (backquoted, hashquoted, triplequoted, etc.) must be set on by default on the cpp.properties file instead of setting off by default, in order to correctly support all the 14 languages using the cpp lexer ?

I seen there is a backquoted.strings property in the SciTE documentation. I tried it and it works well but it's not possible to activate it only on Go language. It applies also for all languages managed by the CPP lexer. I think the backquoted.string property would apply only on C++ files, not on Go files. Perhaps the Go language would be separated from CPP and would have it's own lexer. In example, the preprocessor properties apply also on Go files but there is no preprocessor in Go language.

Hum, the sourceforge web interface for posting messages hasn't preserved lines feed and replaced the backquotes by a frame with ".." . After a '\' character, there is of course a line feed.

Raw strings in Go language not managed by Scite 4.1.0

I tried to launch GNOME session on Xorg and the problem disappeared on Xorg. So, you're right, the problem comes from Wayland. Consequently, you can close this ticket and perhaps add a warning about Wayland on SciTE web site. Regards.

Popup menus programmed in LUA scripts not correctly displayed on Linux GTK

I applied the patch and it's now OK for me on Linux Fedora, even with a very big...

In fact, the problem has not disapperead. I can reproduce it. You wil find in attachment,...