salt/home
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Polybar, i3: Move Polybar launch handling out of its own script

Browse Source
This commit is contained in:
Salt 2017-08-20 21:56:47 -05:00
parent 94a7f5160a
commit db09ba9e0a
2 changed files with 2 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
.config/i3/config
View File

@ -57,7 +57,8 @@ font pango:Overpass 10
# Use in case of NODM/autlogin and .xinitrc -- If we're just starting the system, we need to lock it up.
exec --no-startup-id "i3lock -i ~/.i3splash"
exec_always --no-startup-id "sleep 3; ~/.config/polybar/launch.sh"
exec_always --no-startup-id "sleep 1; polybar top"
#exec_always --no-startup-id "sleep 1; polybar bottom"
exec --no-startup-id "redshift -l 38.627003:-90.199402"
exec_always --no-startup-id "compton --config ~/.config/compton.conf"
exec_always --no-startup-id "dunst"

12
.config/polybar/launch.sh
View File

@ -1,12 +0,0 @@
#!/usr/bin/env sh
# Terminate already running bar instances
killall -q polybar
# Wait until the processes have been shut down
while pgrep -x polybar >/dev/null; do sleep 1; done
# Launch bar1 and bar2
polybar top &
polybar bottom &
echo "Polybars launched..."