4 ms·
Unfortunately that's not the same due to find args being order-significant. It's the difference between only searching the desired dirs, versus recursing throu
by baobun 2y ago
Unfortunately that's not the same due to find args being order-significant.
It's the difference between only searching the desired dirs, versus recursing through your entire filesystem (well, cwd) and then filter results based on path.
Having to go into the middle of the line to change the most commonly changed parameter is bad ergonomics when rerunning stuff from history with small variations often. Especially when basically only find is the special kid and everyone else is happy with it at the end. And it's not like it's ambiguous: find will just throw an error and tell you what you should have typed (as opposed to any other misorder, which it will still run, just not the way you might expect; see above re -path)
Having to cd first would be even worse.
- mixmastamyk 2y agoThis is a modern reinterpretation of the concept, not the tool. No reason an option can't go at the end unless you're determined to copy limits from the past. If so, maybe just use find and save yourself the trouble. Interspersed/intermixed options have been around for quite a while, though not certain they made their way to golang. If not, the program could handle argument processing itself.