| 2022-02-05 02:01:35 +0100 | Guest22 | (~Guest22@82-169-216-34.biz.kpn.net) |
| 2022-02-05 02:01:36 +0100 | Guest22 | (~Guest22@82-169-216-34.biz.kpn.net) (Write error: Broken pipe) |
| 2022-02-05 02:36:31 +0100 | <nivpgir[m]> | ughh |
| 2022-02-05 02:36:44 +0100 | <nivpgir[m]> | it's worse than I thought |
| 2022-02-05 02:39:32 +0100 | <nivpgir[m]> | apparently this bug happens on some versions of windows and not on others, and I mean that it varies between versions of the same OS. |
| 2022-02-05 02:40:43 +0100 | <nivpgir[m]> | I tried it on my HOME pc that I think runs a newer version of windows than my work laptop, and everything works perfectly. |
| 2022-02-05 02:41:19 +0100 | <nivpgir[m]> | however on my work laptop I cannot get it working no matter what hack I try |
| 2022-02-05 02:43:42 +0100 | <nivpgir[m]> | I started playing with `createProcess` trying to find the argument configuration that's necessary to get it to work on both systems, and I just CANNOT get it to work |
| 2022-02-05 02:45:43 +0100 | <nivpgir[m]> | however, for now, I hacked it to use `git-bash` instead of `cmd`, which is acceptable for me, but I don't know if it will be for everyone, since it requires installing `git-bash` |
| 2022-02-05 02:47:01 +0100 | <nivpgir[m]> | even using the builtin `bash` that comes with windows won't work because they need to install a wsl linux distro for it, and then make sure it's configured the same way as their windows |
| 2022-02-05 02:49:41 +0100 | <nivpgir[m]> | the closest thing I could think of which can actually work consistently is to use `powershell` instead of `cmd`, which is good because it will actually be installed on every machine no matter what, but for myself I still prefer using `git-bash` since I'm not really familiar with `powershell`. |
| 2022-02-05 02:51:38 +0100 | <nivpgir[m]> | I still need to test the `git-bash` solution on my laptop, but that'll have to wait until Sunday. |
| 2022-02-05 02:55:40 +0100 | <nivpgir[m]> | I wouldn't mind submitting a PR if you think any of the above solutions is good enough, just let me know which one you think is preferred. also I'm not sure how to make it work differently depending on the OS, so there's that, but I'm assuming that's something that's already solved since kmonad already compiles on different platforms seamlessly. |
| 2022-02-05 02:57:56 +0100 | <nivpgir[m]> | anyways, I'm done for today, going to sleep, and you guys probably heard more than what you signed in for in terms of troubleshooting windows issues. |
| 2022-02-05 02:58:05 +0100 | <nivpgir[m]> | so good night |
| 2022-02-05 03:14:09 +0100 | neurocyte0917090 | (~neurocyte@user/neurocyte) (Ping timeout: 256 seconds) |
| 2022-02-05 08:05:58 +0100 | <Solid> | nivpgir[m]: thank you for the investigation! that sounds... horrifying Oo |
| 2022-02-05 08:06:40 +0100 | <Solid> | I think if this could actually be done using powershell that would be really neat, since as you said it should be installed everywhere |
| 2022-02-05 08:08:26 +0100 | <Solid> | Platform-dependent stuff is usually done via CPP macros, in this case they would look like this: http://ix.io/3OHJ/haskell |
| 2022-02-05 08:08:48 +0100 | <Solid> | (kmonad usually does a pretty good job of hiding this in their own modules, but let me worry about that when the PR is there :) |