Hacker News Reader

Comment by mrweasel | Hacker News Reader

I have to admit I don't like customizing tools like tmux too much. Personally I prefer to just learn and live with the defaults. That mean losing out on some things, but I think it's a good trade off for having thing just work like you expect on random server you sign in to.

Especially something like keyboard shortcuts and leader keys doesn't make sense to change in my mind. It just confuses you when login in to a remote host.

View on HN

I have thought about that. For this same reason I did not remap a lot of keys in nvim, because I still want to be able to use vim wherever I work if that is the only option.

However, I think that creating a simple git repository with rc files and configuration can be used to create a uniform experience across machines.

The git repo idea is fine for some machines, but when I log into a random customers server at 4:00AM to fix some issue that paged me, I'm not spending time cloning a repo to setup neither vim nor tmux, it just has to work.

Also the machine may not actually able to reach out onto the wider internet.

I think it depends on the use case. If I had to do what you do with random machines, I would probably need to be familiar with default tool setups as well

And for me, the most SSH’ing I do these days is into my docker containers and odds are I won’t be opening vim while I’m there.

I do like the repo idea, but I wonder if there’s an easier and maybe faster way to do it over the SSH tunnel

You may be interested in https://www.chezmoi.io/

This exactly. While on the visual side I prettified it a bit over time, Initially I was really tempted to do some major keybind remapping, having used lots of GUI terminals like Terminator in parallel, especially the infuriating h/v splits that I still routinely confuse after years with tmux, but I stopped myself so as not to cripple myself when I log in to anything that has tmux running defaults - and I'm happy with this choice.

Reply on news.ycombinator.com