Re: lib/57867: Why does cbreak or raw affect terminal output differently?

[Brett Lymn <blymn%internode.on.net@localhost>]

On Mon, Jan 22, 2024 at 07:50:02AM +0000, RVP wrote:
>  
>  It shouldn't. I think this is a bug which has also been fixed in 10.x:
>  

It should, see:

https://pubs.opengroup.org/onlinepubs/7908799/xcurses/intov.html#tag_001_005_002

the termios settings are different between raw and cbreak, see the function 
_cursesi_gettmode in tty.c which defines the mode.


>  http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=55931

No, that was an implicit assumption that CUD1 was set to a newline character which would
result in an implicit carriage return being sent and result in the cursor moving to the
beginning of the next line.  Some terminals did not do this which broke the display.

Also, a couple of things:

1) This isn't really a bug per se, it probably would have been better to ask on one of the
mailing lists.

2) If you are trying to create some sort of capture for curses output the have a look in the
automated test framework for the libcurses test which do exactly this already.

-- 
Brett Lymn
--
Sent from my NetBSD device.

"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"