Add rawhide #590
Open
Add rawhide #590
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New App Submission
Repo or homepage link:
https://github.com/raforg/rawhide
https://raf.org/rawhide
Description:
Find files using pretty C expressions.
Why I think it's awesome:
Disclaimer: I wrote rawhide so I am very biased. Use your own judgement. Or just dismiss this.
In the 7th Edition UNIX programmer's manual (1979), the find(1) manual entry has a BUGS section which just says:
That fact has never changed and never will. It got standardized so it can't. We all just got used to it. Like Stockholm Syndrome.
Rawhide (rh) changes this. It's a breath of fresh air. It can do everything that GNU find can do (except
-fstype), but without the painful syntax that's too ugly to remember. It has a search criteria language based on C expressions, and you can define your own functions if you don't like the existing names for things. So if you don't like it, you can change it. But the standard/default search terms are pretty awesome already. It's a pleasure to use.As well as the usual search criteria that GNU find supports (e.g., name, path, symlink target, size, age, permissions, ...), rawhide (rh) can also search by file attributes/flags (like immutable, append-only, ...), and Access Control List ("POSIX" ones (for Linux, macOS, Cygwin) or NFSv4 ones (for FreeBSD, Solaris)), and Extended Attributes (names and values), MIME type, and file type (i.e., what would file(1) say?), and the contents of the file (like grep). And it can output search results in detailed ls-like format or in JSON format. And the only regex syntax it supports is perl regex (pcre) because it's the best.
It's like the love child of find, ls, file, grep, sh, C, and perl. And lsattr and getfacl and getfattr.
Every time I see a ghastly find command offered as the answer to a question on stackexchange or similar, I can always see a much much shorter rh alternative that's clearer and easier to understand (and easily fits on a line).
I'm delighted that I've written this, because it's so much fun to use, and because I know I'll never need to use find again.