This is the mail archive of the
kawa@sources.redhat.com
mailing list for the Kawa project.
Re: 'read' not echoing characters
Jim White wrote:
> That is something of a FAQ for Kawa.
>
> The problem is that SysInPort checks InputStream.available() before
> trying to read any characters. But the Windows console reader buffers
> lines (for the edit functions of course), and so doesn't update that
> on a per-character basis, and neither does it echo because it doesn't
> yet know what kind of read the application is going to do.
Ah. I haven't actually seen that explanation before (that I can recall).
Maybe it is time to get rid of the whole SysInPort hack. The code are
pretty old, and
seems to be work-arounds for problems that I hope Sun has fixed by now!
My requriement is to be able to start a scheme-window and/or a JEmacs
window while
still being able to use the console's read-eval-print-loop. I guess it
should not be too
dofficult to test that, though we might need some testing from people
stuck on
old JVMs before we make a decision.