Open Davidj361 opened 1 year ago
What do you mean by "different docker instance"? You mean working with a remote docker host? In this case please keep in mind that lsp-docker
was tested mostly on the same-host configuration (docker host is the same as the one you run Emacs on).
But if you are trying to use docker on the same host, then yeah: launch spacemacs, open the project, register it (please read the docs about the entrypoints e.t.c), probably build an image and then start lsp
What do you mean by "different docker instance"?
I mean my own docker image with its own toolchains (different compilers and various other binaries + libraries) in it, i.e. not the emacslsp/lsp-docker-langservers
or emacslsp/lsp-docker-full
docker images.
I still don't understand the installation process for spacemacs. I read the README already and tried putting the lsp-docker
package to my dotspacemacs-additional-packages
but that didn't work and I also added the other configuration to my dotspacemacs/user-config
. It didn't install the package and so on. I was also unsure if the bash script were necessary in order to use lsp-docker
.
Ah, ok, I see the problem now. Sadly I can't help you with the details on how to install packages with spacemacs (with vanilla emacs this package can be installed just the same as any other package).
As for the docker image: please take a look at readme. You can either use a persistent yaml config or a .dir-locals
file to reference a particular docker image (or container).
I'm confused, how do I install this properly for spacemacs and how do I use this with a different docker instance? Do I have to use
start-spacemacs.sh
? Or do I launch spacemacs on the host machine and open the project and lsp-docker automates it?