November 2007 - xmonad

Issue 84 in xmonad: Do our own recompilation checker
by codesite-noreply＠google.com 19 Nov '07

19 Nov '07

Issue 84: Do our own recompilation checker http://code.google.com/p/xmonad/issues/detail?id=84 Comment #1 by dons00: Implemented. GHC is now only invoked if the xmonad.hs file is newer than its accopmanying xmonad.o file. Cold starts are back to their usual blinding speed. Issue attribute updates: Status: Fixed -- 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

darcs patch: lots of edits/additions to Documentation.hs, small documentation fix for RotSlaves.hs
by Brent Yorgey 18 Nov '07

18 Nov '07

Sun Nov 18 16:58:58 EST 2007 Brent Yorgey <byorgey(a)gmail.com> * RotSlaves.hs: documentation fix. Sun Nov 18 16:55:41 EST 2007 Brent Yorgey <byorgey(a)gmail.com> * Documentation.hs: a lot more edits and additions.

2 1

Issue 90 in xmonad: Restarting xmonad re-runs dzen/xmobar, which puts it at the top of the window stack
by codesite-noreply＠google.com 18 Nov '07

18 Nov '07

Issue 90: Restarting xmonad re-runs dzen/xmobar, which puts it at the top of the window stack http://code.google.com/p/xmonad/issues/detail?id=90 New issue report by shachaf: What steps will reproduce the problem? 1. Run a status bar (I use dzen) from xmonad. 2. Open a window, and restart xmonad 3. Hide the gap What is the expected output? What do you see instead? The window should cover the status bar, but since xmonad ran it after running the window, the status bar covers the window. What version of the product are you using? On what operating system? Latest darcs, Ubuntu. Please provide any additional information below. Don Stewart has reproduced this on OpenBSD. If this error is due to a module from XMonadContrib, please tag this issue with 'Component-Contrib' below. 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

darcs patch: Prompt/Man.hs: remove docstring. (and 3 more)
by Joachim Fasting 18 Nov '07

18 Nov '07

