I have an italics font now that I can't shake either. Dos command window is fine, uwin is italics and it bugs me - any ideas where that attribute persists? Setting it to plain works for the current window but doesn't persist when I save it for all. Xterm is my answer the last couple of weeks. Italics is nearly unuseable though I'm guessing it my box and not uwin.
- jl - ----- Original Message ----- From: [email protected] <[email protected]> To: tom honermann <[email protected]> Cc: [email protected] <[email protected]> Sent: Wed Dec 09 08:39:31 2009 Subject: Re: [uwin-users] 2009-12-04 beta update This has been a small irritant since I first started using uwin a decade ago. Instead of resetting with the console properties, I simply exit and start another instance, which is nearly always OK. But I fail to see why this would render uwin "essentially unusable for running an interactive 'ksh' shell." Metta, Ivan On Wed, Dec 9, 2009 at 1:19 AM, tom honermann <[email protected]> wrote: > I recently (11-Nov-2009) posted to the uwin-developers email list the > following: > > I've been playing with the last few UWIN betas (including the version > recently released 11/2/2009) and have found that 'ksh' is sometimes, > unexpectedly changing the foreground font color to black. Since the > background color is also black, this makes it impossible to see text in the > 'ksh' console window. Has anyone else experienced this? I haven't yet > isolated a reproducible test case. I've seen this on Windows 2003 64-bit > and, I think, Windows 2003 32-bit. When this happens, the foreground text > color can be manually reset via the console properties. > > Several others replied that they have experienced this problem, but there > was no response from current UWIN developers. Has this issue been addressed > in the 04-Dec-2009 beta? If not, I would humbly advise holding off on the > release until this issue is isolated and corrected. For me, this issue > makes UWIN essentially unusable for running an interactive 'ksh' shell > (which is one of my primary requirements for a product such as UWIN). Is > this issue not experienced by (most) UWIN developers? > > Tom. > > On 12/4/2009 11:44 PM, Glenn Fowler wrote: > > { uwin-base uwin-dev } 2009-12-04 beta binary self-extracting archives > have been posted to > > http://www.research.att.com/sw/download/beta > > after about a week of feedback we plan to make an official release > > _______________________________________________ > uwin-users mailing list > [email protected] > https://mailman.research.att.com/mailman/listinfo/uwin-users > > > -- > > > _______________________________________________ > uwin-users mailing list > [email protected] > https://mailman.research.att.com/mailman/listinfo/uwin-users > > -- Ivan Van Laningham God N Locomotive Works http://www.pauahtun.org/ http://www.python.org/workshops/1998-11/proceedings/papers/laningham/laningham.html Army Signal Corps: Cu Chi, Class of '70 Author: Teach Yourself Python in 24 Hours _______________________________________________ uwin-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/uwin-users _______________________________________________ uwin-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/uwin-users
