<br><br><div class="gmail_quote">On Sat, Oct 8, 2011 at 22:34, Aaron Meurer <span dir="ltr"><<a href="mailto:asmeurer@gmail.com">asmeurer@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
This is on Mac OS X.<br>
<br>
Here is my IPython profile, if that helps:<br>
<a href="https://github.com/asmeurer/dotfiles/blob/master/.ipython/profile_default/ipython_config.py" target="_blank">https://github.com/asmeurer/dotfiles/blob/master/.ipython/profile_default/ipython_config.py</a>.<br>
I'm guessing that having my colors set to 'linux' in my profile has<br>
something to do with it.<br></blockquote><div><br></div><div>Yes - this is a silly thing that we need to figure out. The 'colors' cl_arg sets InteractiveShell.colors. You have set TerminalInteractiveShell.colors, which is a subclass, and thus takes precedence. So when you have colors set in your config, and *also* at the command-line, you will be starting up IPython with config:</div>
<div><br></div><div>c.InteractiveShell.colors = 'NoColor'</div><div>c.TerminalInteractiveShell.colors = 'Linux'</div><div><br></div><div>Now, if you change your config file to specify InteractiveShell.colors instead of TerminalInteractiveShell.colors, the cl-arg will properly override.</div>
<div><br></div><div>What we should really do is adjust the cl-arg system, such that it maps somehow to all subclasses, or possibly just the lowest active subclass, so it always gets highest priority.</div><div><br></div>
<div>
-MinRK</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<font color="#888888"><br>
Aaron Meurer<br>
</font><div><div></div><div class="h5"><br>
On Sat, Oct 8, 2011 at 11:12 PM, Fernando Perez <<a href="mailto:fperez.net@gmail.com">fperez.net@gmail.com</a>> wrote:<br>
> Hi Aaron,<br>
><br>
> On Sat, Oct 8, 2011 at 9:48 PM, Aaron Meurer <<a href="mailto:asmeurer@gmail.com">asmeurer@gmail.com</a>> wrote:<br>
>><br>
>> I'm trying to figure out how to disable colors from the command line.<br>
>> The IPython help (ipython --help) says:<br>
>><br>
>> --colors=<CaselessStrEnum> (InteractiveShell.colors)<br>
>> Default: 'LightBG'<br>
>> Choices: ('NoColor', 'LightBG', 'Linux')<br>
>> Set the color scheme (NoColor, Linux, or LightBG).<br>
>><br>
>> I've tried ipython --colors=NoColor, ipython --colors="NoColor",<br>
>> ipython --colors='NoColors', ipython --colors NoColor, and none of<br>
>> them work (if I type just 1<Enter>, say, Out[1] is red). I do have<br>
>> the colors set in my config file (c.TerminalInteractiveShell.colors =<br>
>> 'Linux'). I tried in the 0.11 release and the git master.<br>
>><br>
>> Am I doing this wrong, or is this a bug?<br>
><br>
> That's very odd, it works perfectly fine for me here...<br>
> "--colors=NoColor" turns off all coloring for me for In, Out,<br>
> tracebacks, etc, as expected.<br>
><br>
> This is on a linux system, I assume?<br>
><br>
> Cheers,<br>
><br>
> f<br>
><br>
_______________________________________________<br>
IPython-User mailing list<br>
<a href="mailto:IPython-User@scipy.org">IPython-User@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/ipython-user" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-user</a><br>
</div></div></blockquote></div><br>