Hi there, nice idea and thanks for sharing.

I was just wondering what is the additional value over just using, tmux and pre-stored pane configurations. From the screenshot in the GitHub repository, I don't see any additional value for me. Will this allow, like, floating panes?

I'm just using tmux with some custom key configurations and with what tmux offers out of the box I'm pretty happy.

▲

saysjonathan 4 hours ago | parent | next [-]

For me, personally, the value was in have something similar to a window manager for the terminal. As I was constantly spawning, killing, and reorganizing panes, a tiling-based approach gave me more control over my terminal and allowed me to perform complex operations without having to memorize or execute multiple commands. My use of a terminal is not static and therefore having a more dynamic option made my life easier.

This is really just a personal project that I wanted to share in case others might like to try it.

I will add that, especially at the time of creation, I was heavily in the 'unix is my IDE' camp. A terminal window manager was a logical next step to that notion. As someone called out below, I even used `ed` as my main editor for a while (which was as bad as it sounds).

▲

ghshephard 2 hours ago | parent [-]

I'm intrigued - as tmux has been my window manager for my desktop for 10+ years now ( I typically have 80-100 different windows/panes in play by the end of any given week, where I take time to close down all sessions that aren't still in progress).

I'm wondering what the difference is between this and just tmux basic environment - which already has a lot of pane / window management. What's the key distinction between using tmux and dwm.tmux?

<5 minutes later> - Ah - this is just tmux with some custom config. The window manager is tmux - I would suggest changing the title a bit - maybe something like, "DWM.TMUX - dwm inspired tmux configs. "

	▲	saysjonathan an hour ago \| parent \| next [-]
		I think the key distinction is the consistent layout (main pane + stack) along with keyboard shortcuts to manage. To me it's similar to running vanilla X{11,org} vs using a window manager (hence the name). A vanilla configuration will work just fine but sometimes a constrained or opinionated environment gets more out of your way and better fits your preferred workflow. If you already have a robust tmux workflow with a desired layout (or lack of layout) and custom keyboard shortcuts then this may not work for you. It's just one way to manage panes/windows in tmux that I hadn't seen before and different from the usual ad hoc methods. Like most window managers, I think it's all preference. What're your current preferences for pane layout, window management, etc? Do you always create/layout panes in the same way or is it situationally dependent?
	▲	saysjonathan an hour ago \| parent \| prev [-]
		It's not just configs though, as there is some logic implemented via shell that could not be handled entirely in configs. "Window Manager" was chosen as it the logic imposes a specific layout without necessarily preventing you from using other configuration options. It's almost solely layout management and keyboard shortcuts to assist.

▲

ghshephard 2 hours ago | parent | prev [-]

For Floating Panes - see: https://github.com/lloydbond/tmux-floating-terminal/tree/mas... (if it doesn't work for you on first try - check - https://github.com/lloydbond/tmux-floating-terminal/pull/6)

Love Floating Panes in Tmux - and best part - all the other plugins - resurrect, continuum, etc..) all support floating panes out of the box.

	▲	saysjonathan an hour ago \| parent [-]
		This does have a single floating pane shortcut (in the current directory), using the tmux `display-popup` command.