>>914 You probably won't need it unless all of your graphical programs go missing and you need to use TTY. I use tmux because I don't have the any of the things you talked about

>>914 Simple: you want to have a service running in the background that's not a daemon For example, transcoding video with ffmpeg might take a very long time. If you end up closing your terminal for whatever reason during that and your session isn't in screen or tmux, it's gone and you have to start from scratch

>>915 Im not sure what you mean even if you don’t use a window manager most default terminals support this kind of features even on gnome and you aren’t using a minimal terminal unless it’s used with a minimal tiling window manager >>921 Im pretty sure the nohup and disown command can do that without a terminal multiplexer

>>921 nohup cmd & or cmd & disown (but disown does not redirect the command output by itself)

>>914 My terminal doesn't support multiplexing so I end up using tmux as a workaround. It also allows me to keep my sessions alive and accessible from elsewhere with ssh.

do you really need tmux? your shell probably has good enough job control features, at least on linux: ctrl+z stops a foreground job jobs lists all the active processes in that terminal bg restarts a stopped job (in the background) fg brings a process to the foreground, and restarts it if it was stopped you can use the job number (from the jobs list) preceded by '%' with bg, fg, disown, etc. for example fg %2

you can run tmux as a daemon and things you run won't die together with x which likes to die alot. nohup is bullshit because it saves output right in your ass. with tmux it's just a matter of reconnecting to the session. i use urxvtd though, because i got sick of overbloated gtk/qt interfaces that don't let me fucking press f1 while messing around with my kernel config

in ~7 years of using linux openrc, x and either dwm or my own wm (no name yet) I have experienced maybe 3 xorg crashes. what do you people do to make xorg crash I guess you could ctrl+alt+f2 and use a different tty for the daemons

I do nothing at all, the screen just randomly goes blank. It only happens once in a while though

>>914 There exist much better alternatives, such as [Alt]+[F*], gpm, dvtm and abduco.

>>981 it's significantly better now but a few years ago just launching minecraft on nvidia was enough for me

>>997 abduco is nice, I use a4[1] instead of dvtm because it's lighter and I find the UI a it more pleasing. Also, it actually seems to handle text wrapping better than dvtm. [1] https://github.com/rpmohn/a4

i don't use tmux as i am a gnu screen loser but some pros are - using it on a vps. i just reattach the screen instance and all of my work is still there. - have one terminal window over several - i like to do work in the tty as less power usage and distractions - screen + emacs -nw is a nice combo - i use xterm

>>1003 1.why do you use an old ass terminal 2.emacs can have multiple windows and buffers even in the terminal it doesn't need screen or tmux 3.there are terminals that support tabs and split screen (kitty)

>>1162 >>914 when you rely on a terminal emulator to multiplex terminals for you, you are doing just that: relying on the terminal EMULATOR itself programs like tmux and zellij function via software that interacts with the terminal itself, they don't need the external terminal emulator to manage that for them fundamentally more simple, powerful, and portable

>>1169 >Abstracting out the terminal's protocol to a library >Or using an already existing GUI framework (such as godot) Terminal emulators are superior, stop it with the autism. If you were as autistic as you think you'd say writing to COMI ports is the GLOBAL interface, virtually all motherboards support that shit