logoalt Hacker News

EvanAndersonyesterday at 5:48 PM3 repliesview on HN

I feel like I'm seeing an error, or I just don't understand what they mean w/ "find" and "Integrated port of the original DOS command" and not listed as conflicting.

There's a "%SystemRoot%\System32\find.exe" on every Windows NT-derived OS. That's absolutely a conflict.

Also, the "find" command from "findutils" is in no way functionally similar to the "original DOS command" (which is for finding text in files).

Aside: Eschew "find.exe" on Windows for "findstr.exe". The latter is vastly more efficient. I discovered that by happenstance once and have trained my hands to type "findstr" when I mean "find" on Windows.


Replies

lheckeryesterday at 6:29 PM

We actually open-sourced DOS sort and published a port of the DOS find command. The suite then dispatches to the GNU/DOS variant based on heuristics. The installer allows you to pick what variant to use by default if the invocation is ambiguous.

RachelFyesterday at 7:53 PM

Don't use find, use Voidtools' Everything. It finds filenames instantly, by searching the NTFS structures.

This is one of the few features that Linux file systems do not have.

capitol_yesterday at 6:58 PM

Why not use ripgrep?

show 1 reply