July 2007 - xmonad - Haskell.org

X Events in a Status Bar
by Andrea Rossato 17 Jul '07

17 Jul '07

Hi, I'm fighting with my personal ignorance and intellectual limitations without seeing any end. Supposed you have a window that displays a string that is the concatenation of a list (of unknown length) of MVars, written by forked threads with unknown frequencies. You could check if any single variable has been updated after a given amount of time, but it is quite probable that some of them have been updated in that period of time. So you just end up reading them periodically, and displaying what can be displayed. This stupid reading happens in a recursive loop. Now, how can you handle X Events in such a situation and specifically an Exposure event? You could stop the loop and wait for the event to occur, but you need to update the display since some MVar have change in the meantime. You could wait for the event for some time and then update anyway. It's a less stupid way of reading, but I cannot find any function to achieve this result. You could just forget about it, keep on updating periodically, but then someone is going to say that your status bar has refresh issues (who cares? Once I started it I'm not going to cover it, so no Exposure event handling is needed here. If you have a problem with that send a patch, it could even be applied...;-). Actually I think I'm not able to find a working solution in a limited amount of time, no matter how huge that amount is. But since I keep reading that in order to code Haskell you must be very smart, I thought I could ask here, before giving up...;-) Ciao Andrea

2 4

[dzen] Color support for arbitrary parts of the input
by Robert Manea 17 Jul '07

17 Jul '07

Hi, I just added support for coloring arbitrary parts of a line to dzen. Anyone who wants to give it a first try should grab the svn version: svn checkout http://dzen.googlecode.com/svn/trunk/ dzen HEADS UP, the syntax has changed: echo 'Default colors ^fg(blue)I'm blue ^bg(green)^fg(#ffffff)and I'm white on green' | dzen2 -p As you see, you can place the ^fg(color) and ^bg(color) commands anywhere into the text in any combination. The set colors will be used until you define a new one on a per line basis (similar to terminal escape seqs.) Both commands accept either symbolic color names or #rrggbb hex-values. If you need to display '^' characters just double them '^^' in order to escape the special meaning. The code is not perfect and I'll be happy to see some testing and possible bug reports before release. There is one known problem in menu mode, i.e. colored text will be printed as is. I'll look into solving this issue in the next couple of days. Bye, Rob. P.S.: With this parsing method it is rather easily possible to support icons in dzen. So this will be a priority TODO as soon as the parser is stable and I found a suitable icon format.

2 1

[DARCS] Failed to compile
by Xavier Maillard 17 Jul '07

17 Jul '07

Hi, I did a darcs pull in Xmonad and XmonadContrib and it failed with these errors: [13 of 14] Compiling Config ( Config.hs, dist/build/xmonad/xmonad-tmp/Config.o ) Config.hs:99:38: Couldn't match expected type `Layout Window' against inferred type `TConf -> Layout Window' Probable cause: `tabbed' is applied to too few arguments In the second argument of `($)', namely `tabbed shrinkText' In the expression: simpleStacking $ (tabbed shrinkText) Config.hs:181:51: Couldn't match expected type `Maybe WorkspaceId' against inferred type `WorkspaceId' Expected type: Maybe WorkspaceId -> X b Inferred type: WorkspaceId -> X () In the second argument of `(>>=)', namely `f' In the expression: (screenWorkspace sc) >>= f I did a setup.lhs clean before doing anything else. What could I do ? Regards, Xavier

3 5

darcs patch: Commands.hs: no more hs-boot modifications required - ...
by Andrea Rossato 16 Jul '07

16 Jul '07

hi, patch description says it all. ciao andrea Mon Jul 16 20:15:40 CEST 2007 Andrea Rossato <andrea.rossato(a)unibz.it> * Commands.hs: no more hs-boot modifications required - added to MetaModule I tried to change this module as little as I could, and just to remove the need of hs-boot modification. Now runCommands takes a list of commands that the user must set in Config.hs (as reported in Usage). Commands.workspaceCommands requires the number of workspaces. Removed defaultCommands and divided commands into categories. Afterall a little to change to keep track of this module.

1 0

Error compiling Commands.hs
by Kai Grossjohann 16 Jul '07

16 Jul '07

