installer

[DetachHead]

the installation instructions require manually running commands. other version control tools such as git have installers. it would be very convenient if sapling had one too

[KotlinIsland]

also PS> setx PATH "$env:PATH;C:\Program Files\Sapling" -m is sus, it will overwrite the path with an expanded one.

[bolinfest]

Thanks, yes, we would prefer to provide an .msi. Unfortunately, no one on the team has experience creating .msis, so we need to carve out time to educate ourselves.

[KotlinIsland]

I think .msix installers are the preferred option nowadays https://learn.microsoft.com/en-us/windows/msix/overview

[vsytch]

also PS> setx PATH "$env:PATH;C:\Program Files\Sapling" -m is sus, it will overwrite the path with an expanded one.

I think this command bricked my system path. I got a truncation warning when running it:

PS C:\Users\vsytc> setx PATH "$env:PATH;C:\Program Files\Sapling" -m                                  
WARNING: The data being saved is truncated to 1024 characters.

SUCCESS: Specified value was saved.
PS C:\Users\vsytc>

And now my system env looks like this:

[DetachHead]

@KotlinIsland @vsytch since that's a different (and critical) problem i've raised it separately #234