3 ms·
I like that. I don’t want to use tmux (and I don’t when I’m working on my local machine), but I can’t escape it when SSHing. I could ssh to a ton of sessions, b
by Graziano_M 11mo ago
I like that. I don’t want to use tmux (and I don’t when I’m working on my local machine), but I can’t escape it when SSHing. I could ssh to a ton of sessions, but then I 1. Have to remember their names 2. Can’t easily create a new pane (on the remote host) for some short task and 3. Need yet another solution for restoring my pane layout for when my client restarts.
Maybe I’ll try the session name thing, I just foresee it being annoying. Do you see your tool as a shpool replacement?
- fragmede 11mo agoDon't give them useful names, just call them 1 or 2 or asdf and let your brain do the mapping.
- Graziano_M 11mo agoI also (coincidentally) just started using OP's coder, and that also sets up ssh config to use special wildcard hosts, and unfortunately 'hogs' the config (it threatens to trash any changes to the coder section).
- qudat 11mo agoYes this completely replaces `shpool`. I totally understand your concerns for creating new terminals for short tasks. I generally lean towards `nvim` terminal buffers to solve that issue. Or I have a `term` session open that I can quickly go to for random terminal commands that don't belong to a project.