aboutsummaryrefslogtreecommitdiff
path: root/functions/colors.zsh
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'fix_colors' into prepare_066Dominik Ritter2018-08-081-322/+297
|\
| * Write comparison with double quotesDominik Ritter2018-08-081-1/+1
| |
| * Pad colors with zeroesDominik Ritter2018-08-081-1/+2
| |
| * Always use color codes instead of named colorsDominik Ritter2018-08-081-34/+25
| | | | | | | | | | | | This Code was to check if the color is supported by the Terminal Emulator. This is not necessary, if we always use the numerical code. This makes the code much clearer.
| * Fix bright colorsDominik Ritter2018-08-081-6/+0
| | | | | | | | | | | | Remove old code that set bright colors equal to normal colors. This code was ancient and led to bright colors being unusable. The code originates from 0e37d8ef865daddd6af02ba78b4a3bb86fd5917e.
| * Make colors a global arrayDominik Ritter2018-08-071-265/+267
| | | | | | | | That way it must not be defined in every function call.
| * Write comparisons with double equalsDominik Ritter2018-08-071-1/+1
| |
| * Fix bright colorsDominik Ritter2018-08-071-6/+2
| | | | | | | | | | | | Remove old code that set bright colors equal to normal colors. This code was ancient and led to bright colors being unusable. The code originates from 0e37d8ef865daddd6af02ba78b4a3bb86fd5917e.
| * Make purpose clear of backgroundColor and foregroundColor functionsDominik Ritter2018-08-071-12/+4
| | | | | | | | | | The functions just start the colors, they do not end them. It seems too much to have a function that terminates a color.
* | Merge branch 'fix_colors' into prepare_066Dominik Ritter2018-08-061-0/+2
|\|
| * Add missing colors to fix color comparisonDominik Ritter2018-07-241-0/+2
| | | | | | | | | | Added magenta and cyan that were only present with their alternative names (fuchsia and aqua). See https://en.wikipedia.org/wiki/X11_color_names#Clashes_between_web_and_X11_colors_in_the_CSS_color_scheme
* | Test more readableYthildir2018-07-221-1/+1
| |
* | Resolve #918 Transparent backgroundYthildir2018-07-211-0/+4
|/ | | | | Now function getColorCode consider value 'none' like a good value. When it's use to set background the segment become transparent
* Make variables localDominik Ritter2018-03-271-3/+3
|
* add check of /etc/os-release for linux distrosTim Otlik2018-02-161-0/+0
|
* Merge pull request #681 from Stazer/tcolor-warningBen Hilburn2018-01-311-0/+4
|\ | | | | Added flag to ignore checking the term colors & lang settings
| * renamed POWERLEVEL9K_CHECK_TERM_COLORS to POWERLEVEL9K_IGNORE_TERM_COLORSJustus Flerlage2018-01-071-1/+1
| |
| * Added flag for checking the term colorsJustus Flerlage2018-01-071-0/+4
| |
* | getColor() must always print resultChristian Höltje2018-01-201-1/+1
|/ | | | This was causing colors specified as numbers to not be shown.
* colors checking optimized and added tput for check the colorsCharles Peterson2017-12-311-0/+16
| | | | moved to colors functions, because it makes sense.
* fix for colors since the terminals so not always render named colors when ↵Charles Peterson2017-12-161-267/+319
| | | | using parameter expansion.
* color names and fixesCharles Peterson2017-11-251-9/+258
| | | | | | | - fix for packageName truncated by POWERLEVEL9K_DIR_OMIT_FIRST_CHARACTER - processing the pwd/HOME replacement ONCE. - fix tests for named colors - use color names by default to allow dark/light themes to adjust colors based on names
* Extracted color functions to a separate file.Dominik Ritter2015-10-241-0/+56