Closed fast-90 closed 1 year ago
Thanks very much for all of these suggestions. I'll improve the documentation ASAP.
Thanks again.
No problem! For the part I mentioned you could use something like:
# move the resulting .so file to the lspce folder (note the rename of the file as well)
$ mv target/debug/liblspce_module.so lspce-module.so
# or alternatively, if .d and .dylib files are created for you:
$ mv target/debug/liblspce_module.d lspce-module.d
$ mv target/debug/liblspce_module.dylib lspce-module.dylib
With the above, I was able to use lspce on MacOS (I was able to get completions and error diagnostics, and find definitions/references and rename work). Only thing was that it wasn't aware of my virtual environment as mentioned in #6 .
Thanks! Glad to hear that lspce works in some degree for you now. I guess I need some time to figure out what to do about #6 , but I'll.
I'm not an Emacs "expert" by any means, but it was a trial-and-error process for me to get this setup. In particular, the following part was unclear to me:
.../site-lisp/lspce
if following the instructions). I would reflect that in the wording to make it clearer.cargo build
are namedliblspace_module.d
andliblspace_module.dylib
(presumably because I am on MacOS?), but the instructions should still apply. Maybe good to clarify?:load-path "/path/to/lspce/lisp"
part of the use-package declaration is confusing, given that in the installation instructions you would have no lisp folder in "/path/to/lspce/". Maybe change to reflect that?It doesn't amount to much, but I think these suggestions can make it easier for newer people like me to set it up :)