whoisninjaturtle

Sorry to cross over but https://github.com/ratchetphp/Pawl is in exactly the same boat. My company uses Pawl specifically and it's to the point where we're ready to maintain our own fork...

The existing repository structure makes sense; RFC6455 defines agnostic components that anyone could use in their Server/Client implementations. These components are separate from the implementations themselves. Pawl is purely an...

Interesting. I took a quick look at this in the same way on a RH-flavor Linux install and my PATHs are not rearranged like you're describing. ``` bin/patch /root/.vscode-server/bin/8b3775030ed1a69b13e4f4c628c612102e30a681/bin/remote-cli:/root/.nvm/versions/node/v13.12.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin src/patch...

I noticed that change and wondered myself too. I did look closely at the two given PATHs and they are simply just rearranged, not actually different in content, which makes...

More to your original point, it would seem advantageous in multi-version environments to be able to pass the desired PHP executable path into patch via CLI option

Either pass the Websocket around to whatever needs it or make it globally accessible to everything that does.

This has already been fixed: https://github.com/ratchetphp/Pawl/pull/158 I suspect this could be closed