December 2007 - xmonad

Issue 99 in xmonad: common command line flags (version, replace, display)
by codesite-noreply＠google.com 10 Dec '07

10 Dec '07

Issue 99: common command line flags (version, replace, display) http://code.google.com/p/xmonad/issues/detail?id=99 Comment #1 by thomas.adam22: --display and --version are trivial. Would be nice also to have a --screen flag for xinerama, too. The point of this reply is to discuss how --replace might work, since it's not as trivial as people might think. When xmonad loads it should "register" itself as the running window manager. How it would do this is by interning a series of XAtoms which setup meta information about itself, such as: _IC_WM_MANAGER _IC_WM_VERSION _IC_WM_TIMESTAMP Then, using the XClientMessageEvent structure, fill it in. The XAtoms defined above would need changing via XChangeProperty(). Then just send the event of StructureNotifyMask along with the XClientMessageEvent structure. There's more to it than that, but that's the basic outline. -- 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

1 0

Issue 99 in xmonad: common command line flags (version, replace, display)
by codesite-noreply＠google.com 10 Dec '07

10 Dec '07

Issue 99: common command line flags (version, replace, display) http://code.google.com/p/xmonad/issues/detail?id=99 New issue report by jus...(a)justinbogner.com: The following command line flags would be nice: 1. --version should output the version of xmonad and quit 2. --display should set the X display, overriding the environment variable $DISPLAY 3. --replace should replace the running window manager (kill the current WM and start XMonad) Issue attributes: Status: New Owner: ---- Labels: Type-Defect Priority-Medium -- 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

1 0

ANNOUNCE: xmonad 0.5: a tiling window manager
by Don Stewart 09 Dec '07

09 Dec '07

The xmonad dev team is pleased to announce the 0.5 release of xmonad! http://xmonad.org xmonad is a tiling window manager for X. Windows are arranged automatically to tile the screen without gaps or overlap, maximising screen use. Window manager features are accessible from the keyboard: a mouse is optional. xmonad is extensible in Haskell, allowing for powerful customisation. Custom layout algorithms, key bindings and other extensions may be written by the user in config files. Layouts are applied dynamically, and different layouts may be used on each workspace. Xinerama is fully supported, allowing windows to be tiled on several physical screens. Features: * Very stable, fast, small and simple. * Automatic window tiling and management * First class keyboard support: a mouse is unnecessary * Full support for tiling windows on multi-head displays * Full support for floating windows * XRandR support to rotate, add or remove monitors * Per-workspace layout algorithms * Per-screens custom status bars * Easy, powerful customisation and reconfiguration in Haskell * Large extension library * Extensive documentation and support for hacking Get it! More information, screenshots, documentation, tutorials and community resources are available from the xmonad home page: http://xmonad.org The 0.5 release, and its dependencies, are available from hackage.haskell.org, here: http://hackage.haskell.org/cgi-bin/hackage-scripts/package/xmonad **The headlines** xmonad 0.5 is a major new release of xmonad, allowing, for the first time, dynamic extension in Haskell without requiring recompilation. Extension and configuration of xmonad is now faster, simpler, and more flexible. All configuration is done via the ~/.xmonad/xmonad.hs file. Example config files and screenshots are available on the wiki: http://haskell.org/haskellwiki/Xmonad/Config_archive This marks the final break from its dwm origins. As a result, xmonad is now also much easier to package, distribute and extend, as recompilation of xmonad is not required to extend it. New features: * xmonad is now a library, as is the collection of xmonad extensions * xmonad is configured by editing ~/.xmonad/xmonad.hs * simpler layout hooks type and interface * small EDSL for writing window management rules * support for ghc 6.8.x * xmonad now requires Cabal 1.2 or newer * small bug fixes Extensions: xmonad comes with a huge library of extensions (now more than 5 times the size of xmonad), contributed by viewers like you. Extensions enable pretty much arbitrary window manager behaviour to be implemented by users, in Haskell, in the config files. Examples include: * ion-like window tabs * status bar support * X property and hints support * altnerative layout algorithms For more information on using and writing extensions see the webpage. The library of extensions is available from hackage: http://hackage.haskell.org/cgi-bin/hackage-scripts/package/xmonad-contrib Brought to you by the xmonad team: Spencer Janssen Don Stewart Jason Creighton Andrea Rossato David Roundy Brent Yorgey with code contributions from: Brandon Allbery Chris Mears Shachaf Ben-Kiki Eric Mertens Alec Berryman Neil Mitchell Gwern Branwen Devin Mullins Joachim Breitner Daniel Neri Alexandre Buisse Stefan O'Rear Nick Burlett Simon Peyton Jones Peter De Wachter Hans Philipp Annen Aaron Denney Karsten Schoelzel Nelson Elhage Michael Sloan Shae Erisson Ivan Tarasov Joachim Fasting Alex Tarkovsky Michael Fellinger Christian Thiemann David Glasser Joe Thornber Kai Grossjohann Matsuyama Tomohiro Dave Harrison Daniel Wagner Juraj Hercek Ferenc Wagner Sam Hughes Jamie Webb Miikka Koskinen Klaus Weidner David Lazar nornagon Lucas Mai timthelion Robert Marlow Valery V. Vorotyntsev Dougal Stanton Joel Suovaniemi Mats Jansborg Dmitry Kurochkin Clemens Fruhwirth As well as the support of many others on the #xmonad and #haskell IRC channels, and the wider Haskell and window manager communities. Thanks to everyone for their support!

