This repository has been archived by the owner on Apr 30, 2020. It is now read-only.
Fix POWERLINE_CUSTOM_CURRENT_PATH #59
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
POWERLINE_CUSTOM_CURRENT_PATH does nothing, because it then sets POWERLINE_CURRENT_PATH instead of POWERLINE_PATH
sp-roger-clotet
approved these changes
Apr 11, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
POWERLINE_CUSTOM_CURRENT_PATH does nothing, because it then sets POWERLINE_CURRENT_PATH instead of POWERLINE_PATH
Feasibly, POWERLINE_CUSTOM_CURRENT_PATH could be renamed to POWERLINE_CUSTOM_PATH, or its behaviour could be directly rolled into the POWERLINE_PATH variable (by checking if it is unset before setting the default).