Live data from Hacker News

Show HN: Shpool, a Lightweight Tmux Alternative

github.com

141–150 of 201 posts

Re: Show HN: Shpool, a Lightweight Tmux Alternative

#141

I super duper highly recommend iterm2 (macos) + its integrated tmux support. It was relatively popular in my circles at google when I was there. It comes with this tool’s benefit of native scrolling/cp paste PLUS the huge benefit of “right click to split vertical/horizontal”.

can I still use my keyboard shortcuts for switching between sessions and windows within the session?

I am much happier with that muscle memory than whatever the iterm shortcuts would be.

Re: Show HN: Shpool, a Lightweight Tmux Alternative

#142

For me tmux is everything. But I have been looking for 2 utilities they may not exist. - tty keystroke router: A program that lets you send keystrokes to different tty's (ideally tmux sessions) but not taking over the actual terminal (so sort of a background application , a daemon that listen to a certain key bind and upon pressing it will route all the keypresses to a certain tty/tmux session. - tty screen real esta…

For the second, might be useful. It's not quite what you asked for; it emulates a two-column virtual terminal within another (virtual) terminal.

If you can extend your terminal window across your two monitors and run `tcvt` within it, that might suit your purposes.

Re: Show HN: Shpool, a Lightweight Tmux Alternative

#143

Earlier quoted context omitted.

It's definitely not a complete alternative, but a surprising number of tmux users are only in it for the session persistence. We did a little internal (criminally underpowered and confounded) survey of some tmux users at google and found that half of them were only really using it for session persistence. I was really surprised by this and thought more people would be using all the slick tiling features that tmux has…

I think there is a whole group of vim + tmux people out there and their primary use case may not be session persistence, but to construct an IDE like environment, which is also my use case.

Note that vim also has windows, tabs and tiling, along with terminals.

Re: Show HN: Shpool, a Lightweight Tmux Alternative

#144
This seems to suffer the same problem as abduco, which is, you better be reconnecting from the same terminal (don't change your termcap). Fine if working from a single machine.

I did notice they have a vt100 emulator, but it's only used for screen restore?

It seems the focus of the tool is for reconnecting from the same machine.

Re: Show HN: Shpool, a Lightweight Tmux Alternative

#145

Earlier quoted context omitted.

Hi. Nice kit. > I couldn't use my normal `i3`/`sway` bindings to switch between terminals inside a tmux session Just curious, what are your normal 'i3'/'sway' bindings that you cannot get to work with tmux ? And what actual terminal program do you use ? Perhaps tmux wants more config than most people care to bother with, but scrollback and copy-paste can be configured just as you like.

If you’re using a tiling window manager your window switch keybindings necessarily conflict between the manager and tmux, since if you configure the same one and then press it while focused on a tmux window, the tiling window manager will override tmux and claim the event. Scrollback and copy paste cannot always be configured as you want. I’ve shared some specifics elsewhere in this thread.

Hi. ok, I get that. Maybe something like A-left to move to next i3 window and A-S-left to move to next tmux window within an i3 window ? Perhaps a tiling window manager with multiple windows combined with tmux dividing some of those windows further into sub-windows isn't an ideal flow.

Re: Show HN: Shpool, a Lightweight Tmux Alternative

#146

"The main way that shpool differs from tmux is that tmux is a terminal multiplexer which necessarily means that it offers session persistence features, while shpool only aims to be a session persistence tool. In contrast to tmux the philosophy of shpool is that managing different terminals is the job of your display or window manager, not your session persistence tool." What if the computer user does not use a window…

Then you can run tmux locally for the multiple windows and then in each window use this if you need to connect remotely to resumable sessions there.

On the other hand if your use case is just windowing on a single host (local only or remote only) then probably stick with tmux.

Re: Show HN: Shpool, a Lightweight Tmux Alternative

#147

Earlier quoted context omitted.

Nohup still attaches to the terminal's stdin/out/err. If the process is known to be non-interactive, redirecting to log files should be sufficient (tail -f to "reattach"). If it does expect interaction, creating a fifo file to redirect stdin from should work, but I've never tested it.

nohub doesn't attach nor redirect the stdin/out/err, it intercepts the HUP signal that apps receive when their controlling TTYs are disconnected. Implying "tail -f $LOGFILE" is akin to tmux reattaching to a console is a stretch.

The standard Unix version of nohup does in fact redirect the output/error streams if they would otherwise go to a terminal. https://pubs.opengroup.org/onlinepubs/009695299/utilities/no... / https://en.wikipedia.org/wiki/Nohup

Re: Show HN: Shpool, a Lightweight Tmux Alternative

#148
> The biggest advantage of this approach is that `shpool` does not break native scrollback or copy-paste.

tmux/screen do not break copy-paste. And that tmux/screen have their own scrollback is a feature.

The selling point for shpool is simplicity, which I appreciate. I need terminal multiplexing, but I might use shpool here and there.

Post reply on HN