You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Response file parsing can currently be customized by a developer using System.CommandLine using the CommandLineBuilder.ParseRespondFilesAs(ResponseFileHandling) method. The ResponseFileHandling enum provides two modes (in addition to Disabled) but the behavior is not apparent to end users, and is occasionally surprising.
The proposal is to support only a single response file parsing behavior by removing the existing methods and supporting only enable/disable. The new behavior would follow these rules:
Multiple-line files will be parsed treating newlines as equivalent to spaces.
Multiple tokens on a single line will be parsed as though passed verbatim on the command line.
Including a space within a token will now require enclosing the token in quotes, e.g. "this is one token".
Shell-specific escaping of quotes will not be required.
Allow comment lines using a # prefix at the beginning of the line
Open questions:
How should quotation marks be escaped?
The text was updated successfully, but these errors were encountered:
It's inconsistent, with minor differences even among Microsoft implementations. Documentation is a bit sparse. I couldn't find any mention of escape syntax.
Response file parsing can currently be customized by a developer using System.CommandLine using the
CommandLineBuilder.ParseRespondFilesAs(ResponseFileHandling)
method. TheResponseFileHandling
enum provides two modes (in addition toDisabled
) but the behavior is not apparent to end users, and is occasionally surprising.The proposal is to support only a single response file parsing behavior by removing the existing methods and supporting only enable/disable. The new behavior would follow these rules:
"this is one token"
.#
prefix at the beginning of the lineOpen questions:
The text was updated successfully, but these errors were encountered: