Why would I want to touch the mouse?
Why would I want to touch the mouse?
Or, put another way: think beyond your own use case before posting, yeah?
No installation required.
Your hands are going to the keyboard.
We're discussing whether or not it's worth screwing around with the mouse beforehand.
Is it for me? I'll try it, but I don't think so. But I think it serves a need for some people, and I can always get behind ideas that serve or improve--successful or not--workflow/dev needs.
Great work Trevor!
Command-n
zz enter
The times per day I open a new SSH session (and I'm a heavy SSH user) are so miniscule that keyboard vs mouse wouldn't do anything than give me a false sense of superiority.
That said, I already know this Spotlight shortcut, and yet I fail to see how eleven (ELEVEN) keypresses as described above are any better than lazily moving my mouse and clicking on a dropdown menu.
No, I don't want to "have my hands down on the keyboard all the time", like they are glued there. Not even when I'm programming. I'm drinking my coffee at the same time, for one.
And my commits (including typed and discarded code) are no more than 1000 lines per day. I could write those in 5 minutes, if keyboard dexterity was all it took to program.
So fuck yeah, I'll move my hands. I move them anyways, to interact with graphical elements that do need a mouse, to drink my coffee, to grab a pen and pencil and do some rough sketch, to scratch my neck, to answer the phone, to fix my glasses and tons of other things. And to not have them go numb.
Second, why would you open a new terminal window, then immediately open a new terminal window?
Third, I accounted for this in my post.
Finally, what kind of response is this? Are you posting a how-to? Are you making a counter point? Are you just being snarky?
Long ago I wrote a similar ssh target browser, in just a few lines of Perl/Tk, that pulled all the hosts from my then-employer's server database (several hundred of them, thousands if you included our dev/test VMs, and constantly changing) and created a simple tree view for reviewing and navigating the set, based on location, functional role, sequence number, customer, software level etc.
Also handy/dangerous was having it launch mirrored gterms for a given set.
Half the staff used this tool. I'd be surprised if most admins of moderate-to-large installations didn't have something similar.