71–80 of 126 posts
> 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.
WTF! That was one of my favourite features!!!!
Earlier quoted context omitted.
> Having a modem is a pretty handy thing built into it. in what way?
when I worked in the embedded software industry long ago, I spent lots and lots of time connecting over serial ports to dev boards, using software like Minicom. Being able to do that in screen itself would be neat. Tmux does it.
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…
That conflicts with the standard Emacs binding to move to the beginning of the current line. Many years ago, I switched to C-z instead, on the theory that it is really easy to type C-z C-z when I really want to suspend whatever is currently running.
Pity that (AFAICT) terminals have no concept of Super and Hyper (USB doesn’t know about Hyper, either, but at least X11 does).
Earlier quoted context omitted.
Yeah maddening! But you can remap it. I use this in my .screenrc to make it C-f: escape ^Ff
C-f moves forward a character which is also useful. The easiest to type character that had the least impact I could find was to remap to C-j. Works well in both Dvorak and Qwerty layouts and that's the one emacs shortcut I use so infrequently that I can live with having to type it twice.
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…
Editing with TRAMP, on the other hand, is a pleasure.
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…
The one thing I hate about tmux is that it leaks env vars across instances: # terminal 1, start a fresh first tmux session, which magically spawns a daemon with the same env $ env FOO=bar tmux # terminal 2, start another tmux session, which reuses the daemon's env $ tmux $ echo $FOO bar Try the same with `screen` and you're safe. This is especially annoying when you're using, say, direnv, and project-specific env var…
I just have my terminal emulator spin up tmux when it starts, and I start my terminal emulator from my desktop, so it always runs in a clean environment.
Earlier quoted context omitted.
Truecolor finally being released is big
I'm looking forward to trying this indeed. 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.
Any program has to expect wide, narrow, or an inconsistent mixture of both if font substitutions are invoked. With no actual API to reliably discover a codepoint display width, your best option is to print some candidates and check the cursor position as a heuristic.
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…
The one thing I hate about tmux is that it leaks env vars across instances: # terminal 1, start a fresh first tmux session, which magically spawns a daemon with the same env $ env FOO=bar tmux # terminal 2, start another tmux session, which reuses the daemon's env $ tmux $ echo $FOO bar Try the same with `screen` and you're safe. This is especially annoying when you're using, say, direnv, and project-specific env var…
To anyone to perhaps who has used both a lot: * Are there particular pros and cons to using screen or tmux ? (I'm generally on macOS for work, but never really go into using iTerm2, so that integration isn't a big thing for me personally.) Edit: I mean why use one over the other. I generally use something on the destination host I'm SSHing to in case the network goes sideways.
In that case, try Zellij. I gave it a shot the last time it made the rounds on HN and instantly loved it. Killer feature: mouse scrolling works out of the box.
The only problem is that projects dealing with network stuff require aging just the way wines do. Networks are unreliable and can get into a thousand different states that are a combination of local connection issues, remote issues, input problems, etc etc. I found (when I tried it a year or two ago) that Zellij could handle a decent amount of such weird states, but not all of them. There was noticeably more "stuck" states it could get into.
It was a pleasure to use in every other way, and maybe this has become much less of a problem in the intervening time. I'm pretty sure that Zellij is going to be my one true term mux for the future, just not sure that future has started yet.