Xref: utzoo comp.sys.mac.apps:1045 comp.protocols.appletalk:4072
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!lll-winken!cms1.llnl.gov!Sowa
From: Sowa@cms1.llnl.gov (Erik Sowa)
Newsgroups: comp.sys.mac.apps,comp.protocols.appletalk
Subject: Re: NCSA Telnet Setup Keys
Message-ID: <65966@lll-winken.LLNL.GOV>
Date: 6 Aug 90 18:01:01 GMT
References: <TJFS.90Aug6125859@tadtec.tadpole>
Sender: usenet@lll-winken.LLNL.GOV
Followup-To: comp.sys.mac.apps
Organization: Lawrence Livermore National Laboratory
Lines: 15

In article <TJFS.90Aug6125859@tadtec.tadpole> tjfs@tadtec.tadpole (Tim 
Steele) writes:
> Aagh!  It's so annoying!  Following on from my posting last week
> asking if anyone knew how to stop NCSA Telnet 2.3.2 defaulting to ^C
> ^S ^Q for interrupt/flow control (which conflicts with Emacs), I have
> been looking through the code for the relevant bytes.  At offset $3c1a
> in CODE resource Main I found:

Why don't you try the Setup Keys... item on the Session menu?
It's lots easier than hacking the code...

Erik Sowa (sowa@cms1.llnl.gov)
*****
That is my opinion, it is mine, and belongs to me and I own it, and what 
it is too.