From 2f9625ea1e26f28e0b2eb4669c5f7fae7a0b70ee Mon Sep 17 00:00:00 2001 From: Patrick Ziegler Date: Wed, 5 Jun 2019 20:57:54 +0200 Subject: [PATCH] Updated Known Issues (markdown) --- Known-Issues.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Known-Issues.md b/Known-Issues.md index bbb89f4..dcdb708 100644 --- a/Known-Issues.md +++ b/Known-Issues.md @@ -109,6 +109,8 @@ This behaviour was introduced in [`#831`](https://github.com/polybar/polybar/pul **Workaround:** The workaround that some people use, is to create a full-width fully transparent dummy bar on the same monitor and in the same position (with `override-redirect = false`), so that i3 reserves space for this dummy bar, effectively also reserving space for our actual bar. The real bar may need to have `wm-restack = i3` set for it to not overlap with fullscreen windows. **Note:** This requires that you have a composition manager running because the dummy bar may overlap the real bar. +If you are using i3-gaps (branch `gaps-next` or version `4.17` once it's released), you can set `gaps top X` or `gaps bottom X` in your i3 config to reserve space for the bar where `X` is the number of pixels you want to reserve. **Note:** On multi-monitor setups this will be applied to all monitors. + ## Version Mismatch between `xcb-proto` and `libxcb-randr0-dev` on Ubuntu 17.04 **Problem:** On Ubuntu 17.04 (and possibly others), the `xcb-proto` version does not match the version of the `libxcb-*` packages, especially `libxcb-randr0-dev`. This creates problems with the header files. If you get the following or a similar compiler error, this fix may be for you: ~~~