Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Color Terminal screens and ssh revisited yet again' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Color Terminal screens and ssh revisited yet again
Authored by: pauljlucas on Sep 23, '05 12:21:08PM

I still don't get why people like to make simple things complicated. Just create a Terminal window as you want it, color and all, and save its .term file. You change the Shell plist item to be "ssh whatever" and it works.

Unless you're ssh'ing to lots of different hosts all the time, the above is good enough.

---

- Paul



[ Reply to This | # ]
Color Terminal screens and ssh revisited yet again
Authored by: tomholio on Sep 23, '05 03:27:29PM
Unless you're ssh'ing to lots of different hosts all the time, the above is good enough.
uhm, that's pretty much the whole point! thanks to the two authors for collaborating and wrapping everything up!

[ Reply to This | # ]
Color Terminal screens and ssh revisited yet again
Authored by: the_shrubber on Sep 23, '05 07:27:11PM

That's one good way to do things (especially since it lets you set all the colours, unlike our script). But for me, invoking a special purpose Terminal for a specific subtask doesn't come very naturally. My perhaps suboptimal tendency whenever I want to ssh somewhere is to pick up whatever terminal I have nearby and just use that. This script is useful for dealing with this sloppy behaviour.

Also, one thing which seems harder with the save-a-Terminal method is using ssh-agent. I tend to set up an ssh-agent, paste the details into a Sticky, and replicate it across several Terminals. I'd welcome any elegant suggestions you have for dealing with that :-)



[ Reply to This | # ]
ssh-agent
Authored by: sjk on Sep 23, '05 07:58:18PM
Not sure I completely understand your problem with ssh-agent but SSHKeychain might be a solution for it. Highly recommended, even with an intermittent memory leak on 10.3.x (haven't seen that on 10.4.x).

[ Reply to This | # ]