Sun Nov 18 15:32:40 CET 2007 Joachim Fasting <joachim.fasting(a)gmail.com> * Prompt/Man.hs: remove docstring. Sun Nov 18 15:41:53 CET 2007 Joachim Fasting <joachim.fasting(a)gmail.com> * Actions/SinkAll.hs: update usage doc. Sun Nov 18 15:47:22 CET 2007 Joachim Fasting <joachim.fasting(a)gmail.com> * Prompt/XMonad.hs: minor typo in doc. Sun Nov 18 15:48:49 CET 2007 Joachim Fasting <joachim.fasting(a)gmail.com> * Prompt/*: add XConfig variable to keybindings in doc.

3 3

darcs patch: WindowNavigation: don't export the confi... (and 1 more)
by David Roundy 18 Nov '07

18 Nov '07

I'm ambivalent about whether this goes into 0.4. It's a pretty peripheral extension, so maybe this should go in so it'll change less on its second stable release. Or we could leave it out. I don't care. The default layout uses an extremely hokey computation of an average of the focussed and normal border colors, but it seems to give qualitatively reasonable colors anyhow. David Sat Oct 13 05:05:24 EDT 2007 Andrea Rossato <andrea.rossato(a)unibz.it> * WindowNavigation: don't export the config constructor and some haddock fixes I told to David I would have taken care of that: instead of exporting the config constructor we export 2 functions: navigateColor and noNavigateBorders. Updated documentation accordingly. Mon Oct 15 12:55:04 EDT 2007 David Roundy <droundy(a)darcs.net> * compute a reasonable navigation color based on focussed color.

3 3

does it make any sense?
by Andrea Rossato 18 Nov '07

18 Nov '07

Hi. Sorry if I keep bothering with that. I don't know why, but documentation is something I care quite a lot about, and I don't know if what I'm doing, which is also quire time consuming, is worthy. I'm writing the new Documentation module[1] as if it were a tutorial for haskell beginners or intermediate users who want to start playing with configuring xmonad. The idea, in part supported by David if I did correctly understand him, was to have an introduction to xmonad internals... ...which brings me to two question: 1. who should be the audience of a documentation like that, which remains a Haddock library documentation? 2. what is a user required to know in order to being actually able to configure xmonad? I mean, if I get it right, customizing the key bindings means dealing with a Data.Map.Map, with insertions, unions, and so forth. To be done explicitly in Haskell. Which makes configuration so powerful and everything so exciting. This is why we like XMonad, after all. This is why we did not write a window manager, but a library to let every user write a window manager in 3 lines of haskell! But if you don't know Haskell at all and don't care anything about it? I think I need some help documenting that: should I stick with my initial proposal or should we find a better way to write something targeted at a broader audience? i think that, in this second case, things get more complicated. And is it the right place for something intended for the general user? Any suggestion is welcome. Andrea [1] http://gorgias.mine.nu/xmonad/xmonad-contrib/Documentation.html

4 9

darcs patch: Prompt/Shell.hs: fix invalid module imp... (and 6 more)
by Joachim Fasting 18 Nov '07

18 Nov '07

Sat Nov 17 23:46:14 CET 2007 Joachim Fasting <joachim.fasting(a)gmail.com> * Prompt/Shell.hs: fix invalid module import in usage doc. Sun Nov 18 00:06:27 CET 2007 Joachim Fasting <joachim.fasting(a)gmail.com> * Prompt/Layout.hs: add missing import to usage doc. Sun Nov 18 00:07:34 CET 2007 Joachim Fasting <joachim.fasting(a)gmail.com> * Prompt/Man.hs: tweak import stuff in usage doc. Sun Nov 18 00:08:14 CET 2007 Joachim Fasting <joachim.fasting(a)gmail.com> * Prompt/Ssh.hs: fix import statements in usage doc. Sun Nov 18 00:08:54 CET 2007 Joachim Fasting <joachim.fasting(a)gmail.com> * Prompt/Window.hs: fix import statements in usage doc. Sun Nov 18 00:09:31 CET 2007 Joachim Fasting <joachim.fasting(a)gmail.com> * Prompt/Workspace.hs: update module description. Sun Nov 18 00:09:40 CET 2007 Joachim Fasting <joachim.fasting(a)gmail.com> * Prompt/Workspace.hs: suggest using defaultXPConfig in usage doc.

3 2

idea: split XConfig definition into its own file
by Brent Yorgey 17 Nov '07

17 Nov '07

Hi all, How do people feel about splitting the definition of XConfig out of Core.hsand into its own file, XConfig.hs? (It could then be re-exported from Core.hs, of course, so no changes would be required to anything else.) The point of this would be so people who are trying to write their xmonad.hs and want to see what fields are available don't have to wade through all of Core.hs to find it. Such an XConfig.hs would also be a good place to provide some nice, detailed Haddock documentation explaining what each of the different fields are, and how to use them. I'd be happy to make the changes myself, just thought I'd run it by the list first to see what people think. -Brent

3 4

darcs patch: some edits to Documentation.hs
by Brent Yorgey 17 Nov '07

17 Nov '07

Sat Nov 17 12:39:24 EST 2007 Brent Yorgey <byorgey(a)gmail.com> * Documentation.hs: various stylistic edits, add a few more details

2 2

help needed in the documentation effort
by Andrea Rossato 17 Nov '07

17 Nov '07

Hi, I've just pushed a patch that adds a module, called Documentation, that will allows us to use Haddock commands to produce a hyperlinked documentation of the xmonad-contrib library. Here's the documentation produced with the HEAD tree: http://gorgias.mine.nu/xmonad/xmonad-contrib/ and this is the specific module I'm talking about: http://gorgias.mine.nu/xmonad/xmonad-contrib/Documentation.html As you may see it is just a draft. There's the basic structure, but you can take it as a proposal. Please send you suggestions, comments, and patches!! I'm asking for help, especially from our users who are not really familiar with Haskell, or with the XMonad code base: helping in documenting it can be a quite useful learning experience (I know it because that's my experience too!). Moreover non expert can provide hints on what must be stressed most, especially for non experienced users. In order to help you need: 1. haddock[1] and the haddock documentation[2] 2. darcs to record and send patches (I'm sure you already have darcs installed!) 3. if you want to build the core (xmonad) documentation you need to build haddock with the attached patch, since by default it doesn't handle some of the newtype deriving used in XMonad.Core That's it. I'll try to keep the above link as updated as I can. Thanks for your kind attention. And for the forthcoming help! ;) Andrea [1] http://haskell.org/haddock/ [2] http://haskell.org/haddock/haddock-html-0.8/index.html

1 1