jcard

4 ms·

1. 1.▲
   by jcard 6y ago

   AFAIK, you'll need to have at least `setw -g mode-keys vi` in your ~/.tmux.conf file to allow tmux to use vi keybindings in copy mode (`Ctrl+b ]`). Make sure to fully exit all tmux sessions and start a new session after making tha
2. 2.▲
   by jcard 6y ago

   Ah! Thanks for pointing that out. That's the piece I forgot about here. iTerm is populating the system clipboard from tmux because of the tmux integration [1]. [1] https://iterm2.com/documentation-tmux-integration.html
3. 3.▲
   by jcard 6y ago

   That's a fair point! The kubernetes example I gave is somewhat contrived, but I will say that I prefer to have whatever resource id I'm working with in my clipboard vs. relying on myself to select the correct one in a tab completi
4. 4.▲
   by jcard 6y ago

   I haven't tried it, but that looks pretty great! Kind of like a TUI version of something like Lens.
5. 5.▲
   by jcard 6y ago

   This should work the same locally & on remote hosts. Tmux doesn't care that you're ssh'd into some host. As long as your system & version of tmux supports copying to the local clipboard, you should have no problems pa
6. 6.▲
   by jcard 6y ago

   Using the tmux vi keybindings to copy and paste between panes is great if you haven't tried it. This copy/paste workflow is really nice for working with kubernetes on the command line. E.g., imagine that you need to delete a kuber