I’ll look into that, I’m currently just using cross term, which was enough to pass my rudimentary tests of nyancat. I’ll have to create some form of test suite to chuck various inputs at it and confirm it all works correctly.

Its definitely not intended to replace screen or be better, that would require a lot more features and work that I just dont want to do. Its for fun/scratching an itch.

I started it originally when I had issues with screen and permissions issues. The main branch is what I actually use, and I use it for running Minecraft servers. Its just an easy way to send commands to stdin of the process. (Stdout connected to regular stdout, stdin connected directly to a Unix socket).

As for tmux, most I’m not that familiar with it, and used screen more.

Well, your point stands regarding alacritty_terminal, but right now, it actually works just fine for that test case:

<img alt="" src="https://programming.dev/pictrs/image/5b496f9b-cc0e-4530-b1d6-445c70990dfa.png">

I suspect once I stop directing the raw input/output to the shell, it might become more important.

My first thoughts was also “Don’t. Clone tmux instead.” But don’t use ctrl-b. It’s a massively awkward and annoying combo on common keyboards. And don’t make it necessary to release ctrl before the second key.

set-option -g prefix C-a
unbind-key "C-b"
bind-key "C-a" send-prefix

I had thought screen was pretty commonly known, but its a tool you can use to background and reconnect to a process, with the child process being completely separated from your shell. So you can ssh into a box, start a process with screen, and then logout, return later and reconnect. (It also does other stuff like read from serial consoles)

Codewise, there isnt a lot there, 3 main files (main.rs, server.rs and client.rs) all weighing in at ~200 lines.

It felt premature to add a readme at this stagr, as I dont see this as a complete thing yet, but I can add a readme later today.

If you’re someone who might use this tool, you’re likely on a system that can run man screen. I agree that readme-s are useful. But just run man screen, find out what the tool is, be done. Otherwise, I think you’re asking the creator to do more work while I suspect you aren’t the target audience.

Yeah, its a bit of a mess, it does so much. The thing I wanted was just the persistent sessions, so probably not gonna go further than that. Of course, the code exists, and someone else is welcome to take it and run with it (I’ll give it a permissive licence eventually).

The name of the branch is probably misleading, its not gonna be better than screen, it was meant to be better than my first attempt.

This is likely to never have any real use outside of my own personal usage.

The README helped a lot, thanks. Just wanted to point out a minor typo, I think the second word under the “Client” section is meant to be the word “client”.