X-Authentication-Warning: new-smtp2.ihug.com.au: Host p103-tnt3.syd.ihug.com.au [203.173.132.103] claimed to be acceleron Message-ID: <001301c16f44$db69d550$0a02a8c0@acceleron> From: "Andrew Cottrell" To: References: <004601c153cd$c03c8f80$0a02a8c0 AT acceleron> Subject: Re: Info Issue with CVS LIBC Date: Sat, 17 Nov 2001 19:49:35 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Reply-To: djgpp-workers AT delorie DOT com I have had some time to look at this today and I found that the info from the build I did earlier this week does not exhibit this peroblem. It looks like one of the changes committed to CVS since early October has fixed it. Andrew ----- Original Message ----- From: "Andrew Cottrell" To: Cc: Sent: Saturday, October 13, 2001 8:59 PM Subject: Info Issue with CVS LIBC > Recevied this report from an end user who downloaded the files from clio: > > > I am trying to use DJGPP C++ compiler under winXP. Everything > > seems to be fine with October 07 build, except two things I found > > so far: 1. info.exe does not work actually (not a big problem) - it > > prints something to the screen after each keypress. > > I tried the info.exe on Win2K and a small amount of testing showed that when > pressing the cursor keys it looks like the ansi info is printed to the > display. The cursor appears to almost move correctly, but printing the > "^[[?" interferes with the movement. > > Print Keystroke > ^[[B Cursor Down > ^[[C Cursor Right > ^[[D Cursor Left > ^[[A Cursor Up > > On Win 98 the same problem occurs. > > The following shows the corrupted top left corner of the display after > moveing the cursor arround. > > ^[le: dir, No > ^[[B > ^[[Belcome to > ^[[Bented here > ^[[B > ^^^^^^[[Bw a t > the l^^^[[Begi > ^[[D > Th^^[[Ahe D > retur^^[[ADD, > for first-time > > I suspect that this is a 2.04 LIBC issue caused by one of the changes to do > with the terminal io. Anyone got any ideas where to start looking? If I > start looking at it now it will take me a number of hours before I narrow > the issue does enough to asertain where the problem may be. > > Thanks, > Andrew > >