Hacker News Reader

Comment by trial3 | Hacker News Reader

i desperately want to use ghostty but cmd+f support is just such a dealbreaker. excited about this development though!

It's on the roadmap: https://ghostty.org/docs/install/release-notes/1-2-0#roadmap

oh, incredible! i'll keep my eyes peeled and will be switching to it from iTerm the moment it's available

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.

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.

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

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`

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.

|grep or |less

Not after it's run you don't.

You just run it again.

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.

I can’t always do this.

    $ 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.

You can map something like cmd+shift+f to open the entire buffer in your default text editor, this has been sufficient for a lot of folks - myself included - while we wait for native scrollback search to land.

wow yankcrime describing a literal vi yank crime. i'll give it a try this week, that's helpful

I started using it months ago and don't miss that so much, if I really can't rerun the command and pipe it to less/grep. I'll just use the mouse to copy it to the clipboard and then run `xclip -o` (linux) or `pbpaste` (mac) and pipe it to grep. I know there's a keybinding for putting the buffer in a file, but copying with the mouse is faster than finding it.

Also, not sure if this is by default or it picked it up from my old iTerm2 configuration, but cmd+shift+up/down navigates through prompt lines so it's easy to find the start of a long command. My PS1 in zsh is:

    PS1='%1~ %F{green}»%f '

Can someone explain why this was not one of the first features added? Who doesn't want to search their history? There must be some complication.

Mitchell raised the issue himself two years ago: https://github.com/ghostty-org/ghostty/issues/189

probably because you never volunteered to code it up.

but really not all features can make it in 1.0

As someone who lives in the terminal, I can't say I've ever had the need to do that. It's only by reading the comments that I've realised that there's no search in Ghostty.

Guessing its "hard to do it right".

You could run tmux inside it and bind cmd f to copy-mode + /

> i desperately want to use ghostty

Is there any particular reason?

Curiosity?

iterm2 is slow, uses a ton of memory, and keeps adding weird bloat/AI garbo

Reply on news.ycombinator.com