Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Injected-Via-Gmane: http://gmane.org/ To: cygwin@cygwin.com From: Joe Buehler Subject: Re: stdio on bash shell/emacs Date: Thu, 30 Jan 2003 17:31:58 -0500 Organization: Spirent Communications, Inc. Lines: 19 Message-ID: References: Reply-To: jbuehler@hekimian.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@main.gmane.org User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3a) Gecko/20021212 X-Accept-Language: en-us, en In-Reply-To: Aaron Edsinger wrote: > hi. i've got a c program that works fine through cygwin bash. when i run it > from emacs bash on windows, the stdio no longer works. after trolling around > on the user groups, i found that using fflush(stdout) will allow a printf to > work. however, a call to kbhit() only returns true on Ctrl-C. does anyone > have any ideas about this. (here's the code:) As another poster said, investigate the "tty" setting in the CYGWIN variable. The fact that you see special behavior for ^C means that you probably don't have it set. It is also not clear exactly what you are doing. If you are just running "shell" then you are not talking directly to the subshell -- keystrokes are going to emacs, which is buffering them up then sending them when you hit return. -- Joe Buehler -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/