3 ms·
Tell HN: Windows' find.exe claims that it's “Find String (grep) Utility”
... when it's absolutely not even capable of regex matching, which is required under POSIX (and implemented by both the BSD and GNU grep).
- codevark 5y agoPar for the course. Windows also claims it's an "operating system".
- speedgoose 5y agoYou probably already know that, but you should use WSL(2) or Git Bash to not lose your mind.
- glouwbug 5y agoGet the developer’s SDK for Git Bash and then you can use pacman like it’s an arch box
- backslash_16 5y agoI switched to using RipGrep at https://github.com/BurntSushi/ripgrep https://github.com/BurntSushi/ripgrep It's native, really really fast, supports regex, and has nice defaults. The only catch is you need to understand its default ignores if you're working in a git repo.
- runjake 5y agoThe modern Windows equivalent (for over a decade now) to grep is the Select-String command in PowerShell. It supports RegEx fully. In PS, grep is actually aliased to it. https://adamtheautomator.com/powershell-grep/ https://adamtheautomator.com/powershell-grep/
- dingosity 5y agoWindows claims to be POSIX.1 (IEEE Std 1003.1-1990 / ISO/IEC 9945-1:1990) compliant which doesn't cover command line utilities. You might be thinking of POSIX.2: Shell and Utilities (IEEE Std 1003.2-1992), which does cover functions of standard utilities and the shell.
- Rizz 5y agoFind was first added to DOS 38 years ago, years before POSIX was created, and even more years before grep was added to POSIX. Find's capabilities were kept as is for compatibility, newer, more capable, utilities have been added over the years like findstr and select-string.