61–70 of 126 posts
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
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…
I would recommend enabling tab-bar-mode instead for this – it’s in Emacs core, and the tabs are really “numbered window configurations” that act very similarly to what screen/tmux calls “windows”.
I feel Emacs frames are in some ways more analogous to screen/tmux sessions.
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 ins…
> 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.
https://git.savannah.gnu.org/cgit/screen.git/commit/?id=9109...
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.
An example from man tmux -
"
refresh-client -t/dev/ttyp2
rename-session -tfirst newname
set-option -wt:0 monitor-activity on
new-window ; split-window -d
bind-key R source-file ~/.tmux.conf \; \ display-message "source-file done"
"
Screen has no equivalent besides manually using the keybinds.
I believe tmux has some better mechanics around the attach/detach but it eludes me atm what was better.
Basically what made me switch in the first place from screen to tmux was wanting a split window watch compile and a logfile to run automatically with one command.
Hard with screen and easy with tmux.
Meanwhile there's rock solid free software, just chugging along for longer than the people writing those articles have been alive.
I first started using Screen around '95, it was the nicest way to stay logged in to my ircII session while yielding the vt220 terminal to someone else for a while and going for a drink/smoke/walk.
Used it ever since, from terminal multiplexing to daemonizing services at a shoestring startup. I've used just a tiny subset the features I know it has, and probably don't know of many more, but it has served me well over the years.
Congrats on the release!
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.
> Are there particular pros and cont to using screen or tmux If you mean vs. not using screen or tmux, the pros to using (among many) are: 1) you get plural terminals in one "window" (xterm, remote ssh session, etc.) that you can switch between with hot-keys. This has a larger advantage for remote ssh sessions, where one ssh connection can be used for plural remote terminals, than it does locally where you could simp…
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…
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