Re: Issue 313 in xmonad: Merge contrib's isFullscreen and doFullFloat to core

Comment #6 on issue 313 by gwern0: Merge contrib's isFullscreen and doFullFloat to core http://code.google.com/p/xmonad/issues/detail?id=313 The next release from darcs will be 1.0; is there any particular reason the change hasn't been made & pushed, or this bug closed? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

Comment #7 on issue 313 by audunska...@gmail.com: Merge contrib's isFullscreen and doFullFloat to core http://code.google.com/p/xmonad/issues/detail?id=313 I am not convinced that a doFullFloat is the right way to handle fullscreen; this should be up to the user to decide. I would therefore go against putting this hook into the default config. Making it available in core seems resonable though. There is a module now called XMonad.Layout.Fullscreen that sends messages to let the layouts themselves decide what to do with fullscreen windows; this seems to me like a more xmonadish way of doing things. As long as we want to provide several ways of handling fullscreen, providing a default seems counter productive. BTW, thanks for the improved fullscreen query (from alexey). I will look into using it for X.L.Fullscreen. Disclaimer: I'm the author of the mentioned module.

Comment #8 on issue 313 by icarnales: Merge contrib's isFullscreen and doFullFloat to core http://code.google.com/p/xmonad/issues/detail?id=313 Maybe adding entry in the defaultConfig manageHook to add a default behaviour to float windows? Some "custom" actions like floating Mplayer and Gimp are being done there, so I think is no harm.
participants (1)
-
codesite-noreply@google.com