On Thu, Apr 8, 2010 at 10:05 AM, Stanimir Stamenkov <[email protected]> wrote: > Wed, 07 Apr 2010 23:31:54 +0300, /Stanimir Stamenkov/: >> Tue, 6 Apr 2010 16:48:09 -0500, /Steve Borho/: >> >>> The color.py logic in hg-1.5.1 looks like this: >>> >>> if (opts['no_color'] or opts['color'] == 'never' or >>> (opts['color'] == 'auto' and (os.environ.get('TERM') == 'dumb' >>> or not >>> sys.__stdout__.isatty()))): >>> "apply color" >> >> I guess I have to >> trace somehow at least the results of (os.environ.get('TERM') == >> 'dumb') and (sys.__stdout__.isatty()) to see if they differ as both >> systems I'm trying on are pretty much the same. > > Thanks for pointing out the exact program logic, Steve. It appeared > I have TERM=dumb set in the environment on the machine not showing > the colors automatically. I don't know where I've got it from though.
For what it's worth, today's tortoisehg-unstable MSIs have the new cmd.exe console aware color.py extension. When hg-1.6/thg-1.1 is released, wincolor.py will be turned into an empty shim, and removed outright in a later version. -- Steve Borho ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
