You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee='https://github.com/birkenfeld'closed_at=<Date2008-10-16.21:16:37.859>created_at=<Date2008-10-10.21:21:01.158>labels= []
title='sphinx: ansi color even on dumb terminal'updated_at=<Date2008-10-16.21:16:37.858>user='https://bugs.python.org/dottedmag'
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.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: