Daylin Morgan

Yay encoding errors.... docker or your system is returning text with a different encoding. I think I can catch this at runtime. What is the output of the following command:...

Removing the encoding all together will be an issue if there is an error in the subprocess because then the stdout/stderr is returned to the user: https://github.com/daylinmorgan/monolisa-nerdfont-patch/blob/6f5ec7e73e781a11cd37dceb698a9ad3bd8777ee/patch-monolisa#L97-L105 I don't know...

> Wouldn't it be better to enclose the subprocess block in `try..except` and catch explicit errors. Not really because we don't actually need the output for anything so might as...

We don't want to run the subprocess twice because the error has nothing to do with it. And this doesn't solve the problem I mentioned [here](https://github.com/daylinmorgan/monolisa-nerdfont-patch/issues/7#issuecomment-1979368996) that we still want...

I use none semver tags for e.g. a `nightly` release that raises a similar error for https://nimble.directory/pkg/forge