Xref: utzoo news.software.b:7699 news.newusers.questions:5019
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!otsc!snyde_sl
From: snyde_sl@tsca02.uucp (Steve Snyder)
Newsgroups: news.software.b,news.newusers.questions
Subject: Problem with rn - long commands must end with ^J
Summary: Cannot use <RETURN> key after long rn command
Keywords: rn, C news, control-J (linefeed), <RETURN>, stty
Message-ID: <1991May8.211839.11974@otsc.eds.com>
Date: 8 May 91 21:18:39 GMT
Sender: snyde_sl@otsc.eds.com (Steve Snyder)
Distribution: na
Organization: none
Lines: 45

Our site recently established a newsfeed.  We are running C news (last
patch date is 24-Mar-91) and rn (last patch date is 01-Jan-91, # 54)
on an Apollo DN3000 under Domain/OS SR10.2 (sys 5.3 environment).

The problem is not real serious but is a minor irritation.  In order to
execute any of rn's commands which are more than 1 character long, I
have to type control-J (linefeed) to terminate the command.  This 
appears to be the case at all 3 command levels (newsgroup selection,
article selection, pager).  If I press the <RETURN> key, ^M is echoed,
but the command is not executed.  I'd like our users to be able to 
execute these commands by pressing the <RETURN> key instead of having
to enter ^J.  Commands which give me this problem include the 
following:
	s <destination>
	& 
	g <newsgroup>
	<number>

The readnews reader (distributed with C news) does not have this 
problem.  I believe that rn is running in curses cbreak mode at the 
above prompt, whereas readnews is probably not.

I've tried changing some of the stty settings, but that didn't seem
to help.  Here's the output from 'stty -a' (default settings) if 
that's of any use:

	speed 38400 baud; line = 0; intr = ^c; quit = ^|; erase = ^h; 
	kill = ^u; eof = ^d; eol <undef>; 
	-parenb -parodd cs8 -cstopb -hupcl cread clocal 
	-ignbrk -brkint -ignpar -parmrk -inpck istrip -inlcr 
	-igncr icrnl -iuclc ixon -ixany -ixoff 
	isig icanon -xcase echo echoe echok -echonl -noflsh 
	opost -olcuc onlcr -ocrnl -onocr -onlret -ofill -ofdel 


Any ideas why rn responds this way, or possible solutions to this 
problem?  Does this happen to anyone else?  I'd prefer responses by
email, but I'll continue to watch the newsgroups where I posted this
if you'd rather post a reponse for the benefit of others who might
have a similar problem and questions.  Thanks.
-- 
Steve Snyder             | You've got to know when to code 'em,
Electronic Data Systems  | know when to modem, know when to load 'em,
snyde_sl@otsc.eds.com    | and know when to run.
uunet!tsca02!snyde_sl    |                        --Anonymous