#1 Following the guide is Rough! but I got through it without too many workarounds.

Opened by cellarroot on May 21, 2023
cellarroot on May 21, 2023

Notes to self. Wow there were a lot of documentation bugs. And also a Windows bug on literally recording inside b. Starting with the literal bug first.

PS C:\Users\Wirrsturm\revisions\b> pijul record -m “blibli added to b” Error: Cannot parse change That’s the windows binary right there. 5/21/2023. VScode just introduced the “Trust workspaces” and it’s suuuuuper annoying for the unoffiical windows build. I’m not sure where or how to tweak that but good lord that was annoying. I’m not sure it was related. maybe just a red herring. But also editing in code and then getting “Error: Cannot parse change” was pretty show stopping.

cellarroot on May 21, 2023

I continued to use WSL and treated is as a “Debian operating system” even though it’s technically Ubuntu and that might not be beginner friendly knowledge. Lots of death by a thousand cuts stuff. I’m going to document the flaws in the docs in another discussion to keep this focused on the Windows failure to work out.

cellarroot closed this discussion on May 21, 2023
cellarroot on May 21, 2023

oh I closed this discussion and it shouldn’t be.

cellarroot reopened this discussion on May 21, 2023