Live data from Hacker News

GNU Screen 5.0 Released

savannah.gnu.org

31–40 of 126 posts

Re: GNU Screen 5.0 Released

#31
post #23
post #19

My `~/.screenrc` has a comment at the top, which says I created it on "05-May-1994" (before I switched to ISO 8601 dates). I'm no longer using `screen` on an HP 2392A dumb terminal and PP 14.4kbps modem. But `screen` is still coming in very handy, when working on servers, and for some kinds of developing&running long-running programs on the workstation laptop. It's also fun, on the occasion that you introduce `screen…

There are bugs. But Screen itself is running locally and per-user? I could imagine attacking from one tab (window) interacting with another tab but then the user runs already a harmful application. I worry more about everything containing Electron or similar built “web applications”.

Screen has multiuser features, two people can share the same screen session

Re: GNU Screen 5.0 Released

#32
post #5

Finally :) I’m waiting for a year that we don’t have to push Escape twice in Vim/Neovim. Some mouse emulation was catching it. https://savannah.gnu.org/bugs/?57748 https://superuser.com/questions/1675761/why-does-gnu-screen-... I should write the developers a note with thanks :)

I would advice to use tmux. It's not worth it to keep fighting with that issue.

Take this from someone that used GNU Screen from ca 2002-2024. Yep, I just recently switched, because of truecolor and because of the issue you mention.

Of course GNU Screen is in my heart. Where it stays.

Re: GNU Screen 5.0 Released

#33
post #22
post #8

Earlier quoted context omitted.

> Ctrl+a from my cold dead fingers As someone who uses `set -o emacs` I cannot possibly imagine pressing C-a C-a to go to the beginning of the line Also, as an iTerm2 user: the integration with tmux control mode (tmux -CC) is just amazing for the way I use tmux

Yeah maddening! But you can remap it. I use this in my .screenrc to make it C-f: escape ^Ff

I map mine to C^] which I find to be a good balance between easy to type and not conflicting with other tools

Re: GNU Screen 5.0 Released

#34
post #7

I used to be an avid user of screen, then later on tmux. My terminal directly launched a session upon opening. But something that was always bugging me was the "ssh unawareness" - I've always wanted to be able to do splits on the remote end, but that was simply not possible without nesting sessions. Now, I've switched my terminal to wezterm, which fills all my multiplexing needs, as it supports this exact "remote-or-…

I started with screen and Terminal.app, then I switched to tmux and iTerm. Now i"m on wezterm and zellij. Works great! Still, I'm happy to see work on screen continuing.

What do you use Zellij for that isn't covered by Wezterm? I used Zellij in Alacritty and now in Foot, but recently tried Wezterm and the features it offered really seemed to match what Zellij offers. I didn't need two ways to do splits, tabs, sessions so I'm back to Foot/Zellij, but was just curious to your use-case.

Re: GNU Screen 5.0 Released

#35
post #12

Screen, tmux, et al. are great. But here's another way of approaching the same problem: Emacs can serve as a superlative terminal multiplexer if you're willing to give it a shot or if you're already an Emacs user, but do not want to use Emacs's TRAMP (remote editing) functionality: 1. Emacs can run as a server, so you can run it on your remote servers and connect to it with `emacsclient' via SSH. This has the added a…

All you say is true... But I still run emacs in screen :P

I know I should run a single emacs instances and use projectile or whatever to switch context, but for me it's just easier to run many screen sessions (with descriptive names via `screen -S my-session-name`, attaching via `screen -r my-session-name`) and an emacs instance for each screen session.

One day I'll improve my emacs-fu and I'll use a single emacs instance for everything.

Re: GNU Screen 5.0 Released

#36

Earlier quoted context omitted.

I wonder how many people are using the default b key binding in tmux

No emacs user. I use p in screen and tmux as prefix key. I usually prefer tmux.

Your use of p surprises me if you don't use b for emacs reasons! How do you go up a line!?

Re: GNU Screen 5.0 Released

#37
post #21

Looks like a few QoL improvements and bug fixes. Nothing disruptive that would normally come with a major release version. Looks like you can set a password on it now, which is cool (though I personally like having linux perms govern access to my screen/tmux). Multiinput sounds interesting as well, though in the past that was a feature I thought I'd love to have, but once I had I never use. I'm glad to see Screen is…

Why did you switch to tmux? It seems to me that screen is more ubiquitous, and has more features. Having a modem is a pretty handy thing built into it.

> Having a modem is a pretty handy thing built into it.

in what way?

Re: GNU Screen 5.0 Released

#38
post #21

Earlier quoted context omitted.

Why did you switch to tmux? It seems to me that screen is more ubiquitous, and has more features. Having a modem is a pretty handy thing built into it.

Not GP, but ~15 years ago tmux offered a lot better screen splitting options and a few other features that screen did not. That's why I switched. I did continue to use screen at work because it was ubiquitous, but then sysads started installing tmux as well and that was no longer an issue. screen has improved a lot since then, but it lagged behind substantially for years.

Yes, this is exactly why I switched as well.

Also a benefit was actually being able to understand and edit my conf file without having to RTFM everything. Certainly not a reason to switch by itself, but a nice plus.

Re: GNU Screen 5.0 Released

#39
post #23
post #19

My `~/.screenrc` has a comment at the top, which says I created it on "05-May-1994" (before I switched to ISO 8601 dates). I'm no longer using `screen` on an HP 2392A dumb terminal and PP 14.4kbps modem. But `screen` is still coming in very handy, when working on servers, and for some kinds of developing&running long-running programs on the workstation laptop. It's also fun, on the occasion that you introduce `screen…

There are bugs. But Screen itself is running locally and per-user? I could imagine attacking from one tab (window) interacting with another tab but then the user runs already a harmful application. I worry more about everything containing Electron or similar built “web applications”.

For example, you start a `screen` session, and within one of those `screen` windows, you SSH to an untrusted remote system, and that remote system can then send arbitrary bytes to be interpreted by `screen`. If there's a bug, it's potentially remote system having arbitrary code execution capability on your local system that's running `screen`, under your UID, and then escalate from there.

Re: GNU Screen 5.0 Released

#40
post #8

Looks like a few QoL improvements and bug fixes. Nothing disruptive that would normally come with a major release version. Looks like you can set a password on it now, which is cool (though I personally like having linux perms govern access to my screen/tmux). Multiinput sounds interesting as well, though in the past that was a feature I thought I'd love to have, but once I had I never use. I'm glad to see Screen is…

> Ctrl+a from my cold dead fingers As someone who uses `set -o emacs` I cannot possibly imagine pressing C-a C-a to go to the beginning of the line Also, as an iTerm2 user: the integration with tmux control mode (tmux -CC) is just amazing for the way I use tmux

As someone who also uses emacs, I type C-a a so often that sometimes I do the same in emacs and it leaves an extra a. It's quite rare though.
Post reply on HN