On Mon, Dec 08, 2008 at 10:56:15AM -0500, Benji York wrote: > On Mon, Dec 8, 2008 at 2:22 AM, Michael Howitz <[EMAIL PROTECTED]> wrote: > > Log message for revision 93766: > > color by default > > This setting apparently causes problems for people who use Emacs, so > for zope. and zc. packages at least, we don't use --auto-color.
Two comments:
* on Unix it is possible to detect whether your terminal supports
color: curses.tigetnum('colors') returns 8 in gnome-terminal and -1
in emacs's dumb terminal). zope.testing.testrunner already uses
curses.tigetnum() to detect the terminal width with graceful
fallbacks on Win32 and other crippled platforms that don't have
'curses'. Making --auto-color do the Right Thing should be easy.
https://bugs.launchpad.net/zope.testing/+bug/306476
* it's a rather strong personal preference whether people want
colors or not; enabling them by default is not a good decision,
having a global config file in $HOME for that setting would be a
good choice.
https://bugs.launchpad.net/zope.testing/+bug/306478
Marius Gedminas
--
Attempts to stick to simple on-or-off options lead to monsters like gcc, which
now has so many flags that programmers are using genetic algorithms to explore
them.
-- http://www.third-bit.com/~gvwilson/xmlprog.html
signature.asc
Description: Digital signature
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
