Subject: Re: Ctrl C won't work on our MACs

From: Joe Brennan <[email-masked]>
Date: Thu, 6 Apr 95 17:34:12 EDT

In Mac NCSA telnet, pull down Session, Setup Keys, and blank out the
three boxes, especially the one that makes ^C be Interrupt Process
(referring to the Mac!).  Save the settings.  I can't figure out why
anyone would want the defaults; ^C is essential to unix systems.

The ^J problem is tough.  The return key and even literally control-M
end up sending a ^J to the unix host.  I've been told in some cases
it's an old version of telnetd on the host.  We gave up here and
hacked pine so ^J is treated like RETURN (^M), and reassigned the
functions of ^J to other control keys.  Not too awful, although
it's little changes all over the place.  3.91 was easier than 3.05.

It would be a nice compile option to get the "No-control-j" version.
Actually, I can only blame myself for not packaging the changes as
patches yet.

Joseph Brennan     Academic Information Systems
                   Columbia University in the City of New York
                   [email-masked]

---

From: [email-masked] (Barry Bouwsma)
Date: 7 Apr 1995 03:09:43 GMT

Having made a post after 30+ hours of wakefulness about this thread, I
feel obligated to chip in another 2c...

>anyone would want the defaults; ^C is essential to unix systems.

    In the setup I was using, these keys were blank.  That's what disturbed
me, along with the fact that of the two sessions I had with identical
settings, one worked well (the SunOS), while the other, um, did not.

    On a different Mac, running the same NCSA telnet, the host which did
not work well before, seemed to be working, until I remembered I had opened
an rlogin to the troublesome host.  My actual telnet session was to a Dec
Ultrix machine, which seemed to cooperate reasonably well with the Mac.

    However, a direct telnet to the BSD/386 machine is a disaster.  I cannot
use many of the control keys.  I can't suspend and continue.  I have to use
ESC ESC ^ to mark text.  (And I thought the Dec with no ESC key was a bit
inconvenient for an Emacs junkie.)  And I think that the ^O was lost -- I use
Emacs too, and I was unable to open a new line.  Right now I can't open a new
line in Emacs, although I think I was able to do so with a direct telnet to
this host (SunOS), which I am now reaching via telnet from the BSD/386 machine
accessed via rlogin from Ultrix to which I have Mac NCSA telnetted.
    I need more OSes I can loop through to reach my destination...

    Obviously, Mac NCSA telnet works with some telnetd programs, and not well
at all with others, and BSD/386 offered by my ISP is not one of them.  (Maybe
there's a replacement for that telnetd...)

-- 
 Barry Bouwsma, will crash computers for chocolate and dental care
    Please direct mail to  <[email-masked]> (MIME-aware)
LOAD "SENDMAIL",8,1
                            driving a 300 baud Trabant on the Datenautobahn