You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cargo is also not a fan when a directory cannot be canonicalized, but here Helix does a cheeky .unwrap() after calling the std::fs method to canonicalize the executable directory (This is inside Helix/Loader, and right on startup). I have created a pull request (#12879) which allows Helix to launch in this situation, but according to my log it looks like the LSP still fails to load which might be related.
Reproduction Steps
I tried this:
Creating a RAM disk via ImDisk on Windows 10
Installing Helix on it
Running Helix
I expected this to happen:
Helix launches
Instead, this happened:
> .\hx.exe -vv
thread 'main' panicked at helix-loader\src\lib.rs:74:10:
called `Option::unwrap()` on a `None` value
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
What does cannot be cannonicalized mean? That would usually mean that the directory does note exist. Helix does not support running in a directory that has been deleted
It's a proper path on a mounted (temporary) filesystem. The files still exist as of the time of running .\hx.exe
& I mean that's the error. Windows doesn't like the path & will not give you a canonical version of it.
See the linked PR for how I was able to get Helix to run, it is very simple.
@pascalkuthe I added some more context to the repro section. I am using ImDisk to create a RAM disk & installing+running Helix on that, which causes Helix to crash immediately.
Summary
Cargo is also not a fan when a directory cannot be canonicalized, but here Helix does a cheeky
.unwrap()
after calling the std::fs method to canonicalize the executable directory (This is inside Helix/Loader, and right on startup). I have created a pull request (#12879) which allows Helix to launch in this situation, but according to my log it looks like the LSP still fails to load which might be related.Reproduction Steps
I tried this:
I expected this to happen:
Helix launches
Instead, this happened:
Helix log
~/.cache/helix/helix.log
Platform
Windows
Terminal Emulator
Powershell 7
Installation Method
source / releases page
Helix Version
Current master / 25.01.1
The text was updated successfully, but these errors were encountered: