51–60 of 126 posts
Earlier quoted context omitted.
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
https://www.gnu.org/software/screen/manual/html_node/Nethack...
> Changes the kind of error messages used by screen. When you are familiar with the game nethack, you may enjoy the nethack-style messages which will often blur the facts a little, but are much funnier to read. Anyway, standard messages often tend to be unclear as well.
Earlier quoted context omitted.
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.
I'm not sure if zellij can do that, and coming from tmux, zellij was an easy change.
Earlier quoted context omitted.
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!?
I usually never do heavy editing in a tmux window. Rarely I use emacs in a terminal window these days. I use tramp to remote connect and edit comfortably in my X session.
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…
> Removed commands: - nethack https://www.gnu.org/software/screen/manual/html_node/Nethack... > Changes the kind of error messages used by screen. When you are familiar with the game nethack, you may enjoy the nethack-style messages which will often blur the facts a little, but are much funnier to read. Anyway, standard messages often tend to be unclear as well.
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 :)
Earlier quoted context omitted.
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
I used to do training with this. Every student got a private username/password to connect to my laptop where their login shell connected to a specific window (to which only that user had access) in a shared screen session. They each had their own little environment to hack in. Then when we were doing exercises and people got stuck, I would put their screen up on the projector so we could discuss their code together.
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…
Truecolor finally being released is big
I'm wondering if the use of wcwdith() will improve my luck with using UTF-8 characters in my caption and hardstatus lines. I'd like to be using nerdfonts in there but it just makes a mess.
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…
I wonder how many people are using the default b key binding in tmux