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
{{ message }}
This repository has been archived by the owner on Feb 15, 2024. It is now read-only.
If you think it's worth it, I could send a PR that prepares a WSL path similar to how it currently prepares a Cygwin path and calls VBoxManage.exe if VBoxManage is missing.
The text was updated successfully, but these errors were encountered:
Oh, I should mention that sometimes I had to hit <space><enter> when it was asking "Press enter when something is ready". It ignored plain <enter>. Probably some WSL incompatibility.
I have no experience with WSL but I believe Cygwin is more portable and WSL is only available for Windows 10, so I believe I'll stick with Cygwin unless there are other advantages to WSL.
I don't think @bronson is implying to get rid of the Cygwin method, but eventually, WSL will be very mainstream. Just an option to allow easier adoption/use.
I'd gladly accept a pull request with an if statement that identifies running under WSL and adds VBoxManage to PATH, but I would like to keep everything under one working directory (no creating symlinks in ~/bin) and avoid elevating privileges (ask the user to manually install the packages).
Yes, I agree with all those points. If I can find some time to try to get iMessage going again, I'll put together a PR. (won't be the next few weeks tho!)
A Debian guest running in WSL worked great. This script is really impressive.
To prepare, I only had to make VBoxManage.exe available as VBoxManage. I did it like this:
If you think it's worth it, I could send a PR that prepares a WSL path similar to how it currently prepares a Cygwin path and calls VBoxManage.exe if VBoxManage is missing.
The text was updated successfully, but these errors were encountered: