I recently ditched VS Code in favor of Neovim and thanks to Ghostty transition has been a success. As a Mac user I use the cmd key in tons of shortcuts and it just worked out of the box, no need to send weird escape sequences
Libghostty is coming
51–60 of 275 posts
Re: Libghostty is coming
#52i desperately want to use ghostty but cmd+f support is just such a dealbreaker. excited about this development though!
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.
Re: Libghostty is coming
#53I really want a little adapter that can plug into a monitor to make it a dumb terminal. Instantly on, no full OS, just a VT100 or something. I've looked into it with a PiZero and some HATs but I'd like something made by smarter people. This would be perfect for that. Ideally just some dip-switchs to set the terminal to emulate and set the display resolution.
Then what would you do? serial port? ssh? what is your terminal connected to if you don’t have an OS?
Serial port or serial port over "ethernet"[1] (technically it's 8p8c[2]).
My router doesn't have a video port, but it does have a dummy terminal port. I had to scrounge a video card for my server to set it up, but it does have a serial port [3]. So that would have been nice.
Also would be nice for a modern remake of dumb terminal with abandoned monitors.
[1] https://www.cabling-design.com/references/pinouts/EIA-TIA-56...
Re: Libghostty is coming
#54i desperately want to use ghostty but cmd+f support is just such a dealbreaker. excited about this development though!
You could run tmux inside it and bind cmd f to copy-mode + /
Re: Libghostty is coming
#55i desperately want to use ghostty but cmd+f support is just such a dealbreaker. excited about this development though!
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.
Re: Libghostty is coming
#56> excellent feature compatibility such as parsing Kitty Graphics Protocol or Tmux Control Mode, and more
Oh oh oh!!!
> https://github.com/ghostty-org/ghostty/issues/1935
awww...
(while ghostty can parse Tmux Control Mode stuff, it doesn't actually implement the full feature. My dependence on iTerm2 remains...)
Re: Libghostty is coming
#57How does this compare to https://gitlab.gnome.org/GNOME/vte/ ?
For that matter: how does it compare to libvterm (https://www.leonerd.org.uk/code/libvterm/)?
Re: Libghostty is coming
#58> excellent feature compatibility such as parsing Kitty Graphics Protocol or Tmux Control Mode, and more Oh oh oh!!! > https://github.com/ghostty-org/ghostty/issues/1935 awww... (while ghostty can parse Tmux Control Mode stuff, it doesn't actually implement the full feature. My dependence on iTerm2 remains...)
Ghostty has the capability to parse Tmux control mode (and this blog post is about libghostty-vt). Ghostty the GUI is missing the capability to map that to GUI elements. But Ghostty understands Tmux control mode today: https://github.com/ghostty-org/ghostty/blob/main/src/termina...
Re: Libghostty is coming
#59Re: Libghostty is coming
#60i desperately want to use ghostty but cmd+f support is just such a dealbreaker. excited about this development though!
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