fix "--colors=" option in py-python-command-args. otherwise ipython is launched with "-i --colors LightBG" arguments.
How does this differ from existing PR #757?
PR #757 tells if user specifies his/her own color scheme by looking at the py-python-command-args as my patch does. That's correct. But if user follows the the new syntax, it won't work as expect. Because:
(member "--colors" py-python-command-args)
fails to match --colors=LightBG. while my patch matches the arguments with (string-match "^--colors=*" x) where string-match matches the elements in the argument list with a regular expression of ^--color=* . That's the right way to go, IMHO.
(string-match "^--colors=*" x)
Other than this, we are basically the same. And I am sending PR #765 in which I replace all tab with four spaces.
just re-submitted PR #766 which is better formatted and more concise.
You don't need to keep reissuing pull requests, they are not static. If you push again to the same branch, it will change the pull request. You can clobber existing changes with push -f.
thanks a lot. minrk. =)
I just pushed the latest commit.
While you are fixing args, you might fix '-pylab' to '--pylab'. '-pylab' is technically allowed, but throws a deprecation warning, because it doesn't match the existing pattern.
fix "--colors=<color>" option in py-python-command-args. otherwise ip…
…ython is launched with "-i --colors LightBG" arguments.
Okay, then I'll go ahead and merge, as this seems straightforward and useful.