Re:A Quick and Easy Guide to Tmux (2015)
by jrowley on Tuesday October 29, 2019 @10:57PM
(#21394297)
I’m curious, can you share what industries this practice is common, sshing into a protected source code machine?
Re:A Quick and Easy Guide to Tmux (2015)
by taude on Wednesday October 30, 2019 @08:44AM
(#21397051)
I worked in Security for a bit (that was actually a case of RDPing to a dev environment) and some friends at certain projects at big tech were telling me about their setups and how they had to learn Emacs again because all the code and their dev workstations were in a protected remote environment and no source code was allowed on their local machines.
Re:A Quick and Easy Guide to Tmux (2015)
by scruple on Tuesday October 29, 2019 @11:51PM
(#21394540)
In embedded, I did a _lot_ of development work _on_ the physical target hardware via SSH. It wasn't every product, but it was most. It wasn't from the beginning, but rather there was always some point in development time where the feedback loop would tighten up dramatically if the work was being done on a device on the bench.
But you're super right, I have so many little "quirky" things that just don't work right, like I used to be able to easily double click a line and it would just copy it to a buffer; pasting from my host OS requires different key bindings, and my TMUX config file has slowly grown as I tried to get it working just right... Might be time for me to learn iTerm2 properly....(maybe I can modify keyboard shortcuts to be like Tmux for moving around to different panes....) But part of me worries about the time when I have to go back to a remote dev env where I'm expected to SSH to a protected source code machine.