Fully featured telnet client for OSX?

[fishfry]

I sometimes have to telnet to two or more hosts at one time. What I can
do with BetterTelnet is associate colors with a particular terminal,
then associate that terminal to one or more of my telnet sessions. So
for example when I connect to host A, the telnet window comes up with
red lettering on a white background. When I telnet to host B, the
window uses blue lettering. I get an instant visual reminder of which
system I'm and I'm much less likely to type the wrong command into a
window.

I can't do this in Terminal.app. In Terminal I can set the text color
to blue or green or whatever but I have to do it by hand after I've
telnetted in. And I have to do it every single time.

At one point I think there was a project to port NCSA Telnet to OSX but
I don't think they got it working and I can now longer find it.

The problem with using BetterTelnet is that it's a Classic app, and my
10.2.6 system has a conflict between the energy saver and Classic that
causes Classic apps to not be able to display any text if the system has
ever been put to sleep. Apple has known about this bug for a long time
but apparently it's too low priority for them to fix.

Any suggestions for a replacement terminal client? Or are there clever
ways to get Terminal.app to do what I want?

[Jim Hill]

fishfry wrote:

>I sometimes have to telnet to two or more hosts at one time.

<shudder>

>The problem with using BetterTelnet is that it's

telnet.

<shudder>


Jim
--

Longhaired freaky people need not apply.

[David Eppstein]

In article <BLOCKSPAMfishfry-9A975E.22283030092003@netnews.attbi.com>,
fishfry <BLOCKSPAMfishfry@your-mailbox.com> wrote:

> I sometimes have to telnet to two or more hosts at one time. What I can
> do with BetterTelnet is associate colors with a particular terminal,
> then associate that terminal to one or more of my telnet sessions. So
> for example when I connect to host A, the telnet window comes up with
> red lettering on a white background. When I telnet to host B, the
> window uses blue lettering. I get an instant visual reminder of which
> system I'm and I'm much less likely to type the wrong command into a
> window.

Heh. I just include the line
set prompt='%m %~: '
in my .cshrc on all the hosts (as well as the OSX machine I connect
from). So I get immediate visual feedback in my prompts without
annoying color clutter.

--
David Eppstein [url]http://www.ics.uci.edu/~eppstein/[/url]
Univ. of California, Irvine, School of Information & Computer Science

[Tom Stiller]

In article <BLOCKSPAMfishfry-9A975E.22283030092003@netnews.attbi.com>,
fishfry <BLOCKSPAMfishfry@your-mailbox.com> wrote:

> I sometimes have to telnet to two or more hosts at one time. What I can
> do with BetterTelnet is associate colors with a particular terminal,
> then associate that terminal to one or more of my telnet sessions. So
> for example when I connect to host A, the telnet window comes up with
> red lettering on a white background. When I telnet to host B, the
> window uses blue lettering. I get an instant visual reminder of which
> system I'm and I'm much less likely to type the wrong command into a
> window.
>
> I can't do this in Terminal.app. In Terminal I can set the text color
> to blue or green or whatever but I have to do it by hand after I've
> telnetted in. And I have to do it every single time.
>
> At one point I think there was a project to port NCSA Telnet to OSX but
> I don't think they got it working and I can now longer find it.
>
> The problem with using BetterTelnet is that it's a Classic app, and my
> 10.2.6 system has a conflict between the energy saver and Classic that
> causes Classic apps to not be able to display any text if the system has
> ever been put to sleep. Apple has known about this bug for a long time
> but apparently it's too low priority for them to fix.
>
> Any suggestions for a replacement terminal client? Or are there clever
> ways to get Terminal.app to do what I want?

ITerm, available from sourceforge.net, has pretty good AppleScript
support. You can script it to change background and foreground colors
based on the connected host.

--
Tom Stiller

PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3
7BDA 71ED 6496 99C0 C7CF

[Hugh Wolf]

["Followup-To:" header set to comp.sys.mac.apps.]
On 2003-10-01, fishfry <BLOCKSPAMfishfry@your-mailbox.com> wrote:

