top | item 41683197

How to avoid running tmux in VSCode-terminal

2 points| cuanim | 1 year ago |rakim.bearblog.dev

5 comments

order

pavel_lishin|1 year ago

> If you're like me and have a default attach-session setup in your ~/.zshrc

Serious question, as a user of tmux - why would you want your new terminal windows to automatically connect to tmux every time?

boffinAudio|1 year ago

Consistency and permanence. There is much utility to be gained in having a terminal that you can always re-connect to, from different networks and indeed different client computer terminals, and yet still maintain your remote state on the system running tmux.

For example, I regularly run jobs that can go on for hours and hours, without much predictability - so using tmux means I can start the job at work, but then check in on it later on my iPhone during the commute back home, and then from my home-office system later, without fuss.

Using tmux this way makes your remote host a reliable development partner instead of giving you hassles if you lose your connection/need to relocate to another network provider/use a different terminal client than the one you started at the office, etc.

3np|1 year ago

Doing the same (though new-session rather than attach) - tmux is just part of my everyday workflow. I use multiple tabs/panes/buffers/windows /splits/whathaveyou constantly where I guess you may be relying on your terminal emulator or window manager for the same features?

To me this reads like "As a user of X11, why would you want your session to start a desktop environment on login?"

Because the first and only thing I'd do unless something is broken is run [startx/tmux] anyway.