Show HN: A simple, fast and user-friendly alternative to find, written in Rust

Post by Ezku » Mon, Oct 09, 2017, 2:11 PM UTC

TeddyDD wrote: post #171

coldtea wrote: post #17

It would be nice to have a collection of modern/faster/saner alternatives to common unix tools and such utilities (made in rust or not) that becomes standard -- or at least easily installable in linux distros and OS X. Not for replacing those tools, but for supplementing them. Thinking of stuff like fd and: ripgrep: https://github.com/BurntSushi/ripgrep (grep/ag alt) xsv: https://github.com/BurntSushi/xsv (csv tool)…

I like tool called "just". It's simple command runner inspired by make. https://github.com/casey/just One could argue that tool like this makes no sense since make is installed almost everywhere but I'm already using fish shell so one more non standard tool makes no difference. I appreciate simplicity of "just".

Post by burntsushi » Mon, Oct 09, 2017, 4:52 PM UTC

zeotroph wrote: post #192

burntsushi wrote: post #188

Earlier quoted context omitted.

If you're grepping binary files, then even with grep, you need to pass the `-a/--text` flag. ripgrep has the exact same flag. Protips: `rg -u` stop looking at `.gitignore` files. `rg -uu` searches hidden files/dirs. `rg -uuu` searches binary files.

I actually forgot why exactly I switch from rg to grep for binary files, but after some tests I found the use case grep can but ripgrep can NOT do: $ grep FOO * Binary file libBar.so matches foo.txt:file with FOO in it rg/rg -u/rg -uu/ ignore libBar.so completely, whereas rg -uuu spits out binary garbage. Here grep's default behavior is what I expected: I want to know which binary files contain some symbol, details a…

Post by earenndil » Mon, Oct 09, 2017, 5:47 PM UTC

coldtea wrote: post #17

It would be nice to have a collection of modern/faster/saner alternatives to common unix tools and such utilities (made in rust or not) that becomes standard -- or at least easily installable in linux distros and OS X. Not for replacing those tools, but for supplementing them. Thinking of stuff like fd and: ripgrep: https://github.com/BurntSushi/ripgrep (grep/ag alt) xsv: https://github.com/BurntSushi/xsv (csv tool)…

Post by laumars » Mon, Oct 09, 2017, 9:55 PM UTC

foo101 wrote: post #191

laumars wrote: post #161

Earlier quoted context omitted.

You can. There's nothing stopping you adding ~/bin to $PATH. Many compilers allow you to specify the destination location either via a ./configure flag (for example) or an environmental variable. Or there is always the option of doing a `make build` and then manually copying the binaries into your ~/bin directory without doing a `make install` You can also add ~/lib (for example) to your LD_LIBRARY_PATH path if you w…

This is precisely what I am forced to do and I do this very often when I have to setup my environment in a remote box I don't have root-login too. But this is by no means a trivial process compared to how easily we load a complex app into a browser tab just by clicking a URL. I think it is fair to hope that after 25 years of Internet, it should be easy to bring in new tools from the Internet into our local environmen…

Post by joshka » Tue, Oct 10, 2017, 9:40 AM UTC

zimpenfish wrote: post #187

parmesan wrote: post #177

Earlier quoted context omitted.

httpie: https://github.com/jakubroztocil/httpie (cURL for humans) Httpie is my goto http cli for all systems. Pretty much PostMan (that a lot of ppl use for no reason) but without annoying UI and on a single line. Formats JSON and colors it right in the terminal as well. Has a super nice query, header and post body syntax. Works well with sessions and cookies.

> Pretty much PostMan (that a lot of ppl use for no reason) I can't see anywhere in the httpie docs about capturing variables from and/or running tests on the HTTP responses - it's an extremely powerful feature of Postman when you're debugging non-trivial HTTP flows.

    $ userId=$(http get https://jsonplaceholder.typicode.com/posts/1 | jq '.userId')
    $ http get "https://jsonplaceholder.typicode.com/users/$userId" | jq '{name,email}'
    {
      "name": "Leanne Graham",
      "email": "Sincere@april.biz"
    }