[Mono-bugs] [Bug 77518][Nor] Changed - Console 2.0 Problems Escape Codes and SetCursorPosition

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Feb 21 12:03:09 EST 2006

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by mike.hull at coversant.net.


--- shadow/77518	2006-02-21 10:46:29.000000000 -0500
+++ shadow/77518.tmp.11015	2006-02-21 12:03:09.000000000 -0500
@@ -1,12 +1,12 @@
 Bug#: 77518
 Product: Mono: Class Libraries
 Version: unspecified
 OS: GNU/Linux [Other]
 OS Details: Tried the latest mono on Gentoo and Suse 10.0
-Status: NEEDINFO   
+Status: REOPENED   
 Severity: Unknown
 Priority: Normal
 Component: CORLIB
 AssignedTo: gonzalo at ximian.com                            
 ReportedBy: mike.hull at coversant.net               
@@ -73,6 +73,35 @@
 Please provide further details: operating system, version, terminal,
 environment variables, and so on.
 Am setting this bug to NEEDINFO, please reopen this when you have the
+------- Additional Comments From mike.hull at coversant.net  2006-02-21 12:03 -------
+If you type very quickly in gnome-terminal or xterm it happens.  As 
+the speed of input increases the bug makes itself more apparent.  
+Try pasting something into the console if typing doesn't do it for 
+you.  That makes it happen every time for me.
+It happens in OpenSuse 10.0, with Mono very severely.  I'm 
+using Gentoo linux with and SVN for most of my testing.  
+With SVN from yesterday it happens quite a bit less, but it still 
+happens consistantly. 
+I have no environment variables of consequence.  The ROWS and LINES 
+are correct, and mono returns the correct values now.
+Its more apparent on my dual processor workstation in xterm, but it 
+also happens when I boot without the smp kernel in gnome-terminal.
+I'm going to attach a slightly modified version of the test case.  
+If an escape sequence is returned to ReadKey(true) it will write in 
+read letters "Escape Pressed".
+I'll have some time to dig into the Mono source today, hopefully I 
+can help find the cause.
+It also does not run correctly under win32 mono  It looks 
+like the Environment.NewLine is not being displayed correctly. And 
+each key that is being pressed is being returned twice.

More information about the mono-bugs mailing list