Siteshwar Vashisht

This issue has diverted from it's original topic. But since everyone is putting down their thoughts here, I will summarize my experience and view of this project. I will try...

> define "irrelevant". problem starts here... > > > Removing code that was related to supercomputers that became obsolete in the 90s. I can't find relevant commit on quick look....

@gordonwoodhull Thanks for chiming in. > I'm open to all suggestions. I will follow the discussion and see if there are other stakeholders and other opinions. There are few questions...

> Since there is no one inside the company to maintain the project, that will be the end of the original fork, and we can archive it. That would be...

> I disagree with @siteshwar that this would be the "death of ksh". rather to the contrary. going on without a clear cut would do decisive further (maybe mortal) harm...

@krader1961 Was this comment meant for #1338 ?

@krader1961 It was reported against `ksh-20100202` on RHEL 5 back in 2013.

@kernigh You are right. I misinterpreted the expected test output. Also, the behavior does not change with locales but with using `-N` option instead of `-n`.

As @DavidMorano mentioned, `ksh` peeks into file descriptors before reading data. It seems it is being used to determine slow devices. When `read -n` is used, ksh [tries to peek](https://github.com/att/ast/blob/71e6fdad1cb24c245954a887b85b0b5268ed3933/src/lib/libast/sfio/sfpkrd.c#L223)...

@zakukai This issue was reported earlier to kernel people, but they do not consider it a bug. You can read related message [here](https://marc.info/?l=ast-users&m=120978595414993&w=2).