Tmux allows you to set up multiple panes in your terminal that keep running in the background. Therefore, if you disconnect from a remote machine, scripts running in tmux will not be killed. We tend to run experiments across many tmux panes (especially overnight).
Does no one use suffix & disown which sends a command to a background process that doesn’t depend on the ssh process, or prefix nohup which does the same thing? You have to make sure any logging that goes to stdout goes to a log file instead (and in this way tmux or screen are better)
Your remark about uv: forgot to mention that it’s effectively a poetry replacement, too
Like htop: btm and btop are a little newer, nicer to look at
Also for json: jq. cat file.json | jq for pretty printing json to terminal
I didn’t learn about disown or nohup until recently, because there was no impetus to, because I’d been using tmux. (My workflow also otherwise depended on tmux; when developing locally I liked its method of managing terminal tabs/splits.)
Does no one use suffix
& disownwhich sends a command to a background process that doesn’t depend on the ssh process, or prefixnohupwhich does the same thing? You have to make sure any logging that goes to stdout goes to a log file instead (and in this way tmux or screen are better)Your remark about uv: forgot to mention that it’s effectively a poetry replacement, too
Like htop: btm and btop are a little newer, nicer to look at
Also for json:
jq.cat file.json | jqfor pretty printing json to terminalI didn’t learn about disown or nohup until recently, because there was no impetus to, because I’d been using tmux. (My workflow also otherwise depended on tmux; when developing locally I liked its method of managing terminal tabs/splits.)