> I sometimes have to telnet to two or more hosts at one time. What I can
> do with BetterTelnet is associate colors with a particular terminal,
> then associate that terminal to one or more of my telnet sessions. So
> for example when I connect to host A, the telnet window comes up with
> red lettering on a white background. When I telnet to host B, the
> window uses blue lettering. I get an instant visual reminder of which
> system I'm and I'm much less likely to type the wrong command into a
> window.
>
> I can't do this in Terminal.app.

Sure you can. Create a Terminal document with 'New Command' executing
the telnet to host X, set up the colors and everything else as you
want them, save the document. Launching the document will run a
telnet session to host X in a window with the given settings. If you
save the document in the default place it will show up in the
'Library' submenu of the 'File' menu.

I've been using color-coded windows in this way with Terminal.app
since the 10.0 beta, though with ssh rather than telnet.

[Doc O'Leary]

In article <BLOCKSPAMfishfry-9A975E.22283030092003@netnews.attbi.com>,
fishfry <BLOCKSPAMfishfry@your-mailbox.com> wrote:

> I can't do this in Terminal.app. In Terminal I can set the text color
> to blue or green or whatever but I have to do it by hand after I've
> telnetted in. And I have to do it every single time.

Only because you haven't bothered to save your session in Terminal.
Nothing "clever" about that.

[Phil Stripling]

fishfry <BLOCKSPAMfishfry@your-mailbox.com> writes:

> I sometimes have to telnet to two or more hosts at one time. What I can

I hope you mean you are using ssh?

>SNIP<
> I can't do this in Terminal.app. In Terminal I can set the text color
> to blue or green or whatever but I have to do it by hand after I've
> telnetted in. And I have to do it every single time.

Others have told you how to go about this. I love the menu selection for
help in Terminal: "Terminal Help." :-) OS X's help is not the easiest to
use (for me, anyway), but it is a heck of a lot better than the man pages.

If I may ask a favor, please use ssh instead of telnet. It is much more
nearly secure. My ISP will not even allow telnetting in.

>
> At one point I think there was a project to port NCSA Telnet to OSX but
> I don't think they got it working and I can now longer find it.
>
> The problem with using BetterTelnet is that it's a Classic app, and my
> 10.2.6 system has a conflict between the energy saver and Classic that
> causes Classic apps to not be able to display any text if the system has
> ever been put to sleep. Apple has known about this bug for a long time
> but apparently it's too low priority for them to fix.
>
> Any suggestions for a replacement terminal client? Or are there clever
> ways to get Terminal.app to do what I want?

--
Philip Stripling | email to the replyto address is presumed
Legal Assistance on the Web | spam and read later. email to philip@
[url]http://www.PhilipStripling.com/[/url] | my domain is read daily.

[Dave Hinz]

On Wed, 1 Oct 2003 05:58:46 +0000 (UTC), Jim Hill <jimhill@swcp.com> wrote:

> fishfry wrote:

>>I sometimes have to telnet to two or more hosts at one time.

><shudder>

>> telnet.

><shudder>

Hey, that's kind of a interesting effect. Everytime someone says
"telnet",
Jim seems to shudder.

Is the reason for the shudder, Jim, one of aversion to command line,
or to telnet as a connection protocol, or something else?

Dave "Telnet" Hinz

[spacemancw]

Jim Hill is as helpful as tits on a bull ... shut the eff up unless u
have some help to offer .... and I already know that ur predictable
response is on it's way

Anyway ... u can use Terminal

Open a new window in terminal
Go to File > Show Info
Set your colors, fonts, Window title, etc
Make sure the window now refelects these settings
The File > Save
and save as hostblah.term

to the extention is .term for any of these configs that u wanna save

Save the file in ~/Library/Application Support/Terminal/
You may have to create the directory 'Terminal' in the Application
Support directory.
Now under File > Libray you will see this new config as an option.

You can save the file anywhere u want. You can then open it by typing
at the command line

>open [PathToFile] filename.term

Hope this helps.




fishfry <BLOCKSPAMfishfry@your-mailbox.com> wrote in message news:<BLOCKSPAMfishfry-9A975E.22283030092003@netnews.attbi.com>...

