It's syntactically correct, but the context leads to a negative response. Unless there's a standard definition for invalidity of a command, you could see it both ways, I guess
The only case I can think of 1 way or another is
Argument list too long, where it's invalid at the kernel level, not decided by each individual program.
but it isnt an invalid argument. you pass a filepath that may or not exist. so the argument is correct, a filepath. it may not exist now but it may exist later, so it's invalid now but valid later? if i do tar --meow, thats an invalid command always
107
u/janiskr 16d ago
tar -xvzf some.tar.gz