aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* pull upstream changes from gitstatusromkatv2019-10-192-0/+0
|
* work around a bug in zsh that percent-expands `%1F{2}` as if it was `%F{2}`; ↵romkatv2019-10-191-6/+5
| | | | fixes #270
* cleanupromkatv2019-10-161-1/+1
|
* Also show the default profile when setMelvyn de Kort2019-10-161-1/+1
|
* Add support for awsumeMelvyn de Kort2019-10-161-1/+1
|
* add ITERM_SHELL_INTEGRATION_INSTALLED to param sig; inline iterm2_prompt_markromkatv2019-10-161-2/+3
|
* bug fix: display the right OS icon on Androidromkatv2019-10-131-1/+1
|
* pull upstream changes from gitstatusromkatv2019-10-121-3/+6
|
* Fix EXC_BAD_ACCESS on MacOS CatalinaBenedikt Stemmildt2019-10-121-2/+2
| | | | Fix #259
* update screenshot, now with rainbow styleromkatv2019-10-121-0/+0
|
* change dir foreground from black to white in rainbow style; looks a bit less ↵romkatv2019-10-112-7/+7
| | | | ugly
* pull upstream changes from gitstatusromkatv2019-10-111-30/+36
|
* bug fix: set correct gitstatusd path on androidromkatv2019-10-111-2/+2
|
* bug fix: wrong tail color for rainbow in the wizardromkatv2019-10-111-1/+1
|
* add rainbow style; delete p9k styleromkatv2019-10-112-78/+947
|
* bug fix: normalize colorsromkatv2019-10-111-2/+2
|
* cleanupromkatv2019-10-113-86/+7
|
* restore "?" as VCS_UNTRACKED_ICON in lean and classic stylesromkatv2019-10-111-12/+14
|
* add POWERLEVEL9K_BATTERY_LEVEL_FOREGROUND; fixes #256romkatv2019-10-111-1/+9
|
* add the default powerlevel9k style to the wizardromkatv2019-10-102-12/+141
|
* add pure style to the configuration wizardromkatv2019-10-101-12/+40
|
* tone down the downsides of pureromkatv2019-10-101-13/+8
|
* docsromkatv2019-10-101-20/+26
|
* define POWERLEVEL9K_VCS_MAX_SYNC_LATENCY_SECONDS=0 in p10k-pureromkatv2019-10-101-2/+7
|
* make p10k-pure work without gitstatusromkatv2019-10-101-29/+49
|
* bug fix: wrap zle-line-finish even on hot startromkatv2019-10-101-6/+6
|
* remove spurious execute permissionsromkatv2019-10-103-0/+0
|
* use jq in azure if availableromkatv2019-10-101-3/+8
|
* md5 -q => md5romkatv2019-10-091-1/+1
|
* add two-level fs cache and use it everywhere instead of the one-level cacheromkatv2019-10-091-42/+80
|
* persist cache more aggressivelyromkatv2019-10-091-3/+15
|
* don't persist Git stateromkatv2019-10-091-6/+6
|
* cleanupromkatv2019-10-081-2/+1
|
* revamp aws_eb_env. it returns the starred entry from the output of "eb list"romkatv2019-10-083-4/+34
|
* typoromkatv2019-10-081-2/+2
|
* bump state versionromkatv2019-10-081-1/+1
|
* save and restore VCS_STATUS_NUM_UNSTAGED_DELETEDromkatv2019-10-081-1/+3
|
* pull upstream changes from gitstatusromkatv2019-10-081-0/+8
|
* avoid calling 'functions +M' as it sometimes crashes zshromkatv2019-10-082-2/+2
|
* add azure prompt segmentromkatv2019-10-084-0/+34
|
* bump state versionromkatv2019-10-081-1/+1
|
* check for gitstatus.plugin.zsh existence in preinitromkatv2019-10-081-10/+11
|
* avoid spurious console output where is more more than one dir segmentromkatv2019-10-081-1/+1
|
* clarify comments for POWERLEVEL9K_DIR_MAX_LENGTHromkatv2019-10-082-2/+4
| | | | | | | | Make it explicit that POWERLEVEL9K_DIR_MAX_LENGTH isn't the only constraint that may cause directory truncation. See the original description of #250 before this issue was repurposed for something unrelated.
* pull upstream changes from gitstatusromkatv2019-10-071-2/+3
|
* replace expansion-based Git status formatter with a functionromkatv2019-10-072-86/+168
|
* bug fix: respect POWERLEVEL9K_DISABLE_GITSTATUS; see #246romkatv2019-10-071-1/+4
|
* update docs to recommend cloning powerlevel10k git repo with --depth=1romkatv2019-10-071-4/+5
|
* remove git flag that has no effectromkatv2019-10-071-1/+1
|
* doc cleanupromkatv2019-10-071-1/+1
|