Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding Solarized light theme #143

Closed
wants to merge 104 commits into from
Closed

Adding Solarized light theme #143

wants to merge 104 commits into from

Conversation

ruturajv
Copy link

@ruturajv ruturajv commented May 9, 2014

Adding solarized light theme and tweaking the dark one.

solarized-dark
solarized-light

@ruturajv ruturajv changed the title Adding Solarized theme Adding Solarized light theme May 9, 2014
Ruturaj K. Vartak and others added 7 commits May 14, 2014 11:35
OSError: if git is installed in non standard path
Rationale:
A plain path like "~/projects/powerline-shell" can be easily copied&pasted, and also takes up less space in the prompt.

The new command line parameter --cwd-mode controls the display of the cwd segment:
--cwd-mode=fancy is the same as the current default
--cwd-mode=plain is the new mode to display a plain path
--cwd-mode=dironly is the same as the old parameter --cwd-only (which is still supported to keep backward compat)
vivekkrish added a commit to vivekkrish/powerline-shell that referenced this pull request Nov 16, 2014
ruturajv and others added 8 commits February 8, 2015 16:54
b-ryan and others added 29 commits November 21, 2015 18:55
Allow virtualenv segment to be from Anaconda
The indent level didn't allow for copy and paste in my ~/.vimrc, as there were prefixed by 8 spaces.
Docs: rm indent level in codeblock
Encoding works on Py2.7, but will only encode if Py3 in case
it breaks earlier Py2.x
sys.version_info doesn't have named tuple components prior
to Python 2.7
https://docs.python.org/2/library/sys.html#sys.version_info
Py3 fixes to lib/color_compliment.py
When all of the new code to provide more interesting stats was added to
git.py, it was not very re-usable. A few pull requests could use it
though. In particular, b-ryan#105 adds more info to the svn segment and b-ryan#210
does the same for mercurial. I would rather not create inconsistencies
among these segments or have them duplicate code. Moving it into the
base file creates a place where each segment can access it and have a
consistent behavior.
Moved all repo stats code from git.py to the base
@b-ryan b-ryan closed this in 9e49b7d Sep 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.