Jon Sequeira
Jon Sequeira
We did originally have such a toggle in place (without the open-ended extensibility mechanism). There were still cases that neither of the available options satisfied, though. Probably orthogonal to this...
There's a more minimalistic version here: https://github.com/dotnet/runtime/pull/76271/files Note that this will not allow one response file to reference another.
> Sure. But I expect the two most common options are "split by whitespace" and "split by newline". This isn't the case, unfortunately. Within "separate by newline" there are several...
> This is very much an like "tabs vs spaces" where you'll have two (or more) competing standards effectively forever The goal was to try to avoid that by aligning...
Have you looked at System.CommandLine.Hosting? It provides integration with Microsoft.Extensions.Logging, Microsoft.Extensions.DependencyInjection, etc.
You could use `Environment.CommandLine` for this.
>No, it doesn't. Because dotnet-suggest cannot distinguish exceptions in the tool from normal output from the tool. Exceptions within dotnet-suggest are sent to stderr. The tool error is printed to...
Some of these tools might be using a version of `System.CommandLine` that isn't compatible with the version of `dotnet-suggest` that's in use. Support for cursor positioning (i.e. (`[suggest:32767]`) wasn't available...
Yeah, I'm curious about how it got registered.
At first glance this looks to me like a bug. I'm not sure if the ability to specify the order in which these things happen is generally useful, but it...