This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author dottedmag
Recipients dottedmag
Date 2008-10-10.21:20:59
SpamBayes Score 2.7268188e-12
Marked as misclassified No
Message-id <1223673661.93.0.815684986423.issue4102@psf.upfronthosting.co.za>
In-reply-to
Content
Debian bug #501629 (http://bugs.debian.org/cgi-bin/bugreport.cgi?
bug=501629).

Both sphinx-build and sphinx-quicksetup attempt (and fail) to use ansi
color sequences, even when TERM=dumb (for example, when run from an
emacs shell buffer, or m-x compile.  This produces garbage, like this:

^[[01mSphinx v0.4.2, building linkcheck^[[39;49;00m

While it does look like I can add -N in the generated Makefile, and
thus this is only a wishlist item since I have a workaround - it
really shouldn't generate color unless it has *some* indication that
it might work - even mooching off of $LSCOLORS would be better than
doing it blindly, though it should be enough to look at a TERM or
TERMCAP property - or perhaps indirectly via curses.has_colors() which
does appear to be able to tell "xterm" from "dumb" successfully.
History
Date User Action Args
2008-10-10 21:21:02dottedmagsetrecipients: + dottedmag
2008-10-10 21:21:01dottedmagsetmessageid: <1223673661.93.0.815684986423.issue4102@psf.upfronthosting.co.za>
2008-10-10 21:21:01dottedmaglinkissue4102 messages
2008-10-10 21:21:00dottedmagcreate