Fredrik Høisæther Rasch

Yes, the log states that I am using nimsuggest compiled from devel, but I have confirmed that the same issue occurs on vanilla 0.17.0 nimsuggest.

Yeah, I have also converted over to httpyac. Httpyac also has built-in hooks for extending, user interaction apis for querying for inputs, etc.

@Themodem yeah, I personally prefer the one below, but I agree that it is still horribly ugly... ``` powershell foreach ($package in $(dotnet tool list --global | Select-Object -Skip 2))...

I am considering to write myself a tool that uses the techniques shown above, but also uses Nuget to determine whether a tool actually is out of date. You might...

> #3115 clearly state DotNetCliToolReference is dead Hmm... thinking about that, maybe someone can ask the dependabot nuget-integration to also do automatic updates for dotnet tools listed in a Dotnet...

@KathleenDollard My idea is more in the direction of changing how an application outputs stuff. If you set the culture that will affect all of number parsing, number outputs, DateTime...

@jonsequitur Hmm, I absolutely think that we should also add an environment-variables directive! That would be a great bonus! I'll get right on it. However, I am unsure whether setting...

I have added the environment-variable parsing directive as its own proposal in #965. > Possibly related: https://github.com/dotnet/runtime/blob/master/docs/design/features/globalization-invariant-mode.md @jonsequitur That is an interesting point, setting the variable `DOTNET_SYSTEM_GLOBALIZATION_INVARIANT` will enforce invariant....

@jonsequitur I merged master into this branch after #965 got accepted. So now, with environment variable parsing out of the way, what do you think about my choice for well-known...

639624f6f5a43dfaca25b620f697ec476e38b9a7 shows an interesting challenge for culture awareness: The HelpBuilder is run **AFTER** the invocation pipeline has completed, and therefore the execution context has been restored to the previous culture...