On 2017-02-14 21:44, Claude Marinier wrote: > I am trying to reproduce the error with the intent of poking around. > How can I tell 'csc' to keep the generated C?
Use `csc -k` (for "keep"). > By the way, right after building, I notice 'csi' behaves oddly. > > claude@HP MINGW64 ~/chicken-4.11.1/tests > $ csi > (* 1 2 3 4 5) > (exit) > > CHICKEN > (c) 2008-2016, The CHICKEN Team > (c) 2000-2007, Felix L. Winkelmann > Version 4.11.1 ((detached from 4.11.1)) (rev 116f42e) > windows-mingw32-x86-64 [ 64bit manyargs dload ptables ] > compiled 2016-09-12 on waldrop (Linux) > > 120 > > claude@HP MINGW64 ~/chicken-4.11.1/tests > $ > > This is unexpected. It looks like a terminal I/O problem. Is this known? Yeah, and I have a hunch it might be caused by the same underlying issue, but I'm not really sure. In short, `##sys#tty-port?`, which is used by by csi(1) to detect whether it's running in a terminal or not, fails from within the MSYS shell: peeking the leading byte of the port gives a non-zero value, which is unexpected. Cheers, Evan _______________________________________________ Chicken-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-users
