From fbe91c1b658c0ea1fd6fc60f946eead1be54d7c2 Mon Sep 17 00:00:00 2001 From: Michael Carlberg Date: Mon, 20 Jun 2016 17:05:23 +0200 Subject: [PATCH] fix(docs): Improved launch section --- README.md | 25 ++++++++++++++++++++++--- 1 file changed, 22 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 01064d00..f56b8eeb 100644 --- a/README.md +++ b/README.md @@ -133,10 +133,13 @@ into the project. When using the wrapper to start the bar in in your wm's autostart routine, make sure to include a kill directive before launching the bar. This is done to make sure that any previously spawned -processes gets terminated before before we launch the new ones. For example in -`$HOME/.config/bspwmrc`: +processes gets terminated before before we launch the new ones. + +Create an executable file containing the startup logic, for example `$HOME/.config/lemonbuddy/launch.sh`: ~~~ sh + #!/usr/bin/env sh + # Terminate already running bar instances lemonbuddy_terminate noconfirm @@ -147,7 +150,23 @@ processes gets terminated before before we launch the new ones. For example in echo "Bars launched..." ~~~ -If you are using i3, see [this issue](https://github.com/jaagr/lemonbuddy/issues/21) on how to display the bar. +If you are using **bspwm**, add the following line to `bspwmrc`: + + ~~~ sh + $HOME/.config/lemonbuddy/launch.sh + ~~~ + +If you are using **i3**, add the following line to your configuration: + + ~~~ sh + exec_always $HOME/.config/lemonbuddy/launch.sh + ~~~ + +Remember to make it executable using: + + ~~~ sh + $ chmod +x $HOME/.config/lemonbuddy/launch.sh + ~~~ ## Configuration