Fix Windows shell and path handling#1966
Conversation
|
Hello, there are still some tests failed for me. I'm at commit 948fde2 and running Full log is attached: |
948fde2 to
33940da
Compare
|
Thanks — I tracked this down. The remaining failures were not from the Windows shell/path fix itself, but from selector tests ( I fixed that by resetting those tests to I also cleaned up the branch history and force-pushed it so this PR no longer includes the unrelated Revalidated with:
|
|
Sorry, my bad. After running I also manually tested the path slash bug in #1769 and this PR fixes it for me too. |
33940da to
01958b7
Compare
|
sorray, i did this myself :/ |
|
When did it become so trendy to be so rude. |
|
@badlogic @ferologics Hello, I've noticed that this PR is closed because the main issue is fixed on main already. However there is a minor thing missing: the custom keybinding causing tests to fail. This PR seemed to fix that but the latest main doesn't. Could you consider incorporating that fix into main too? |
|
A simple Relevant log: |
@jamwil i truly wonder what about "sorry, i implemented this myself" is rude? have you also considered that there may be out-of-channel coms between me and fero (a friend of mine)? |
|
I hadn’t considered that, no. From the context in this thread alone it seemed like someone put a fair amount of effort into a PR only to have it closed unceremoniously and with a comment that would be hard to interpret as anything but rude, were it not for the fact that you know each other and communicated via other means, I suppose. |
Summary
!commandconfig values through pi's configured shell abstraction instead of the platform default shellFixes #1775.
Also addresses #1769.
Related prior attempt: #1902.
Validation
./test.shnpm run checkOut of scope / follow-ups
windows-latestCI job in this PR. The goal here was to get the Windows test suite green locally first; CI can be added in a follow-up once this behavior lands cleanly.