-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DistantLaunch error "vim/_editor.lua:0: Vim:Failed to start manager" #114
Comments
It looks like the manager is failing to start. There's a couple of things we can do to diagnose:
|
I reinstalled from the script |
What operating system are you using? On Unix-like systems (Linux, MacOS, FreeBSD) a socket file is created, but the error message isn't really giving us details, which is surprising. Try a different Unix domain socket pathYou can try something like When it says
If you supply
The full path should be created automatically for you. Not sure why it's giving an error instead. Unix domain socket pathsIf changing the socket path works, you can specify it as part of your setup process: require('distant'):setup({
['network.unix_socket'] = '/tmp/distant.sock',
}) Use a private networkYou can also use a private network, which will create the Unix domain socket in a local path tied to neovim itself: require('distant'):setup({
['network.private'] = true,
}) |
Hello, I had a similar issue and using
Note also that After the above it was able to connect to a remote server and open files, etc. Hope this helps in your case. Cheers. |
It's Ubuntu 22.04.1 LTS. WSL unfortunately - corporate laptop.
Thanks, that worked. @anchorite |
Windows pipe on WSLI haven't checked WSL, but neovim will supply distant with both a windows pipe and unix domain socket as options. Distant itself "should" detect which one to use for you. Do you see a socket file created? If so, then it's using the socket file. This is baked into which version of distant you're using, the one compiled for Windows or the one compiled for Linux (if you're using WSL). The one compiled for Linux will always using a domain socket while the one compiled for Windows will always use a Windows pipe. The UI is just showing you both. If you find this confusing, we could add a check in neovim to see if you're in Linux to show the socket or Windows to show the pipe in the UI, hiding the other one. Color Scheme@InsaneZulol hm, that color scheme doesn't look right. It should ideally be something like below. I haven't actually checked the colorscheme on default neovim as I'd used the same scheme as mason.nvim, which I assumed worked. Seems like I may need to both tweak the default colors and make it so it's easier to customize the colors yourself. NetworkingI may switch You can start a manager outside of neovim and - when not using private - neovim should connect to it. This goes for the global socket or the user-local socket. If you use a custom socket path, it won't know where to find it unless you also provide that in the configuration. Config fileYou shouldn't need to create the configuration file, but it won't hurt to do so. I would expect to see an access attempt from strace that @anchorite saw, but when it fails to load, the default configuration is used instead. This is the same configuration you get from generating it! :) |
I tried all of these tips, I'm in a Linux virtual environment on a Chromebook. I'm trying to use this along with the DevPod CLI which starts up a Devcontainer that I can SSH into. When I attempt to connect I first get a prompt/notice that the host is not yet trusted. When I answer with a
If I attempt to use the |
Does the devcontainer have the distant CLI inside it? Or are you trying to use pure ssh? If pure ssh, use connect instead of launch. If you're using the distant inside the container, can you use the Lastly, if you're using distant inside the container, can you try starting distant from inside and then connecting to it versus launching to it? You'll need to get the key printed when manually starting the distant server to provide when connecting to it, though. |
Hello! How can i do this? - "2. Needed to provide the |
Hi,
I'm getting following error executing
:DistantLaunch ssh://neeeeet.net distant.args="--log-level trace --log-file /tmp/dist_launch.log"
:My mess of packer config at the moment
Distant.nvim:
0.3
Distant version:
0.20
. Tried with both gnu and musl. I've tried 0.20 alpha 13, but this resulted in compatibility check error.checkhealth distant:
My mess of packer config at the moment
The text was updated successfully, but these errors were encountered: