Daniel Peñalba

Absolutely! Yes, this project has a CI build for the managed part but the unmanaged part is unfortunately [manual yet](https://github.com/danipen/TextMateSharp/blob/master/onigwrap/README.md). A PR to automatize it would be more than welcome.

Oh ok! Unfortunately I don't have experience mixing managed and unmanaged build. I'd love to hear someone here that already knows the best practives of doing it. That being said...

That sounds good because a new PR with the new native assets will run unit tests in the three platforms. A couple of things to take into account: - note...

Yes. For MacOS lipo tool does the trick. It's fine: https://github.com/aikawayataro/onigwrap-build/blob/c88b7a6356936f1ea72ba2dc1883f088b4742245/build.osx.sh#L22 > Hmm, have you seen linked action? There are builds for Linux aarch64. Yes, I mean Linux x64 is...

For wasm, there are some things to take into account: - `libonig.a` needs to be compiled and copied [here](https://github.com/danipen/TextMateSharp/tree/master/src/TextMateSharp.Wasm). Instructions about how to compile for wasm, [here](https://github.com/danipen/TextMateSharp/tree/master/onigwrap#web-assembly). - `libonig.a`, `oniguruma.h`,...

Sorry I can't remember now why I did that way. I guess that it is the combination that worked those days (I remember having difficulties to ship the native assets......

So are you suggesting creating a new repo and nuget package for onigwrap?

A separate package would be good but I'd like to manage the sources in this repo (not in a external repo) as all belongs to the same project IMO.

Sounds good.

We're experiencing the same crash typing `=>` at the beginning of a line. For sure it's affected by ligatures since that char combination is causing a ligature. We're using Inter...