A couple of minutes ago, I ran "darcs pull" for the main xmonad repo and for the contrib repo. Then I did "Setup.lhs clean", followed by "Setup.lhs configure ...", followed by "Setup.lhs build". The build fails with this error: | [11 of 13] Compiling XMonadContrib.Commands ( XMonadContrib/Commands.hs, | dist/build/xmonad/xmonad-tmp/XMonadContrib/Commands.o ) | | XMonadContrib/Commands.hs:69:73: | Couldn't match expected type `Maybe WorkspaceId' | against inferred type `WorkspaceId' | Expected type: Maybe WorkspaceId -> X () | Inferred type: WorkspaceId -> X () | In the second argument of `(>>=)', namely `f' | In the expression: (screenWorkspace (fromIntegral sc)) >>= f | make: *** [build] Error 1 Is it just me? Kai

4 4

darcs patch: fixes Commands.hs
by Andrea Rossato 16 Jul '07

16 Jul '07

Hi, this patch fixes the issue in Commands.hs reported by Kai Grossjohann. ciao andrea Mon Jul 16 18:40:17 CEST 2007 Andrea Rossato <andrea.rossato(a)unibz.it> * fixes Commands.hs

2 1

darcs patch: MetaModule.hs: add missing modules.
by joachim.fasting＠gmail.com 16 Jul '07

16 Jul '07

Sun Jul 15 22:58:57 CEST 2007 joachim.fasting(a)gmail.com * MetaModule.hs: add missing modules.

2 1

Issue 34 in xmonad: focusedBorderColor does not follow focus that is requested by application
by codesite-noreply＠google.com 14 Jul '07

14 Jul '07

Issue 34: focusedBorderColor does not follow focus that is requested by application http://code.google.com/p/xmonad/issues/detail?id=34 Comment #1 by JinXiaoyong: I did a bit research tonight and I think it might not be possible for window manager to detect that kind of events. It worked for me when I use fvwm, because I let the mouse move along with the focus so that the crossing event is always detected. It seems I can't close this bug report here. -- 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

Patch: unbreak Magnifier
by Peter De Wachter 13 Jul '07

13 Jul '07

This patch unbreaks Magnifier, which was broken since the move to LayoutHelpers. I do remember sending this before, but it must have been eaten somewhere along the way.

2 1

xmobar-0.6 "The Existentialist" released!
by Andrea Rossato 13 Jul '07

13 Jul '07

Hi! I've just released xmobar-0.6 "The Existentialist", my status bar for XMonad. Grab the source here: http://hackage.haskell.org/cgi-bin/hackage-scripts/package/xmobar-0.6 Screen shot: http://gorgias.mine.nu/xmobar/xmobar-0.6.png If you cannot wait for ghc to do his job, here you can find a binary with 2 sample configuration files: http://gorgias.mine.nu/xmobar/ About this release: 1. Plugin support. I've already sent a mail regarding the way through which I decided to add plugin support,[1] so I'm not giving details here. There is an example within the distribution: Plugins/HelloWorld.hs See below (or the README) for instruction on how to install it. The precompiled binary linked above was compiled with it. In the README there are instructions on how to write plugins (should be very easy, I hope at least); 2. new way of configuring commands (resulting from the above change): I hope that makes it easier to configure XMobar: no more tuples but a single command prefixed by "Run". See the configuration samples and instruction in the README; 3. colors are off by default now, and you need to configure them explicitly. See the config sample or the README to find out how. 4. Performance: I did quite some profiling. The most resource consuming part was the network monitor. So I rewrote it. Now XMobar should be quite optimized. Test and report back please. There's room for more optimization I think, but the results so far seem good to me. Hope you'll enjoy. All the best, Andrea [1] My previous mail about existential plugin-ing: http://www.haskell.org/pipermail/xmonad/2007-July/001413.html To install the HelloWorld plugin: 1. import the plugin module in Config.hs, by adding: import Plugins.HelloWorld 2. add the plugin data type to the list of data types in the type signature of "runnableTypes" in Config.hs. For instance, for the HelloWorld plugin, change "runnableTypes" into: runnableTypes :: (Command,(HelloWorld,())) runnableTypes = undefined 3. Rebuild and reinstall XMobar. Now test it with: xmobar Plugins/helloworld.config As you may see in the example configuration file, the plugin can be used by adding, in the "commands" list: Run HelloWorld and, in the output template, the alias of the plugin: %helloWorld% That's it.

1 0