chicken-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-users] csi -:c MSYS problem


From: Kon Lovett
Subject: Re: [Chicken-users] csi -:c MSYS problem
Date: Thu, 6 Jul 2006 18:46:07 -0700

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Jul 6, 2006, at 12:29 PM, Graham Fawcett wrote:

On 7/5/06, Brandon J. Van Every <address@hidden> wrote:
Graham Fawcett wrote:
> Does it work if you run it with the -:c command line option, e.g. "csi
> -:c"? See the FAQ.

Huh, yes it does.  I wouldn't call this expected behavior though; the
FAQ entry is for emacs buffers. How difficult would it be to eliminate the need for -:c under MSYS? It strikes me as an impediment to usability.

Good question -- personally I don't know the answer. I encountered
this when trying to get CSI working in Emacs, and it struck me as odd
at the time; fortunately the FAQ refered to this -:c workaround. But
yes, it feels like a kluge.

Posix provides an isatty() function to let you know when a file
descriptor (like stdin/stdout) is connected to a terminal, rather than
a pipe; but there may be no (obvious) equivalent to this on Windows. I
imagine the root of the problem lies there. I don't know why the "-:c"
behaviour couldn't be the default on win32/msys, though... maybe
someone else can provide a good counter-case.

On a related note, it's really hard to see where the -:c behaviour is
defined in the Chicken source -- can someone give a pointer?

See runtime.c:CHICKEN_parse_command_line. The chk for tty-stdin is done by csi.scm.


Graham


_______________________________________________
Chicken-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/chicken-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)

iEYEARECAAYFAkStvN8ACgkQJJNoeGe+5O762wCeKVyc6/4bMYfadmgBkn+qmDUK
8rsAn0GwO4dn3pQl2BGuur7Xd+T4eAZq
=IOyu
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]