From c3e0af6f89fba0e05d57561b597b652becd06b90 Mon Sep 17 00:00:00 2001 From: Patrick Ziegler Date: Tue, 11 Sep 2018 18:10:05 +0200 Subject: [PATCH] Updated Known Issues (markdown) --- Known-Issues.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Known-Issues.md b/Known-Issues.md index 1fdb194..a62bfdf 100644 --- a/Known-Issues.md +++ b/Known-Issues.md @@ -12,7 +12,7 @@ This page lists some of the issues one can encounter when using polybar. Either ## Click Commands are not Executed **Problem:** Some `click-*` commands are not executed when the bar is clicked. This is a bug that is triggered by the `click-*` command producing output on `stdout` or `stderr`. -**Workaround:** The `click-*` command must not produce any output, so redirect any output to `/dev/null`. This can be done by appending `>/dev/null 2>&1` to the `click-*` command. +**Workaround:** The `click-*` command must not produce any output, so redirect any output to `/dev/null`. This can be done by appending `>/dev/null 2>&1` to the `click-*` command (If you background the program with `&`, make sure that `&` is still at the very end). This issue was discovered in [`#916`](https://github.com/jaagr/polybar/issues/916).