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

Show HN: Cockpit – create tmux panes and windows with ease

cockpit.27ae60.com

Post reply on HN
Print view View original

1–10 of 49 posts

Re: Show HN: Cockpit – create tmux panes and windows with ease

#3

Post by pavel_lishin »

catern wrote: post #2

It's quite an indictment of the current state of our tooling (not just tmux) that such an application as this is necessary. Why isn't it easy to configure this in tmux itself, and persist the resulting configuration?

It's already simple to split panes in tmux, but the ability to persist them sounds like a good Hacktoberfest project.

Re: Show HN: Cockpit – create tmux panes and windows with ease

#4

Post by unk »

pavel_lishin wrote: post #3
catern wrote: post #2

It's quite an indictment of the current state of our tooling (not just tmux) that such an application as this is necessary. Why isn't it easy to configure this in tmux itself, and persist the resulting configuration?

It's already simple to split panes in tmux, but the ability to persist them sounds like a good Hacktoberfest project.

this has already been solved by several plugins. this one works well:

https://github.com/tmux-plugins/tmux-resurrect

Re: Show HN: Cockpit – create tmux panes and windows with ease

#5

Post by rhinoceraptor »

catern wrote: post #2

It's quite an indictment of the current state of our tooling (not just tmux) that such an application as this is necessary. Why isn't it easy to configure this in tmux itself, and persist the resulting configuration?

The defaults are a little funky but they’re easy enough to change. I have mine so prefix+s splits horizontally and prefix+v splits vertically. And then prefix+(H,J,K,L) resizes.

Re: Show HN: Cockpit – create tmux panes and windows with ease

#7

Post by pjungwir »

catern wrote: post #2

It's quite an indictment of the current state of our tooling (not just tmux) that such an application as this is necessary. Why isn't it easy to configure this in tmux itself, and persist the resulting configuration?

This doesn't let you persist ad hoc setups, but I have a `~/lib/tmux-code` file that I source from `~/.bash_profile` with entries like this:

    function ins-code {

      env_name=code
      long_name=insurance
      short_name=ins
      tmux_session=${short_name}-${env_name}

      if tmux list-sessions | grep ${tmux_session}; then
        tmux attach-session -t ${tmux_session}

      else
        cd ~/src/${long_name}/backend/app/models && \
        tmux new-session -d -s ${tmux_session} && \
        tmux rename-window -t ${tmux_session}:1 models

        cd ~/src/${long_name}/backend/app/controllers && \
        tmux new-window -t ${tmux_session}:2 -n controllers

        cd ~/src/${long_name}/backend/app/views && \
        tmux new-window -t ${tmux_session}:3 -n views

        cd ~/src/${long_name}/backend/app/assets/stylesheets && \
        tmux new-window -t ${tmux_session}:4 -n css

        tmux select-window -t ${tmux_session}:1 && \
        tmux -2 attach-session -t ${tmux_session}
      fi
    }
Then I can just say `ins-code` and it will either launch a new session or attach if it already exists.
Post reply on HN