No, xmonad uses a different dynamic extension model based on the OS
process. To dynamically upgrade an xmonad process, you,
* modify the source (i.e. the config file)
* hit mod-q, which triggers:
+ linking of the config file into the application library, creating
a new xmonad binary on disk.
+ the application state is serialized to a string representation
+ the new xmonad is then (double) forked with the old state as
input
* the new version of the app is running with the state of the old app.
You can do similar things at a finer grain of control via plugins.
dstcruz:
> Most awesome!
>
> Does xmonad make use of this library?
>
> Daniel
> _______________________________________________
> Haskell-Cafe mailing list
> Haskell-Cafe@haskell.org
> http://www.haskell.org/mailman/listinfo/haskell-cafe
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