> I sometimes have to telnet to two or more hosts at one time. What I can
> do with BetterTelnet is associate colors with a particular terminal,
> then associate that terminal to one or more of my telnet sessions. So
> for example when I connect to host A, the telnet window comes up with
> red lettering on a white background. When I telnet to host B, the
> window uses blue lettering. I get an instant visual reminder of which
> system I'm and I'm much less likely to type the wrong command into a
> window.
>
> I can't do this in Terminal.app. In Terminal I can set the text color
> to blue or green or whatever but I have to do it by hand after I've
> telnetted in. And I have to do it every single time.
>
> At one point I think there was a project to port NCSA Telnet to OSX but
> I don't think they got it working and I can now longer find it.
>
> The problem with using BetterTelnet is that it's a Classic app, and my
> 10.2.6 system has a conflict between the energy saver and Classic that
> causes Classic apps to not be able to display any text if the system has
> ever been put to sleep. Apple has known about this bug for a long time
> but apparently it's too low priority for them to fix.
>
> Any suggestions for a replacement terminal client? Or are there clever
> ways to get Terminal.app to do what I want?

[Susan Kayser]

Getting back to his Subject question, IS there a good telnet (or ssh)
client for OS X? One you can put on the Dock, instead of having to open
Terminal first? I'm trying MacTelnet occasionally, but the author is
still working on it.

Susan K

fishfry wrote:

> I sometimes have to telnet to two or more hosts at one time. What I can
> do with BetterTelnet is associate colors with a particular terminal,
> then associate that terminal to one or more of my telnet sessions. So
> for example when I connect to host A, the telnet window comes up with
> red lettering on a white background. When I telnet to host B, the
> window uses blue lettering. I get an instant visual reminder of which
> system I'm and I'm much less likely to type the wrong command into a
> window.
>
> I can't do this in Terminal.app. In Terminal I can set the text color
> to blue or green or whatever but I have to do it by hand after I've
> telnetted in. And I have to do it every single time.
>
> At one point I think there was a project to port NCSA Telnet to OSX but
> I don't think they got it working and I can now longer find it.
>
> The problem with using BetterTelnet is that it's a Classic app, and my
> 10.2.6 system has a conflict between the energy saver and Classic that
> causes Classic apps to not be able to display any text if the system has
> ever been put to sleep. Apple has known about this bug for a long time
> but apparently it's too low priority for them to fix.
>
> Any suggestions for a replacement terminal client? Or are there clever
> ways to get Terminal.app to do what I want?

--
Dr. Susan Kayser SDSS at FermiLab

[Thomas Russler]

In article <blke4m$37t$1@info4.fnal.gov>,
Susan Kayser <sukayser@fnal.gov> wrote:

> Getting back to his Subject question, IS there a good telnet (or ssh)
> client for OS X? One you can put on the Dock, instead of having to open
> Terminal first? I'm trying MacTelnet occasionally, but the author is
> still working on it.
>
> Susan K

Here's what I do to run an ssh session from the dock:

1. Open a new Terminal window and configure it the way you like it.

2. Save as "whatever.term" in /Users/yourself/Library/Application
Support/Terminal/. You may have to create the folder "Terminal" if it
isn't already there.

3. Quit Terminal.

4. Open somename.term with BBEdit or your favorite text editor. After
the line:

<key>ExecutionString</key>

make the next line read:

<string>ssh name.domain.com</string>

where "name.domain.com" is where you want to ssh to on a regular basis.

5. Save the file and drag it to the dock.

6. Now just one click in the dock and you are up and running.

7. Forget you ever heard of telnet!

--
Tom Russler
[email]trussler@panix.com[/email]

[Hugh Wolf]

["Followup-To:" header set to comp.sys.mac.apps.]
On 2003-10-03, Susan Kayser <sukayser@fnal.gov> wrote:

> Getting back to his Subject question, IS there a good telnet (or ssh)
> client for OS X? One you can put on the Dock, instead of having to open
> Terminal first?

Make a Terminal document running the command you want (ssh, telnet,
lynx, emacs, whatever), save it, drag it into the Dock like any other
document.

There's really no magic to any of this. Termimal is just like any
other osx app. The documents in this case run shell commands in a
vt100-like terminal window.

