X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andy Moreton Subject: Re: Problems with cygwin bash shell under NT Emacs Date: Tue, 15 Jul 2008 09:31:04 +0000 (UTC) Lines: 34 Message-ID: References: User-Agent: Xnews/2005.10.18 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mon, 14 Jul 2008 20:18:12 GMT, rolf wrote: > René Berber writes: > > > [snip] >> Just for reference, with XEmacs opening a shell: >> >> sh-3.2$ echo $TERM >> dumb >> sh-3.2$ echo $TERMCAP >> emacs:co#79:tc=unknown: >> sh-3.2$ python >> Python 2.5.1 (r251:54863, May 18 2007, 16:56:43) >> [GCC 3.4.4 (cygming special, gdc 0.12, using dmd 0.125)] on cygwin >> Type "help", "copyright", "credits" or "license" for more information. >>>>> 2+2 >> 4 >>>>> >> sh-3.2$ echo $SHELL >> /bin/bash > > Changing the TERM/TERMCAP settings didn't help. Thanks for your reference. > > Python just seems to be the only cygwin binary my bash can't handle. > Thats driving me nuts.... I do run NTemacs with cygwin. I do so becuase for a long time the cyugwin emaxs was broken and/or horribly slow compared to the NTemacs port, and requires an X11 server to have a GUI. Try running "python -i" to force interactive behaviour - this works for me. AndyM -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/