Closed anoduck closed 2 years ago
Needless to say, that although the dynamic client does successfully build in OpenBSD. EMACS will not touch it unless the ELISP source files are modified to allow it to do so in "berkley-unix". So, returning to the editor and modifying those files. This time, I will allow time for my changes to mature like a fine wine before sending a pull request.
Since the dynamic client is compiled by hand and not automatically fetched by EMACS, all that was changed in order to allow cargo to build was
env.bash
. The client was built successfully, but not installed in the system withcargo install --path ./
. It was unclear whether this additional step was needed or not.After completion of this pull request, I will perform a PR in my forked repo, and then instruct straight to install elisp-tree-sitter from there. This should allow me to then go into the repo and compile the client again by hand for testing.