[Hugh Wolf]

["Followup-To:" header set to comp.sys.mac.system.]

> Here's what I do to run an ssh session from the dock:
>
> 1. Open a new Terminal window and configure it the way you like it.

If you use Run Command instead of New Shell you can skip all the
manual text editing.

[BreadWithSpam@fractious.net]

Susan Kayser <sukayser@fnal.gov> writes:

> Getting back to his Subject question, IS there a good telnet (or ssh)
> client for OS X? One you can put on the Dock, instead of having to
> open Terminal first? I'm trying MacTelnet occasionally, but the author
> is still working on it.

Terminal.app lets you save a "terminal file" - a document which
contains all the config info for an instance of a terminal window-
with custom fonts, colors, transparancy, size, etc. And it can
even have a default command embedded in it, too.

Save one of those files, stick it in the dock and you're good
to go.

I've got several machines to which I regularly ssh, and for which
I like different sized windows, etc. Each of them gets one of
those terminal documents in my dock. Actually, I've got a custom
icon on one of them, too.

The file it saves is a .term file. It's a simple xml doc and
you can open it up in a text editor if you like (ie. to add
that automated command - the property you edit is the "execution
string").

Start up a Terminal.app window, customize as you like, hit
Save As... from the file menu, and save that .term file.
Then take a look at it.

I, for one, very much prefer that my ssh program is separate
from my terminal emulation program. Which is the case here.

Terminal.app is really pretty good.

--
Plain Bread alone for e-mail, thanks. The rest gets trashed.
No HTML in E-Mail! -- [url]http://www.expita.com/nomime.html[/url]
Are you posting responses that are easy for others to follow?
[url]http://www.greenend.org.uk/rjk/2000/06/14/quoting[/url]

[Expletive Deleted]

On Fri, 3 Oct 2003, Susan Kayser wrote:

> Getting back to his Subject question, IS there a good telnet (or ssh)
> client for OS X? One you can put on the Dock, instead of having to open
> Terminal first? I'm trying MacTelnet occasionally, but the author is
> still working on it.
>

Well, you can put Terminal on the dock, which is what I do.
Then its an easy step to type ssh "server-name" at the command line
prompt.

[spacemancw]

Susan

you can put Terminal in the Dock and have all the different colored
configs as I described in my previous post. Terminal does it all. Some
apps allow you to save a config which already has the name of the host
and a username .. so all u need is to enter ur password .....
but with Terminal you can write a small script for each host u need to
connect to which does

ssh -l username hostname .... or whatever .... (btw .. ya .. avoid
telnet .. do ssh)

that's not too much effort ...... I don't see adding another emulator
when OS X already has what it takes.



Susan Kayser <sukayser@fnal.gov> wrote in message news:<blke4m$37t$1@info4.fnal.gov>...

> Getting back to his Subject question, IS there a good telnet (or ssh)
> client for OS X? One you can put on the Dock, instead of having to open
> Terminal first? I'm trying MacTelnet occasionally, but the author is
> still working on it.
>

[Susan Kayser]

Thanks, everyone. I'll give this a try.

Susan

Susan Kayser wrote:

> Getting back to his Subject question, IS there a good telnet (or ssh)
> client for OS X? One you can put on the Dock, instead of having to open
> Terminal first? I'm trying MacTelnet occasionally, but the author is
> still working on it.
>
> Susan K
>
> fishfry wrote:
>

>> I sometimes have to telnet to two or more hosts at one time. What I
>> can do with BetterTelnet is associate colors with a particular
>> terminal, then associate that terminal to one or more of my telnet
>> sessions. So for example when I connect to host A, the telnet window
>> comes up with red lettering on a white background. When I telnet to
>> host B, the window uses blue lettering. I get an instant visual
>> reminder of which system I'm and I'm much less likely to type the
>> wrong command into a window.
>>
>> I can't do this in Terminal.app. In Terminal I can set the text color
>> to blue or green or whatever but I have to do it by hand after I've
>> telnetted in. And I have to do it every single time.
>> At one point I think there was a project to port NCSA Telnet to OSX
>> but I don't think they got it working and I can now longer find it.
>>
>> The problem with using BetterTelnet is that it's a Classic app, and my
>> 10.2.6 system has a conflict between the energy saver and Classic that
>> causes Classic apps to not be able to display any text if the system
>> has ever been put to sleep. Apple has known about this bug for a long
>> time but apparently it's too low priority for them to fix.
>> Any suggestions for a replacement terminal client? Or are there
>> clever ways to get Terminal.app to do what I want?

>
>

--
Dr. Susan Kayser SDSS at FermiLab

[read-the-signature@send-spam-to-dev-null.com]

In comp.sys.mac.apps Susan Kayser <sukayser@fnal.gov> wrote:

> Getting back to his Subject question, IS there a good telnet (or ssh)
> client for OS X? One you can put on the Dock, instead of having to open
> Terminal first? I'm trying MacTelnet occasionally, but the author is
> still working on it.
>
> Susan K
>
>

X11 is an excellent solution to the original question (merits of telnet aside).
Its hard to replace xterm with something better IMHO.

You can put X11 in the dock and add menu items to the X11 Application
menu, through customize, to telnet or ssh to a remote host. The commands
below even color the screens differently and set the hostname on the xterm
title bar.

Example commands:

xterm -title hosta.foobar.com -sb -bg black -fg wheat -fn 10x20 -ls -e telnet hosta.foobar.com

xterm -title hostb.foobar.com -sb -bg green -fg yellow -fn 10x20 -ls -e telnet hostb.foobar.com

regards.
--
John J. Rushford
j j r { a t } a l i s a { d o t } o r g
[url]http://www.cs.du.edu/~jjr[/url]

[fishfry]

In article <VWpfb.670443$YN5.525916@sccrnsc01>,
[email]read-the-signature@send-spam-to-dev-null.com[/email] wrote:

> In comp.sys.mac.apps Susan Kayser <sukayser@fnal.gov> wrote:

> > Getting back to his Subject question, IS there a good telnet (or ssh)
> > client for OS X? One you can put on the Dock, instead of having to open
> > Terminal first? I'm trying MacTelnet occasionally, but the author is
> > still working on it.
> >
> > Susan K
> >
> >

>
> X11 is an excellent solution to the original question (merits of telnet
> aside).
> Its hard to replace xterm with something better IMHO.
>
> You can put X11 in the dock and add menu items to the X11 Application
> menu, through customize, to telnet or ssh to a remote host. The commands
> below even color the screens differently and set the hostname on the xterm
> title bar.
>
> Example commands:
>
> xterm -title hosta.foobar.com -sb -bg black -fg wheat -fn 10x20 -ls -e
> telnet hosta.foobar.com
>
> xterm -title hostb.foobar.com -sb -bg green -fg yellow -fn 10x20 -ls -e
> telnet hostb.foobar.com
>
> regards.

I've heard it's a lot of work getting X11 installed, is that true?

[read-the-signature@send-spam-to-dev-null.com]

In comp.sys.mac.apps fishfry <BLOCKSPAMfishfry@your-mailbox.com> wrote:

> In article <VWpfb.670443$YN5.525916@sccrnsc01>,
> [email]read-the-signature@send-spam-to-dev-null.com[/email] wrote:
>

>>
>> Example commands:
>>
>> xterm -title hosta.foobar.com -sb -bg black -fg wheat -fn 10x20 -ls -e
>> telnet hosta.foobar.com
>>
>> xterm -title hostb.foobar.com -sb -bg green -fg yellow -fn 10x20 -ls -e
>> telnet hostb.foobar.com
>>
>> regards.

>
>
> I've heard it's a lot of work getting X11 installed, is that true?

Not for OSX. If you do not have it installed already, download it from
here: [url]http://www.apple.com/macosx/x11[/url]. You install and use it like
any other OSX application. When you start it, see the X11 "Applications"
menu and go to "Customize". Use "Add Item" and give each command a name and
then put the xterm commands from above in the command column.

regards
--
John J. Rushford
j j r { a t } a l i s a { d o t } o r g
[url]http://www.cs.du.edu/~jjr[/url]