4 Dec 2010 15:58
5 Dec 2010 22:03
New xmobar maintainer: request for comments
Hi, I've recently accepted Andrea Rossato's kind offer to take over maintainership of xmobar, and i wanted to ask for feedback to the community. My apologies for cross-posting to the cafe and xmonad, but xmobar didn't have a mailing list until a couple days ago. My immediate plans are to fix some low-hanging bugs, incorporate a handful of patches and contributions i have in my repo and make a new release (0.12). Besides that, i've created a mailing list (xmobar@..., http://projects.haskell.org/cgi-bin/mailman/listinfo/xmobar, also mirrored at gmane.comp.lang.haskell.xmobar) and i will move xmobar's homepage to http://projects.haskell.org/xmobar (not done yet). Perhaps more disruptingly, i'm thinking of moving source code management from darcs to git (right now, i maintain a _mirror_ at github, http://github.com/jaor/xmobar). But xmobar has a very lively user base and many contributors, and i wouldn't like to alienate or disturb anyone: would that move be frown upon by the community? I also plan to keep hacking and adding (not many) features to xmobar in the future, and would be delighted to hear from you: please, do not hesitate to send your feature requests or any other comment directly to me or to the new list. Thanks in advance for your feedback, and special thanks to Andrea for creating xmobar and giving me this great chance of being more than a mere spectator of the haskell world.(Continue reading)
7 Dec 2010 16:22
Re: Issue 11 in xmobar: Abnormally high cpu load on X
Comment #26 on issue 11 by klu...@...: Abnormally high cpu load on X http://code.google.com/p/xmobar/issues/detail?id=11 I still see this problem, with the following versions: xmobar: 0.9.2 (Ubuntu) xmonad: 0.9.1 (Ubuntu) xorg: 1:7.5+5ubuntu1 linux: 2.6.32-25 If I'm reading this bug report correctly, those are versions for which the problem was thought to be solved. If I'm wrong and just need to update my software, that's good, too. Attachments: xorg.conf 499 bytes xmonad.hs 1.3 KB .xmobarrc 869 bytes
7 Dec 2010 17:46
Re: Issue 11 in xmobar: Abnormally high cpu load on X
Comment #27 on issue 11 by klu...@...: Abnormally high cpu load on X http://code.google.com/p/xmobar/issues/detail?id=11 Here's an ltrace of xmobar running under my configuration. I'm pretty sure ltrace caused xmobar to crash after a while, so take it with a grain of salt. -Eric Attachments: xmobar.trace 2.9 KB
7 Dec 2010 20:54
Re: Issue 31 in xmobar: MPD plugin does not respect common arguments
Updates: Status: Accepted Comment #2 on issue 31 by jaortega: MPD plugin does not respect common arguments http://code.google.com/p/xmobar/issues/detail?id=31 (No comment was entered for this change.)
7 Dec 2010 20:58
Re: Issue 31 in xmobar: MPD plugin does not respect common arguments
Updates: Owner: jaortega Comment #3 on issue 31 by jaortega: MPD plugin does not respect common arguments http://code.google.com/p/xmobar/issues/detail?id=31 (No comment was entered for this change.)
8 Dec 2010 00:00
Re: Issue 24 in xmobar: swap <usedratio> always displays zero
Comment #3 on issue 24 by jaortega: swap <usedratio> always displays zero http://code.google.com/p/xmobar/issues/detail?id=24 The git repo now contains a fix for the off-by-100 issue. Regarding %, there's a new option, -P, which switches it on/off.
8 Dec 2010 00:04
Re: Issue 25 in xmobar: memory <usedratio> doesn't include percent symbol
Comment #5 on issue 25 by jaortega: memory <usedratio> doesn't include percent symbol http://code.google.com/p/xmobar/issues/detail?id=25 I've pushed a patch in the git repo whereby including % is controlled by a new per-plugin flag, -P, which can be set to either True (the default) or False. I could be persuaded to set it to False by default, but using True seemed the less surprising option for old users.
8 Dec 2010 00:07
Re: Issue 26 in xmobar: Add a Run Once for executing external commands
Comment #2 on issue 26 by jaortega: Add a Run Once for executing external commands http://code.google.com/p/xmobar/issues/detail?id=26 I've implemented this feature in the git repo by letting the refresh rate to be 0 (or a negative value) to denote "run once" (instead of introducing new syntax). Thus, now one can write Run Com "uname" ["-s", "-r"] "" 0 and uname will be run just once.
8 Dec 2010 00:11
Re: Issue 31 in xmobar: MPD plugin does not respect common arguments
Comment #4 on issue 31 by jaortega: MPD plugin does not respect common arguments http://code.google.com/p/xmobar/issues/detail?id=31 This is now fixed in the git repo.
RSS Feed