Hacker News Reader

Comment by nhumrich | Hacker News Reader

I have heard this from a lot of people, yet here I am, using a terminal that supports this, and have yet to ever do it. Can you help me understand what workflows you depend on Ctrl+f for? I wonder if I am missing something big.

View on HN

Don't you ever need to search through a program's output; e.g., to find what failed? Otherwise you'll have to remember to tee everything to a file every time you run a command.

You know, I can't remember ever doing this in a terminal. Not because it doesn't sound useful (it sounds VERY useful), it just sort-of never occurred to me as a thing you could do. It's just muscle memory at this point to rerun the command with a pipe to a pager and search there.

I get ya, but this would be more of my case if my terminal didn't have scrollback search available (or if I really wanted to scrutinize the output carefully).

In foot I just ctrl+shift+r and search back the references one-by-one in a mode, which I guess is 90% of my use case for scrollback.

I guess that's what I always do. or grep or awk or sed.. Maybe if a program takes hours to return it's helpful to be able to search the terminal, but otherwise i'm just pushing up with my arrow and `| grep -v UGLY | grep BEAUTIFUL`

|grep or |less

Not after it's run you don't.

You just run it again.

    $ rm -rfv huge_dir
    (A zillion removed files scroll past)

Now check if any of the removed files that were dumped out contain “foo.txt”.

No, “just run it again” doesn’t work.

I can’t always do this.

It could take a long time to run, and my time is not free. The native MacOS terminal has a buffer search, why doesn't ghostty? It is a rudimentary feature.

forever i've been doing the grug brain way of copying the output to notepad++/sublime-text

Reply on news.ycombinator.com