←back to thread

538 points todsacerdoti | 1 comments | | HN request time: 0.208s | source
Show context
gertlex ◴[] No.44358402[source]
I really appreciate this method of sharing workflows. Well catered to the audience. Actually was slightly hoping there'd be sound to the vid, too, but reading the list of actions after-the-fact was reasonable. I learned a few things I could do and/or approach differently in my own flows.

You mentioned the arcane keyboard shortcuts of tmux. I'm curious if you or others here have tried/use byobu (which I think of as a wrapper around tmux, basing most commands on the F# row). I was shown it a decade ago and have used it since (after a couple prior years of primitive tmux use).

replies(1): >>44358456 #
jynelson ◴[] No.44358456[source]
glad you've enjoyed it :) i was trying to find something that was clear while still being easy to skim.

> You mentioned the arcane keyboard shortcuts of tmux.

oh, i've remapped almost all the shortcuts in tmux. `ctrl-k` is not the default prefix and `h` is not the default key for "select pane left".

i haven't tried byobu but from skimming the readme i expect it not to have a ton other than nicer default key bindings, and i'd rather not add more layers to my terminal.

replies(1): >>44361447 #
1. gertlex ◴[] No.44361447[source]
Gotcha! My main reason for advocating for byobu is it's more beginner/defaults-friendly. I've never customized it, nor fully learned its hotkeys.

In my case, we have dev robots with byobu installed, and it's much easier to train non-SW engineers (i.e. HW folks, technicians, QA) on its use (primarily for remote session persistence).

(This is also why I don't do much/heavy customization these days: for uniformity between local and robot machines...)