Bug 2/30: Dotnet CLI ANSI Escape Codes


Bug 2 is dotnet/command-line-api/Incorrect ANSI escape codes. The last one was embarrassingly easy, but this one is more like real work. I decided that having had one success on this codebase I may as well see if there was anything else I could help to fix. The Windows terminal (or as Microsoft call it the Command Prompt, accessed in .NET via System.Console) is one of those things that most sensible programmers try to avoid.…
Read more ⟶

When a Bug Is Not a Bug


It is not uncommon for a bug to be raised that is not in fact a bug, but a feature request. Take for example OperationCanceledException should not be treated as an error #430. In this bug report jnm2 states that they believe the OperationCanceledException should be suppressed by the command line API library; their rationale being that other libraries often suppress this exception (this is somewhat amorphous as they give no concrete example).…
Read more ⟶

Bug 1/30: Dotnet CLI Parsing


Bug 1 is dotnet/command-line-api/Trailing spaces break parsing in a response file. It looked straightforward, so I thought it would be a good one to start with. Apparently the dotnet CLI has a built in file parsing mode that allows the user to supply a file containing the program’s arguments instead of supplying on the command line itself. This file has 2 modes: Arguments / options delimited by a line break.…
Read more ⟶