3 ms·

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 workflo

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.

esafak 1y ago
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.
- SSLy 1y ago
  forever i've been doing the grug brain way of copying the output to notepad++/sublime-text
- ludsan 1y ago
  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`
- OskarS 1y ago
  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.
  - badosu 1y ago
    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.
- Geezus_42 1y ago
  |grep or |less
  - esafak 1y ago
    Not after it's run you don't.
    - Geezus_42 1y ago
      You just run it again.
      - esafak 1y ago
        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.
      - saagarjha 1y ago
        I can’t always do this.
      - ninkendo 1y ago
        $ 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.

esafak 1y ago

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.

SSLy 1y ago
forever i've been doing the grug brain way of copying the output to notepad++/sublime-text
ludsan 1y ago
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`
OskarS 1y ago
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.
- badosu 1y ago
  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.
Geezus_42 1y ago
|grep or |less
- esafak 1y ago
  Not after it's run you don't.
  - Geezus_42 1y ago
    You just run it again.
    - esafak 1y ago
      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.
    - saagarjha 1y ago
      I can’t always do this.
    - ninkendo 1y ago
      $ 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.