From a135be6cc22ce2d2e7ef6fd1ef352eb07b811d66 Mon Sep 17 00:00:00 2001 From: Tobias Witek Date: Wed, 1 Jan 2020 13:58:30 +0100 Subject: [PATCH] [doc] autohide: Clarify usage fixes #513 --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index ad2f63e..ed889b7 100644 --- a/README.md +++ b/README.md @@ -182,6 +182,7 @@ This will create a file called `~/bumblebee-status-debug.log` by default. The fi ### Advanced Usage If you want to have a minimal bar that stays out of the way, you can use the `-a` or `--autohide` switch to specify a list of module names. All those modules will only be displayed when (and as long as) their state is either warning or critical (high CPU usage, low disk space, etc.). As long as the module is in a "normal" state and does not require attention, it will remain hidden. +Note that this parameter is specified *in addition* to `-m` (i.e. to autohide the CPU module, you would use `bumblebee-status -m cpu memory traffic -a cpu`). # Required Modules