search

boringcactus / pijul-windows-builds

windows builds for https://pijul.org
Creative Commons Zero v1.0 Universal
30 stars 6 forks source link

Working perfectly to completely not working after vscode updated and added Trusted Windows and "Restricted Mode" #3

Open cellarweasel opened 1 year ago

cellarweasel commented 1 year ago

Every time I record now I get "Error: Cannot parse change" I'm assuming but every time I pijul record a change it pops open vscode in restricted mode and I get that error from pijul. Even if I do ctrl-enter to remove Restricted Mode it seems to have done something to the commit temp file or something and I still get the Cannot Parse Change error. Feed back if others are even experiencing this with the Windows build or if I'm doing something silly is appreciated.

cellarweasel commented 9 months ago

Finally had some hobby time to get back to this and it's independant of vscode. I uninstalled vscode adn now the toml temp files are also getting 'cannot parse change' 

PS C:\Users\Wirrsturm\revisions\a> pijul record
Error: Cannot parse change

I'm still using the old version. I'm off to use the newest and compare if they're up to date etc. 🤞 I'll be able to close this guy here if the new version fixes things.

cellarweasel commented 9 months ago

Damn, it's still doing ot for me with the newest pijul-with-git at pijul 1.0.0-beta.6. Can anybody confirm that this is for everybody or just me?