[openbox] feature suggestion

Dana Jansens dana at orodu.net
Wed Sep 28 17:09:35 EDT 2011


On Wed, Sep 28, 2011 at 5:07 PM, Jorge Almeida <jjalmeida at gmail.com> wrote:
> Dana,
>
> May I suggest a feature, in case some day you decide to make some
> changes? (Not that it needs changing, but anyway...)
> I noticed the --restart flag, which, if I guessed right, forces
> openbox to exec into itself. As the manual says, it is useful only if
> the binary on disk differs from the active one, in the case of an
> upgrading. But what if something else (the environment, for example)
> has changed and you want to load the changes without killing the
> session? I think it would be simple to implement with a minimum of
> code: trap HUP signals  to induce the openbox process into exec'ing a
> certain program, say ~/.config/openbox/reload. If the session is
> started from openbox-session, the program might be a symlink to
> openbox-session, and so we would end up with a new openbox (with new
> environment, etc) but with the same children as before. (It might need
> some polishing, for example in the case of programs started from
> autostart and sent to the background, that might be duplicated...)
>
> Certainly not a priority, but interesting, I suppose.

You can use a restart action to run anything you'd like.  That
anything could be a script that sets ENV vars and then runs openbox
again.

Letting --restart take an argument to do the same thing might be cool.


More information about the openbox mailing list