nagbalae/dunst
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

test keybindingavailabilty after initdbus

Browse Source 
The keybindings are always taken when there's already another instance
of dunst running. The binding-errors could hide the important error
message about another notification-daemon running
This commit is contained in:
Sascha Kruse 2012-09-10 20:50:28 +02:00
parent 3e3235f522
commit e04da92807
1 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
dunst.c
View File

@ -1713,12 +1713,6 @@ int main(int argc, char *argv[])
init_shortcut(&close_all_ks);
init_shortcut(&history_ks);
grab_key(&close_ks);
ungrab_key(&close_ks);
grab_key(&close_all_ks);
ungrab_key(&close_all_ks);
grab_key(&history_ks);
ungrab_key(&history_ks);
geometry.mask = XParseGeometry(geom,
&geometry.x, &geometry.y,
@ -1728,6 +1722,14 @@ int main(int argc, char *argv[])
initdbus();
initfont(dc, font);
grab_key(&close_ks);
ungrab_key(&close_ks);
grab_key(&close_all_ks);
ungrab_key(&close_all_ks);
grab_key(&history_ks);
ungrab_key(&history_ks);
colors[LOW] = initcolor(dc, lowfgcolor, lowbgcolor);
colors[NORM] = initcolor(dc, normfgcolor, normbgcolor);
colors[CRIT] = initcolor(dc, critfgcolor, critbgcolor);