1 0

Issue 98 in xmonad: Conventional configuration strategies
by codesite-noreply＠google.com 09 Dec '07

09 Dec '07

Issue 98: Conventional configuration strategies http://code.google.com/p/xmonad/issues/detail?id=98 Comment #3 by dons00: We now have a config template: http://haskell.org/haskellwiki/Xmonad/Config_archive/Template_Config.hs That is farrly non-Haskell. And we will continue to improve EDSL support for configuration. It is not a priority though to develop a Haskell-lite syntax in front of xmonad. Issue attribute updates: Status: WontFix -- 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

1 0

Issue 68 in xmonad: Extension request: banish mouse pointer
by codesite-noreply＠google.com 09 Dec '07

09 Dec '07

Issue 68: Extension request: banish mouse pointer http://code.google.com/p/xmonad/issues/detail?id=68 Comment #5 by dons00: If someone is interested, write a mouse banishing extension. Issue attribute updates: Status: WontFix -- 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

1 0

Issue 82 in xmonad: Gap should be on by default
by codesite-noreply＠google.com 09 Dec '07

09 Dec '07

Issue 82: Gap should be on by default http://code.google.com/p/xmonad/issues/detail?id=82 Comment #2 by dons00: Bumped. Small issue. Issue attribute updates: Labels: -Milestone-Release0.5 Milestone-Release0.6 -- 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

1 0

Issue 73 in xmonad: xmonad as a library
by codesite-noreply＠google.com 09 Dec '07

09 Dec '07

Issue 73: xmonad as a library http://code.google.com/p/xmonad/issues/detail?id=73 Comment #6 by dons00: Done! Find template xmonad.hs file here: http://haskell.org/haskellwiki/Xmonad/Config_archive/Template_Config.hs Issue attribute updates: Status: Verified -- 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

1 0

Issue 98 in xmonad: Conventional configuration strategies
by codesite-noreply＠google.com 09 Dec '07

09 Dec '07

Issue 98: Conventional configuration strategies http://code.google.com/p/xmonad/issues/detail?id=98 Comment #1 by dons00: An example from Thomas. 1 -- Sample idea of what a non-xmonad/haskell config file might look like. 2 3 -- Set the modkey. 4 modkey = mod4 5 6 myConfig = { 7 borderWidth = 3 8 terminal = "urxvt +sb ...." 9 workspaces = "A", "B", "C", "D" 10 gaps = 15 0 0 0 11 modMask = modkey 12 .... 13 } 14 15 -- Layouts 16 layouts = tiled, mirror tiled, full (noBorders) 17 18 -- Keys 19 key a (shift) Kill 20 key right (control) rotview true 21 22 -- Mouse 23 mouse 1 focusNextWindow 24 25 -- Styles 26 Style (classname=Skype | resource=skype) StartWS A, Float 27 Style (classname=XClock) Float -- 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

3 2

Issue 98 in xmonad: Conventional configuration strategies
by codesite-noreply＠google.com 09 Dec '07

09 Dec '07

Issue 98: Conventional configuration strategies http://code.google.com/p/xmonad/issues/detail?id=98 Comment #2 by thomas.adam22: Thanks Don for that... My intention behind this proposed syntax is that is is sufficiently removed from haskell for it to be generic (i.e., does not enforce Haskell's syntax on the user), but close enough for it to be haskell so that some parser can be written. If that makes sense. Someone on IRC asked what they would do to make a ""global"" key-binding without the modifier -- if one looks at line 19, then that might be represented as: key (nomod) a kill (Potentially stupid in this example, but you get the point.) Again, line 26 (which is an abstract representation of what ManageHook might become, says that: "If a window has a class of 'skype' OR (|) a resource of 'skype' then move it to the WorkSpace of 'A' and put it in the floating layer". Hopefully that helps to clarify things a little. Kindly, Thomas Adam -- 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

1 0

Issue 98 in xmonad: Conventional configuration strategies
by codesite-noreply＠google.com 09 Dec '07

09 Dec '07

Issue 98: Conventional configuration strategies http://code.google.com/p/xmonad/issues/detail?id=98 New issue report by dons00: Now we have reconfigure without recompilation, we can consider non-Haskell mechanisms for configuration (such as a simple text format, or Xresources, or environment variables). A good choice here should ease adoption -- as users can get good results without needing haskell. Issue attributes: Status: Accepted Owner: dons00 Labels: Type-Enhancement Priority-Medium -- 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

1 0