Live data from Hacker News

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

cockpit.27ae60.com

31–40 of 49 posts

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

#31
post #25
post #23

This looks really nice! It's not for me, though. Maybe I'm not a very good systems engineer, but I've got a decent .tmux.conf. Between writing automation and trying to make sense of the mess I've inherited, I'm constantly splitting, resizing, and re-adjusting my work space to suit the task at hand.

what are the pros and cons to using tmux as opposed to say multiple instances of a terminal emulator split up using ratpoison?

I happen to be a vim user. tmux, vim, vim-tmux-navigator, and some comfortable configurations in .vimrc and .tmux.conf can be a force multiplier for one's workflow. If you like vim, then it makes a lot of sense. If you don't, there's still probably some merit, but, maybe less of an incentive.

I've never used ratpoison, but just read into it. Sounds pretty great, actually. If the key bindings are simple enough, I suppose it could be pretty similar. But, as a sibling comment pointed out, it works most everywhere. Where I go, my configuration comes with me.

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

#34
post #23

This looks really nice! It's not for me, though. Maybe I'm not a very good systems engineer, but I've got a decent .tmux.conf. Between writing automation and trying to make sense of the mess I've inherited, I'm constantly splitting, resizing, and re-adjusting my work space to suit the task at hand.

Thanks. I'm also constantly resizing and re-adjusting my work space for which I have binded keys in my .tmux.conf. Cockpit helps me get started :)

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

#35

There is a bug when you close windows (the round yellow thing remains). Also can you name the windows?

Actually, clicking on the round yellow circle is the way to rename the windows. I will improve the experience in upcoming releases.

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

#37

Nice tool. I suggest showing the script beside the window so it can easily be cut-and-pasted. Browser downloading is a hassle especially with tmux on a remote server.

Thanks. Your point to show the script is duly noted. It is actually a great idea. Let me incorporate the suggestion in upcoming updates.

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

#38

Please try to use a different name this clashes quite with http://cockpit-project.org/ But otherwise it’s a nice tool

Thank you. I have a small attachment to the name ‘Cockpit’. Three years ago, me and my friends, we used to spend quite some time in hacking projects or automating our workflow. It was at that time, we created a a tool called ‘Cockpit’ (https://github.com/27AE60/cockpit) for configuring Terminal workspace in Linux. Over the years, I started concentrating on one terminal. And when I shifted to iTerm2 along with Tmux, I wanted to spend less time in configuring workspace and more on my code. Then, I realized, I end up with similar Tmux layouts for most of my prototypes and I wanted to reduce my time in re-loading the projects. I wanted a visual representation of Tmux and flexibility in terms of scripts instead of installing applications. This tool reminded me of my old project and so, I couldn’t think a better name than Cockpit.

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

#39
post #21

How do you create 3 equal sized horizontal windows with Cockpit?

It is not possible to create 3 equal sized horizontal panes with Cockpit. What I normally do is, create three horizontal splits in Cockpit and in tmux, I use `leader-key space` which makes tmux cycle through available layouts, and in one of them is equal sized horizontal windows.

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

#40
post #32

This is awesome. Side note, you may want to rename your project to avoid a clash with kubernetes' cockpit UI for kubernetes cluster monitoring.

Thanks. I've received a similar comment in this thread regarding 'Cockpit' name conflict. I have explained my reasons in reply to the comment by @recentdarkness
Post reply on HN