[openbox] _OB_CONFIG_FILE property

Eric Bohlman ericbohlman at sbcglobal.net
Thu May 13 18:41:27 EDT 2010


Is there any reason why this property is set only if a config file is 
specified on the command line? It would save a bunch of guesswork in 
utilities like OBApps or OBMenu if it were set even if one of the 
default config files were used.

Speaking of utilities that read config files, there's been some 
discussion about having to set mouse bindings redundantly in multiple 
contexts. Would there be any demand for a simple command-line utility 
that would propagate mouse bindings from one context to one or more 
other contexts? e.g. something like "obmouse bottom left right" would 
take the mouse bindings for the "bottom" context and add them to the 
"left" and "right" contexts (obviously there would have to be some way 
to resolve conflicts). For that matter, is there any demand for a 
graphical mouse-binding utility? Now that OBApps is out, the mouse 
section seems to be the only part of the config file without an official 
or unofficial GUI.


More information about the openbox mailing list