-
Notifications
You must be signed in to change notification settings - Fork 9
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
"The specified path does not exist" after start on Windows #25
Comments
I've never tested on Windows and I'm surprised it even starts. There's a few Unix specific things hard coded that would only work on *nixes and Mac. I don't have a Windows box to test unfortunately. Which shell are you using? Are you using bash via cygwin or something similar? |
Oh you mentioned it's cmd.exe (not sure what Console 2 is.) I'm honestly not super interested in adding Windows support and don't have the setup to test it anyway, but if you feel like helping out or know someone who can, I'd happily accept patches! |
I am using the standard |
I suspect it's related to the dotfiles it installs during startup to make autocompletion and history work. It places those files in your home directory, which works differently on Windows. Maybe I can put some time aside to look at it in a VirtualBox. Out of curiosity, why are you using cmd.exe? That's like the worst shell in computing history. Especially with cygwin installed, you could just use bash or zshell. They will translate Unix paths to Windows. |
That problem also happens on a Cygwin-free machine, the one I am currently on. I tried installing Cygwin/bash.exe on this one as well, and replicant still gives the same path error. |
After launching
replicant
from the Windowscmd.exe
or Console2, aThe specified path does not exist
error is thrown.Everything keeps working, but that may cause an issue when launching
replicant
from external tools. In Intellij Idea, for example, as it looks like it's not flushing the standard error properly, thus not showing the initial "Welcome" message.Attached screenshot.
The text was updated successfully, but these errors were encountered: