Subject: Re: Pine and NCSA Telnet for Mac on BSD/386

From: Joe Brennan <[email-masked]>
Date: Sun, 10 Jul 94 0:17:43 EDT

> I have a problem that I hope someone knows the solution to.  We are
> running Pine on a PC running BSD/386.  Everything works great except
> when people connect to the machine using NCSA Telnet on the Mac.
> For these people, the return key ends up being treated like it
> is sending linefeeds during mail creation, such that hitting return
> either tries to attach files or in the body tries to reform the
> paragraph.
> 
> Any suggestions?

We had to rewrite the code to move functions away from control-J.
Some sites do not have this problem, including the home of pine in
Washington, but some do.  I would sincerely request a "no control j"
compile option in some forthcoming version.  I'll try to package the
changes as a patch for 3.90; right now the various changes we did are
intermingled, so I don't have this part readily available.

You may note that literally control key and J ends up as a control-M
character on the unix host.  This is the problem.  We could not find
what does it. The version of telnet is the same one they have at
Washington.  Probably it is somewhere in the network.

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

---

From: [email-masked] (Noel Hunter)
Date: 10 Jul 1994 07:47:23 GMT

You mat be able to termorarily work around the problem with an stty
command to change the way ctrl-j and ctrl-m work.  Here are some
possibilities to try (with explanations from the stty man page):

stty options

options that might affect it:

      igncr (-igncr)           Ignore (do not ignore) CR on input.
      icrnl (-icrnl)           Map (do not map) CR to a new-line character
                               on input.
      onlcr (-onlcr)           Map (do not map) new-line character to a
                               carriage-return/new-line character sequence
                               on output.
      ocrnl (-ocrnl)           Map (do not map) CR to new-line character on
                               output.
      onlret (-onlret)         On the terminal, a new-line character
                               performs (does not perform) the CR function.

typing stty -a should show the current setup.

Good luck!

--
* Noel Hunter,  Academic Systems Administrator,    Wake Forest University *
* email: [email-masked]                            http://www.wfu.edu/~noel *

---

From: Mark Crispin <[email-masked]>
Date: Sun, 10 Jul 1994 14:09:33 -0700

Joe -

     The problem is not in NCSA Telnet, but rather in the telnetd on the UNIX
host.  A version of BSD telnetd of several years ago did not handle Telnet
newlines correctly.  This was fixed back in 1991, but a lot of vendors still
are distributing the old broken version.

     A workaround for some systems (e.g. NeXT) is the command: stty -extproc