Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Shpool, a Lightweight Tmux Alternative

github.com

Post reply on HN
Print view View original

171–180 of 201 posts

Re: Show HN: Shpool, a Lightweight Tmux Alternative

#171

Post by frankjr »

cryptonector wrote: post #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.

> tmux/screen do not break copy-paste

Tmux breaks interacting with the clipboard so much that it has its own dedicated Wiki page dealing with all of the different issues and settings: https://github.com/tmux/tmux/wiki/Clipboard

Re: Show HN: Shpool, a Lightweight Tmux Alternative

#172

Post by remram »

slt2021 wrote: post #124
remram wrote: post #117

Earlier quoted context omitted.

You were talking about replacing the terminal with notebooks, I assumed you meant for terminal tasks. If you are using notebooks for notebook coding tasks then fine but what does that have to do with tmux?

There are two ways to run shell commands: 1. Jupyter has terminals feature in addition to notebook (New->Terminal instead of New->Notebook). You can run any number of terminal sessions, they will be persisten like tmix and each open in separate browser window. They are also shareable and easy to collab, so you can toss the terminal URL to your colleague to let him continue where you left off, or let him monitor stdou…

I see, you're using the JupyterLab Terminal as a terminal, I misread. Apologies.

Re: Show HN: Shpool, a Lightweight Tmux Alternative

#173

Post by lanstin »

remram wrote: post #98
chaps wrote: post #76

Earlier quoted context omitted.

shpool doesn't allow splitting screens either! But I guess in my head, screen is largely for resuming a shell connection on a remote host while tmux is a window splitter.

Both of them are both of those things.

I always get scared when I accidentally have two shell sessions visible at once in tmux. I immediately exit one. I suppose I should read a bit on it. When I want side to side comparisons I go to the shell running emacs and do it there (post vague because I never remember the different words for windows and panes and shells etc these different apps use.)

Re: Show HN: Shpool, a Lightweight Tmux Alternative

#178

Post by chaps »

e12e wrote: post #174
chaps wrote: post #164

Earlier quoted context omitted.

Okay, but is it actually good?

Screen vertical split works fine.

Let me rephrase that -- is it good enough to use 100% of the time you're in a terminal? Cause that's what I do with tmux and it works phenomenally. Haven't had a similarly good experience with screen before, but I'm open to being wrong.

Re: Show HN: Shpool, a Lightweight Tmux Alternative

#179

Post by remram »

lanstin wrote: post #173
remram wrote: post #98

Earlier quoted context omitted.

Both of them are both of those things.

I always get scared when I accidentally have two shell sessions visible at once in tmux. I immediately exit one. I suppose I should read a bit on it. When I want side to side comparisons I go to the shell running emacs and do it there (post vague because I never remember the different words for windows and panes and shells etc these different apps use.)

tmux has a server containing sessions containing windows containing panes. Screen has sessions, windows, and panes (which it calls regions).

I recently finally switched from screen to tmux and I found that it's pretty seamless (especially because I use vi keybinds in tmux still). Some machines at work don't have screen anymore.

Re: Show HN: Shpool, a Lightweight Tmux Alternative

#180

Post by qi437103 »

mkhnews wrote: post #145
ethanpailes wrote: post #136

Earlier quoted context omitted.

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.

It's not i3/tmux, but a similar problem exists for vim/tmux, where the vim window management keys will conflict with tmux's.

And there's https://github.com/numToStr/Navigator.nvim that unifies the keys by letting the outside layer (tmux) always ask the inside layer (vim) before any movements.

Although that is indeed a lot more setup. But works pretty well.

Post reply on HN