Utility.CommandLine.Arguments
Utility.CommandLine.Arguments copied to clipboard
Argument starting with tilde (~) are not captured and left blank
trafficstars
Version: 6.0.0
When passing an argument that begins with a tilde, the argument is not populated to the attributed variable. This would be a common case in non-windows environments to signal relative-to-user paths.
Ex: dotnet run -file "~/data/path/to/file"
Thanks for brining this up. I had a lot of difficulty with this originally, but looking back I think it was probably more about me using MINGW64 on Windows and that takes a lot of liberties when parsing input.
I'll take a look at this on Linux and see if anything jumps out.