Where does using / in paths rather than \ not work in Windows? Sorry to pick on your example, but from what I can see, they've already done that.
If you want paths up to 32k you need to use back-slashes.
I think this is the reason they are not switching e.g. Visual Studio over to max 32k paths.
That's so accurate. I used to write shell scripts with
command $1
until I got a few too many nasty surprises with dashes in filenames. foo() {
for arg in "$@" ; do
echo "arg is \"${arg}\""
done
}
foo 'bar baz' 'spaces in filename.txt'
> dashes in filenames.When writing shell scripts it's a good idea to use the -- option whenever possible
stupid_backup() {
cp -a -- "$@" /stupid/backup/dir/
}
# copies 2 files
stupid_backup --files '-with -leading -dashes'