Closed theologos7 closed 2 months ago
It may be better to change
/J level
to/J=level
so that a simplestring.Split
can be used instead of an error-prone index offset.
that is kinda new to me. as someone who's been using bash for over 2 yrs now, i never thought about this.
7-zip works the same way, =
equals everywhere, which makes it suuuuuuper tedious to use due to lack of tab completions for paths. i ditched using 7zip-cli for that same reason.
but i guess it's just windows things - not aimed at CLI uses 🤷♀️😕
p.s.
ohwwww, now i see why windows use backslashes for paths, 'cz it reserves forward slashes for CLI options 🤦🤦🤦 holy god these legacy shackles. windows ssuckss big time each time.
I made the requested reversion on the publish.bat
file and changed the syntax to /J=<Level>
. I did leave the option to just pass /J
with no =<Level>
which will default to a VeryGood
confidence level.
Adds option for BCU-Console to perform junk removal with a
/J <Level>
switch. Includes updates to the documentation files to account for this change. Welcoming of any pointers or improvements that can be made.I also included a change to
publish.bat
to usevswhere.exe
to findMSBuild.exe
. If this needs to be a separate PR I can split them out.