4 ms·
His solution of using `-L` to create a new named socket for each server does not seem cumbersome to me. I usually run `tmux attach-session` only once per day, s
by anthomtb 4y ago
His solution of using `-L` to create a new named socket for each server does not seem cumbersome to me. I usually run `tmux attach-session` only once per day, so an additional argument would not be a major cognitive load. And I'd imagine most people use shell aliases for that sort of thing anyways (I probably should).
- rudolph9 4y agoThis is actually what I do every time. I thought it was standard practice.
- jhatemyjob 4y agoyea i always do `tmux new -s dev` to start one and `tmux attach -t dev` to attach correct me if im wrong but it seems like i can just do `tmux new -L dev` and `tmux attach -L dev` which is actually better than my old muscle memory. its a win-win for me edit: actually jk it doesnt work. meh who cares i always put my env vars in ~/.profile its weird how OP doesnt mention that at all
- deleted 4y ago[deleted]
- Jtsummers 4y agoThe -L option is for tmux so it needs to go before the command as `tmux -L dev new` and `tmux -L dev attach`.
- jhatemyjob 4y agooh. awesome! thank you kindly edit: damn, now i have to write a custom script for `tmux list-sessions` #!/bin/bash for L in $(ls /private/tmp/tmux-501); do echo $L tmux -L $L list-sessions done honestly at this point it isnt even worth it. i dont wanna have an extra script like this. ill just put my env vars in ~/.profile
- cerved 4y agoI guess I would do something like `-L $$ `