rdipardo

@ToddAndMargo, if you're still interested in having a builtin Raku file type, you can build a custom Geany from @techee's [PR][0], like this: ~~~sh [ ! -d geany ] &&...

> I'm wondering about the Chinese characters you mentioned. Those could be ANSI file paths being rendered as multi-byte streams; forcefully casting a `char *` to a wide string produces...

Here's the "official" explanation, courtesy of Raymond Chen: > Putting ASCII alphabetics in the high-order byte of UTF-16 code units results in nonsense Chinese characters >

Made some progress as far as reproducing the random Chinese and the failure to open more than 2 or 3 files. Most importantly, I can't get the GTK file dialog...

> Or if "somebody" wanted to update the native dialog handling to use the newer MS dialogs which return multiple results in arrays of pointers to strings. Unless Geany intends...

This looks good, but, to my thinking, incomplete without support for Visual Prolog, which is what Lexilla's lexer [actually targets][0]. I opened https://github.com/techee/geany/pull/4 to give an idea of what a...

@techee, It looks like the primary keyword set in your last commit left out the VisualProlog type specifiers [^1] (or ["Domains"][0], as the spec calls them). Compare the appearance of...

> I just suspect not many people will use Geany for Visual Prolog Sounds reasonable. Let's just settle for enough SWI-PL keywords to provide a common denominator between the Vim...

> Right now it's the VS code keywords only. I recommended that set because it's much bigger overall, but it reflects only one syntactic category ([builtin functions][0]). We still need...

> I'm not sure I understand how Scintilla follows the "inefficient but easy" tradition Easy to implement: > [S]ee how little code is needed to use Scintilla Inefficient if you...