I used tmux for about a decade and wrote quite a bit of automation around it, including tmux_super_fingers. But eventually I got frustrated with project sessions being limited to terminal windows. In particular, the browser tabs belonging to those projects were all mixed up in a single browser window.
So I wrote hop[1], which uses sway workspaces instead of tmux sessions. Terminals, editors, browsers, or any other windows really, can now all belong to the same project.
What I hadn't quite anticipated was how liberating it would feel to use the system's own tools - windows, workspaces, clipboard, scrollback, etc. - instead of tmux's alternatives. No more two layers of window management or competing keybindings.
On top of that, hop has proven to be a great fit for working in sandboxed environments. With tmux, sessions are tied to a tmux server running on a particular machine or inside a particular container. With hop, local, containerized or remote (or both) are all allied under one banner.
I realise most folks won't be able to use it - it requires rather extravagant tool choices (notably, sway) - but it's an interesting experiment nonetheless. And it's been working great for me for months now.
[1] artemave/hop
Show HN: I replaced tmux with sway workspaces
1 point · 1 comment
One thing you might be missing is better integration between the local desktop and the remote environment. Things like persistent ssh connections, seamless clipboard sharing (including images), port forwarding and file path translation, so that working remotely feels almost indistinguishable from working locally.
I wrote a session manager[1] to handle all that. Linux/sway/kitty only though.
[1] artemave/hop
artwall - random paintings as wallpapers
One thing I've been missing from my OSX days is Artful - an app that rotated wallpaper through random paintings. Turns out, I like looking at paintings and the concept of lateral learning works well on me - I started to develop both connaissance and taste. However, OSX was terrible in every other way, so I switched to Linux and Sway. Fast forward ten years, thanks to LLMs, I could now recreate a similar thing on Sway. Happy days. But then one day my daughter saw it and said she wanted it too. Since it wouldn't be realistic to get her to use Sway, I needed a desktop environment usable by mere mortals where this could be achieved. KDE Plasma ticked the box and so it was done.
Now, I realise that many people here dislike projects where an LLM did the coding. And I must admit, this is 100% the case - I haven't even read any of it. Full test coverage, type checking and lints give me some modest confidence that the code is not complete garbage, but, ultimately, I have no idea. Having said that, the end result is working well and makes sense (the product of months of iterating and tweaking), has some genuine novelty beyond Artful and thus is worth sharing. So here it is: artemave/artwall
P.S. the demo is recorded on Sway, but it looks and behaves identically on KDE.
2 points · 1 comment
Mentions
I used tmux for about a decade and wrote quite a bit of automation around it, including tmux_super_fingers. But eventually I got frustrated with project sessions being limited to terminal windows. In particular, the browser tabs belonging to those projects were all mixed up in a single browser window. So I wrote hop[1], which uses sway workspaces instead of tmux sessions. Terminals, editors, browsers, or any other windows really, can now all belong to the same project. What I hadn't quite anticipated was how liberating it would feel to use the system's own tools - windows, workspaces, clipboard, scrollback, etc. - instead of tmux's alternatives. No more two layers of window management or competing keybindings. On top of that, hop has proven to be a great fit for working in sandboxed environments. With tmux, sessions are tied to a tmux server running on a particular machine or inside a particular container. With hop, local, containerized or remote (or both) are all allied under one banner. I realise most folks won't be able to use it - it requires rather extravagant tool choices (notably, sway) - but it's an interesting experiment nonetheless. And it's been working great for me for months now. [1] artemave/hop
Show HN: I replaced tmux with sway workspaces
One thing you might be missing is better integration between the local desktop and the remote environment. Things like persistent ssh connections, seamless clipboard sharing (including images), port forwarding and file path translation, so that working remotely feels almost indistinguishable from working locally. I wrote a session manager[1] to handle all that. Linux/sway/kitty only though. [1] artemave/hop
artwall - random paintings as wallpapers One thing I've been missing from my OSX days is Artful - an app that rotated wallpaper through random paintings. Turns out, I like looking at paintings and the concept of lateral learning works well on me - I started to develop both connaissance and taste. However, OSX was terrible in every other way, so I switched to Linux and Sway. Fast forward ten years, thanks to LLMs, I could now recreate a similar thing on Sway. Happy days. But then one day my daughter saw it and said she wanted it too. Since it wouldn't be realistic to get her to use Sway, I needed a desktop environment usable by mere mortals where this could be achieved. KDE Plasma ticked the box and so it was done. Now, I realise that many people here dislike projects where an LLM did the coding. And I must admit, this is 100% the case - I haven't even read any of it. Full test coverage, type checking and lints give me some modest confidence that the code is not complete garbage, but, ultimately, I have no idea. Having said that, the end result is working well and makes sense (the product of months of iterating and tweaking), has some genuine novelty beyond Artful and thus is worth sharing. So here it is: artemave/artwall P.S. the demo is recorded on Sway, but it looks and behaves identically on KDE.