codinuum
codinuum
A possible workaround attached. [gumtree-unicode-fix.patch.txt](https://github.com/GumTreeDiff/gumtree/files/8020366/gumtree-unicode-fix.patch.txt)
I tried only UTF-8 for some batch jobs.
Unfortunately, no. We noticed that [a similar PR](https://gitlab.com/gerdstolpmann/lib-ocamlnet3/-/merge_requests/21) to the upstream has been open for eight months, while we have several applications that should work with both OCaml5 and Netstring....
We will think about it...
Sorry for the delay. We had made [a forked version](https://github.com/codinuum/lib-ocamlnet3) for OCaml5 six months ago, though not tested until now. So we close this.
Here they are. [a0.java.txt](https://github.com/GumTreeDiff/gumtree/files/13964270/a0.java.txt) [a1.java.txt](https://github.com/GumTreeDiff/gumtree/files/13964271/a1.java.txt)
Confirmed. Thanks! How about comparing another pair of files with python-treesitter? [a0.py.txt](https://github.com/GumTreeDiff/gumtree/files/13964620/a0.py.txt) [a1.py.txt](https://github.com/GumTreeDiff/gumtree/files/13964621/a1.py.txt) String literals are missing in the parse trees...
Parsing results in the following in my environment... ``` module [0,113] expression_statement [0,9] assignment [0,9] identifier: s [0,1] =: = [2,3] string [4,9] ": ' [4,5] ": ' [8,9] function_definition...
@jrfaller Updating tree-sitter-parser resolved the problem. Thanks a lot!
That reminds me of something. I have seen conflict markers `>>>>>>>`, `=======`, and `