dc47491533
ClientPatterns might be tricky to get right. Instead of fiddling around in
either the keys-file or the apps-file and restarting fluxbox to see if the
changes had any effect / matched the right windows, 'ClientPatternTest' and
the fluxbox-remote should make this easier:
$> fluxbox-remote "clientpatterntest (title=.*vim*)"
This causes fluxbox to store the list of matched windows in the
_FLUXBOX_ACTION_RESULT property onto the rootwindow. This property might
then be read by:
$> xprop -root _FLUXBOX_ACTION_RESULT
or
$> fluxbox-remote result
The format of the list is:
win_id \t title_of_window \n
win_id is '-1' when fluxbox wasn't able to parse the given ClientPattern.
win_id is '0' when there are no windows matching the given ClientPattern.
|
||
|---|---|---|
| .. | ||
| fbrun | ||
| fbsetbg | ||
| fbsetroot.cc | ||
| fbsetroot.hh | ||
| fluxbox-generate_menu.in | ||
| fluxbox-remote.cc | ||
| fluxbox-update_configs.cc | ||
| Makefile.am | ||
| startfluxbox.in | ||