Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3C04A742.50700@yumpee.org> Date: Wed, 28 Nov 2001 02:58:42 -0600 From: Manoj Plakal User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.5) Gecko/20011011 X-Accept-Language: en-us MIME-Version: 1.0 Newsgroups: comp.lang.python To: cygwin AT cygwin DOT com Subject: rxvt + python problem: script output buffered and interactive output missing Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi, I'm encountering a strange problem when I run Python scripts and the Python interpreter in an rxvt window (with tcsh) on the latest Cygwin. This is with Win98/BeOpen Python 2.0/Cygwin 1.3.5/rxvt-2.7.2. The scripts print some messages to stdout but these gets buffered and appear only when the app exits (it runs for a while). If I add calls to flush stdout, then the messages appear as they are printed. If I run the Python interpreter itself, I get no output at all, the shell just hangs, I get the hourglass icon and I can eventually break out with Ctrl-C's. Things work fine with bash in a DOS box. Makes me think that something is wrong with rxvt's handling of stdout/stderr. But it seems to work with some other console apps (like sftp). Manoj -- 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/