tjfs@tadtec.tadpole (Tim Steele) (08/06/90)
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: 11 7C 00 13 00 62 11 7C 00 11 00 63 11 7C 00 03 00 64 These are move.b instructions to store ^Q ^S and ^C somewhere. Perfect! This is the only place where the three bytes appear in such sequence. Unfortunately... patching them to FF makes no difference!! Can anyone help? If you have source, you could point us to where to patch the binary! Thanks!! Tim -- tjfs@tadtec.uucp ...!uunet!mcvax!ukc!tadtec!tjfs Tadpole Technology plc, Science Park, Milton Road, CAMBRIDGE, CB4 4WQ Phone: +44-223-423030 Fax: +44-223-420772 Telex: 817316 TADTEC G
Sowa@cms1.llnl.gov (Erik Sowa) (08/07/90)
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.
billh@sentry.larc.nasa.gov (Bill Henderson) (08/07/90)
Why don't you try the Setup Keys... item on the Session menu? It's lots easier than hacking the code... Once you use Setup Keys on the Session Menu, select Save Set... on the File menu. This will prompt you for a file name and will save your session save set to disk. Now instead of double clicking on the NCSA Telnet Icon, double click the save set icon. The setup keys will now be whatever you set them to in the previous session. Bill Henderson -- ----------------------------------------------------------------------------- | Q: What's on television? | Bill Henderson | | A: Looks like a penguin!!! | Unisys-NASA Langley Research Center | | | billh@sentry.larc.nasa.gov | -----------------------------------------------------------------------------
derek@leah.Albany.Edu (Derek L. / MacLover) (08/07/90)
From tjfs@tadtec.tadpole (Tim Steele) come these immortal words: >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: [...] >Can anyone help? If you have source, you could point us to where to >patch the binary! Thanks!! Do it this way. Edit your config.tel file, and add a line (under your default session name, if you want it to apply to all of your sessions, which says: localkeys=off if you want it off completely, or change the values. I believe the default is: localkeys="3,19,17" though I'm sure someone will correct me if I'm wrong. If this has been said already, I apologize; our system went down and the last weeks' messages have been purged. >Tim Derek L. -- + + One Mac is worth exactly 2.317 PCs (based on current price indices) + + Disclaimer: I was asleep. ---}=-----F-e-n-c-e-r----------` ++ All the busy little creatures / Chasing out their destinies --Peart ++
aem@mthvax.cs.miami.edu (a.e.mossberg) (08/07/90)
In <65966@lll-winken.LLNL.GOV> Sowa@cms1.llnl.gov (Erik Sowa) writes: >Why don't you try the Setup Keys... item on the Session menu? >It's lots easier than hacking the code... Because it's annoying to have to do it every time and it doesn't save setup keys when you "Save Set...". Someone mentioned a parameter that could be added to the config.tel file, but I tried it (it was setupkeys = or somesuch) and NCSA barfed on it. aem -- a.e.mossberg / aem@mthvax.cs.miami.edu / aem@umiami.BITNET / Pahayokee Bioregion Walk! Not bloody likely. I am going in a taxi. - George Bernard Shaw
rek@sei.cmu.edu (Bob Kubiak) (08/07/90)
>> 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... You can also add the line "localkeys=off" to your config.tel file, which will disable these by default (instead of having to do this each time, or rely on having them saved as such in a set). This was apparently left out of the documentation. We asked, after getting annoyed ourselves. _Bob Kubiak Software Engineering Institute Carnegie Mellon University rek@sei.cmu.edu
dwal@ellis.uchicago.edu (David Walton) (08/07/90)
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 Put the following line in your config.tel file: localkeys = off # disable flow control so emacs doesn't get pissed >Tim -- David Walton Internet: dwal@midway.uchicago.edu University of Chicago { Any opinions found herein are mine, not } Computing Organizations { those of my employers (or anybody else). }
roy@phri.nyu.edu (Roy Smith) (08/07/90)
>> 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) It seems to me that what is needed is some way (possibly an extension to the Telnet protocol?) for the host end to let the terminal end know that the tty has been put into raw mode. I don't see any fundemental reason why this can't be done. Comments? -- Roy Smith, Public Health Research Institute 455 First Avenue, New York, NY 10016 roy@alanine.phri.nyu.edu -OR- {att,cmcl2,rutgers,hombre}!phri!roy "Arcane? Did you say arcane? It wouldn't be Unix if it wasn't arcane!"
brnstnd@kramden.acf.nyu.edu (Dan Bernstein) (08/21/90)
In article <1990Aug7.015958.19478@phri.nyu.edu> roy@phri.nyu.edu (Roy Smith) writes: > It seems to me that what is needed is some way (possibly an > extension to the Telnet protocol?) for the host end to let the terminal end > know that the tty has been put into raw mode. I don't see any fundemental > reason why this can't be done. Comments? Linemode basically achieves this. ---Dan