[burntsushi]

You still haven't specified your corpus size, despite me noting how crucial it was to your question.

You also haven't specified what kinds of queries you're running. If you're doing simple literal queries like 'rg foobar', then ripgrep is pretty much as fast as you're going to get when it comes to non-indexed search. It uses all your CPU cores. On Intel x86_64, it uses AVX2 to do the substring search for 'foobar'. There's just not much you can do to go faster than that in terms of latency.

As I said, if you have a large corpus, then the only way to get instant search times is through an index. You haven't said why those approaches don't work for you.

> I think for something like this even grep would be fast enough.

Sorry I should have mentioned this before, but I'm the author of ripgrep. I know a thing or two about how fast normal exhaustive search greps can go. :-)

[leakbang]

I'm querying through ~600k lines of code. Ripgrep is very noticeably faster than grep when I'm searching. I have no complaints at all regarding the speed!

The only issue I'm facing is that I wish for Ripgrep to display me the search results as I type. Similar to how FSearch does it.

So instead of typing a search query and hitting enter in the commandline, I would want to continuously search as I type. I think since Ripgrep is very fast, it would be amazing for this task.

[burntsushi]

Oh. You're not talking about speed. You're talking about the user interface.

I don't know what FSearch is, so that doesn't help this.

What you want is to pair fzf with ripgrep. There are loads of tutorials out there for how to do it.

[leakbang]

That is exactly what I was looking for! Thanks :)