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 Message-Id: <200211131356.HAA08920@mail.mdanderson.org> Content-Type: text/plain; charset="utf-8" From: Jonathan Fosburgh To: cygwin@cygwin.com Subject: Re: Text problems with Cygwin >1.1.14 and TinyFugue Date: Wed, 13 Nov 2002 08:01:40 -0600 References: <5.1.1.5.2.20021112165500.00a9b6c8@mail.earthlink.net> <200211131327.HAA03290@mail.mdanderson.org> In-Reply-To: <200211131327.HAA03290@mail.mdanderson.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit On Wednesday 13 November 2002 07:32 am, Jonathan Fosburgh wrote: > On Tuesday 12 November 2002 09:10 pm, Jeremy Hetzler wrote: > > When I tested under bash that was using the Cygwin console, which is > cmd.exe. HOwever, when I get a chance, I will reinstall 1.1.15 and try from > a command prompt with no Cygwin shell, at least for comparison. Same problem from the DOS prompt. Also, I saw the same thing with the most recent snapshot of cygwin1.dll (11/6). While playing around, I did notice that the characters I typed wound up being passed to the shell after I killed tf. -- Jonathan Fosburgh AIX/SAN Administrator Communications and Computer Services UT MD Anderson Cancer Center Houston, TX IBM Certified Specialist - AIX v4.3 System Administration -- 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/