Well it depends which one you do. Nobody greps PDFs. And even if you have the article as plain text file you woulnd't grep to see nearby text, you would use your editor's equivalent of ctrl+f.

ctrl+f is about finding the context of something

grep is about filtering out the irrelevant information

Linux utility "less" which is the best tool to browse logs ever has both ctrl+f equivalent(/), and grep equivalent (&) and both are useful.

Control + F will resonate with a far wider audience than the term 'grepping', which I assure you on many other social media spheres, would be met with blank stares. Most people I know in the real world have never interacted with a terminal.

there's just so few people who still grep through website code directly. :P

In Firefox the / key is bound to quick find, so it's there in spirit.

Firefox also allows to search without bringing up the search bar first by setting "accessibility.typeaheadfind" in "about:config" to true. Reducing the timeout for the search bar to disappear after the last keypress is very useful as well. This is hidden behind "accessibility.typeaheadfind.timeout".

Caveat: is messes with pages that use normal letters as keyboard inputs, like WASD as movement keys. One might need to disable it temporarily if that happens.

I use Firefox developer edition - I assume that's set up by default. Though I've learned to work around it, it has driven me mad for so long - I didn't know you could turn it off! Finally, it's fixed! Thank you!

Everyday a good deed - I'm glad I could help ;)

TIL - Thanks!

You mean you don't `curl | rg` web pages?