Q. Is there a way to configure a Helper App that launches telnet or ssh in iTerm rather than Terminal?
A. To do this:
1. Define the ${LAUNCHER} as this command exactly as it appears below:
osascript -e 'tell application "iTerm"' -e 'activate' -e 'tell the last terminal' -e 'tell the last session' -e 'write text "
Notice how the quotes don't actually close correctly here. That's because they will close in the application definition.
2. Add "SSH" to the application list and fill it out like so:
${TITLE}: SSH
Command Line: ${LAUNCHER} ${PATH} ${ARGS} ${ADDRESS}"' -e 'end tell' -e 'end tell' -e 'end tell'
${PATH}: /usr/bin/ssh
${ARGS}: -l admin
Notice how the Command Line is actually a continuation of the ${LAUNCHER} definition.
The -l argument will actually log you into your ssh host with the username specified (in this case it's "admin"). If you don't do this, it will log you in with your shell username, which almost never will match your host.
For telnet, modify the existing application entry to:
${TITLE}: Telnet
Command Line: ${LAUNCHER} ${PATH} ${ARGS} ${ADDRESS}"' -e 'end tell' -e 'end tell' -e 'end tell'
${PATH}: /usr/bin/telnet
${ARGS}:
Thus the point is that just by modifying the ${PATH} variable you can launch anything in iTerm:
${PATH}: /usr/sbin/traceroute
${PATH}: /sbin/ping
On Windows you can use puTTY. For example:
putty ${ARGS} ${ADDRESS}
${PATH}:
${ARGS}: -ssh
Input: ${ADDRESS}
For telnet just change ${ARGS} to be -telnet
This requires you to add the path to puTTY into the Windows $path variable, but instead you can use InterMapper's ${PATH}. The former method allows you to launch puTTY from the command line just by hitting Windows+R and typing in 'putty'.
