mirror of
https://github.com/polybar/polybar.git
synced 2024-11-11 13:50:56 -05:00
8afd5b71df
* Remove DEBUG_SHADED Was disabled by default AND behind an #if 0 * Make TimerHandle expose more libuv functions * Prepare for moving double clicks into eventloop * Make eventloop available to bar * Remove bar mutex Everything in the bar is now in the same thread * Move double-click handling to eventloop * Extract double click deferred function into method * Stop throttling clicks * Increase double click interval to 400 and add option double-click-interval in the bar section Closes #1441 * Implement dimming using timer handles * Remove taskqueue * Remove unused dependencies * Cleanup & Comments
10 KiB
10 KiB
Changelog
All notable changes to this project will be documented in this file.
Each release should have the following subsections, if entries exist, in the
given order: Breaking
, Build
, Deprecated
, Removed
, Added
, Changed
,
Fixed
, Security
.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
Unreleased
Breaking
- We added the backslash escape character (\) for configuration values. This
means that the literal backslash character now has special meaning in
configuration files, therefore if you want to use it in a value as a literal
backslash, you need to escape it with the backslash escape character. The
parser logs an error if any unescaped backslashes are found in a value. This
affects you only if you are using two consecutive backslashes in a value,
which will now be interpreted as a single literal backslash.
#2354
- We rewrote our tag parser. This shouldn't break anything, if you experience
any problems, please let us know.
The new parser now gives errors for certain invalid tags where the old parser
would just silently ignore them. Adding extra text to the end of a valid tag
now produces an error. For example, tags like
%{T-a}
,%{T2abc}
,%{rfoo}
, and others will now start producing errors. This does not affect you unless you are producing your own formatting tags (for example in a script) and you are using one of these invalid tags.
Build
- New dependency: libuv. At least version 1.3 is required.
- Bump the minimum cmake version to 3.5
- The
BUILD_IPC_MSG
option has been renamed toBUILD_POLYBAR_MSG
- Building the documentation is now enabled by default and not just when
sphinx-build
is found. - Users can control exactly which targets should be available with the following
cmake options (together with their default value):
BUILD_POLYBAR=ON
- Builds thepolybar
executableBUILD_POLYBAR_MSG=ON
- Builds thepolybar-msg
executableBUILD_TESTS=OFF
- Builds the test suiteBUILD_DOC=ON
- Builds the documentationBUILD_DOC_HTML=BUILD_DOC
- Builds the html documentation (depends onBUILD_DOC
)BUILD_DOC_MAN=BUILD_DOC
- Builds the manpages (depends onBUILD_DOC
)BUILD_CONFIG=ON
- Generates sample configBUILD_SHELL=ON
- Generates shell completion filesDISABLE_ALL=OFF
- Disables all above targets by default. Individual targets can still be enabled explicitly.
- The documentation can no longer be built by directly configuring the
doc
directory. - The sample config file is now placed in the
generated-sources
folder inside whatever folder you invokedcmake
from instead of in the root folder of the repository. - The
POLYBAR_FLAGS
cmake variable can be used to pass extra C++ compiler flags.
Deprecated
[settings]
:throttle-output
andthrottle-output-for
have been removed. The new event loop already does a similar thing where it coalesces update triggers if they happen directly after one another, leading to only a single bar update.
Removed
DEBUG_SHADED
cmake variable and its associated functionality.
Added
drawtypes/ramp
: Add support for ramp weights. (1750)internal/memory
: New tokens%used%
,%free%
,%total%
,%swap_total%
,%swap_free%
, and%swap_used%
that automatically switch between MiB and GiB when below or above 1GiB. (2472
)- Option to always show urgent windows in i3 module when
pin-workspace
is active (2374
) internal/xworkspaces
:reverse-scroll
can be used to reverse the scroll direction when cycling through desktops.- The backslash escape character (\).
#2354
- Warn states for the cpu, memory, fs, and battery modules.
(
#570
,#956
,#1871
,#2141
)internal/battery
:format-low
,label-low
,animation-low
,low-at = 10
.internal/cpu
:format-warn
,label-warn
,warn-percentage = 80
internal/fs
:format-warn
,label-warn
,warn-percentage = 90
internal/memory
:format-warn
,label-warn
,warn-percentage = 90
radius
now affects the bar border as well (#1566
)- Per-corner corner radius with
radius-{bottom,top}-{left,right}
(#2294
) internal/network
:speed-unit = B/s
can be used to customize how network speeds are displayed.internal/xkeyboard
:%variant%
can be used to parse the layout variant (#316
)- Added .ini extension check to the default config search.
(
#2323
) - Config option to hide a certain module
(
hidden = false
) (#2108
) - Actions to control visibility of modules
(
module_toggle
,module_show
, andmodule_hide
) (#2108
) internal/xworkspaces
: Make the urgent hint persistent (#1081
)internal/network
:interface-type
may be used in place ofinterface
to automatically select a network interface (#2025
)internal/xworkspaces
:%nwin%
can be used to display the number of open windows per workspace (#604
)internal/backlight
: addeduse-actual-brightness
option- Added
wm-restack = generic
option that lowers polybar to the bottom of the stack. Fixes the issue where the bar is being drawn on top of fullscreen windows in xmonad. (#2205
) - Added
occupied-scroll = true
option to bspwm module. Allows scrolling only through occupied desktops only. (#2427
) custom/ipc
:send
action to send arbitrary strings to be displayed in the module. (#2455
)- Added
double-click-interval
setting to the bar section to control the time interval in which a double-click is recognized. Defaults to 400 (ms) (#1441
)
Changed
- We rewrote polybar's main event loop. This shouldn't change any behavior for the user, but be on the lookout for X events, click events, or ipc messages not arriving and the bar not shutting down/restarting properly and let us know if you find any issues.
- Slight changes to the value ranges the different ramp levels are responsible for in the cpu, memory, fs, and battery modules. The first and last level are only used for everything at or below and at and above the edges of the value range, respectively. The other levels are evenly distributed over the value range as before.
custom/script
:interval
now defaults to 0 iftail = true
as per the documentation.internal/network
:- Increased precision for upload and download speeds: 0 decimal places for KB/s (as before), 1 for MB/s and 2 for GB/s.
- Clicks arriving in close succession, no longer get dropped. Before polybar would drop any click that arrived within 5ms of the previous one.
- Increased the double click interval from 150ms to 400ms.
Fixed
- Trailing space after the layout label when indicators are empty and made sure right amount
of spacing is added between the indicator labels, in the xkeyboard module.
(
#2292
) - Parser error if click command contained
}
(#2040
) - Slight imprecision when calculating percentages. This caused the volume
reported by alsa to be off by one.
(
#2399
) internal/backlight
: With amdgpu backlights, the brightness indicator was slightly behind. (#2367
)- Warning message regarding T@ in bspwm module
(
#2371
) polybar -m
used to show both physical outputs and randr monitors, even if the outputs were covered by monitors. (#2481
)internal/xworkspaces
: Broken scroll-wrapping and order of workspaces when scrolling (#2491
)
3.5.7 - 2021-09-21
Fixed
- The tray mistakenly removed tray icons that did not support XEMBED
(
#2479
,#2442
) custom/ipc
: Only the first appearance of the%pid%
token was replaced (#2500
)
3.5.6 - 2021-05-24
Build
- Support building documentation on sphinx 4.0 (
#2424
)
Fixed
3.5.5 - 2021-03-01
Build
- Support older python sphinx versions again (
#2356
)
3.5.4 - 2021-01-07
Fixed
- Wrong text displayed if module text ends with
}
(#2331
)
3.5.3 - 2020-12-23
Build
- Don't use
git
when building documentation (#2309
)
Fixed
- Empty color values are no longer treated as invalid and no longer produce an error.