Live data from Hacker News

Show HN: Boo – Screen-style terminal multiplexer built on libghostty

github.com

21–30 of 31 posts

Re: Show HN: Boo – Screen-style terminal multiplexer built on libghostty

#21

Installed using the curl-to-bash on Sequoia and I’m getting “error: ReadOnlyFileSystem” on ‘boo new’. Can’t see any open issues on gh and nothing in the readme. Definitely interested in something like this - love ghostty and I’ve been finding Zellij a bit crashy recently (plus I don’t really need tabs).

How have you been using Zellij? It's been working great for me

Re: Show HN: Boo – Screen-style terminal multiplexer built on libghostty

#22

Earlier quoted context omitted.

this is incorrect. you can have multiple clients using screen -x instead of screen -a

I didn't say you couldn't have multiple clients, I said clients and servers are the same process forked. Or did someone add distinct client/server support to screen finally? I know theres a lot of stuff bolted onto screen over the years but I wasn't aware they dropped forked servers for the tmux model...

Did a bit of digging; the first client gets forked to create the "server". The forked server then detaches and runs in the background. You're right that -x creates an entirely new, separate client process, unrelated to the OG client or the forked server.

Without -x though it works as originally described.

Edit: gnu screen 1.0 was originally released in 1987. The -x flag was released in screen 3.0 in the 90s. TIL

Re: Show HN: Boo – Screen-style terminal multiplexer built on libghostty

#23
post #17

Earlier quoted context omitted.

Can you please not post AI-generated or AI-edited comments to HN? It's not allowed here - see https://news.ycombinator.com/newsguidelines.html#generated and https://news.ycombinator.com/item?id=47340079 . Of course, it's impossible to know for sure what was LLM processed or not, but some of your posts (like this one) are getting classified that way.

Apologies, half of this indeed was. As I was iterating on the README this seemed apt, but I will refrain!

Appreciated! The community feels strongly about this.

Re: Show HN: Boo – Screen-style terminal multiplexer built on libghostty

#25
This is super cool. I've been a heavy tmux user for a long time and using it more with my coding agent sessions and prefer ghostty. What was the biggest challenge when it came to building a multiplexer directly on top of libghostty that you ran into?

Re: Show HN: Boo – Screen-style terminal multiplexer built on libghostty

#29
Slightly off-topic:

I currently use tmux. Not because I need to multiplex shells in a remote server, but because I like to have my sessions persisted in my local machine. Even between reboots (technically not the same session, but the same tabs and splits I had). I currently have that with tmux and a tmux plugin that restores my sessions. But I think that tmux is overkill for this. And if I'm in a tmux session, then I can't use my terminal emulator's native tabs and splits. Does anyone have a recommendation of how to handle only terminal sessions on Linux?

Re: Show HN: Boo – Screen-style terminal multiplexer built on libghostty

#30

Slightly off-topic: I currently use tmux. Not because I need to multiplex shells in a remote server, but because I like to have my sessions persisted in my local machine. Even between reboots (technically not the same session, but the same tabs and splits I had). I currently have that with tmux and a tmux plugin that restores my sessions. But I think that tmux is overkill for this. And if I'm in a tmux session, then…

This is the exact use-case Boo is made for!
Post reply on HN