| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
send i3 messages and execute special py3status actions
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
module
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
extend it with our own modules without breaking i3status
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
modules methods were not always loaded in the same order and caused inconsistent ordering between reloads. thx to @guiniol for reporting.
|
| | |
|
| | |
|
| |
|
|
| |
py3status-modules-only i3bar
|