January 2010 - xmonad

Re: Issue 352 in xmonad: Fail to build with darcs X11 binding
by codesite-noreply＠google.com 22 Mar '10

22 Mar '10

Updates: Summary: Fail to build with darcs X11 binding Comment #2 on issue 352 by vogt.adam: Fail to build with darcs X11 binding http://code.google.com/p/xmonad/issues/detail?id=352 (No comment was entered for this change.) -- 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 8

darcs patch: Add --replace flag with documentation (issue 99).
by Adam Vogt 12 Feb '10

12 Feb '10

Sun Dec 20 13:35:29 EST 2009 Adam Vogt <vogt.adam(a)gmail.com> * Add --replace flag with documentation (issue 99).

2 1

Re: Issue 99 in xmonad: Move XMonad.Util.Replace to core
by codesite-noreply＠google.com 12 Feb '10

12 Feb '10

Updates: Summary: Move XMonad.Util.Replace to core Status: Accepted Labels: -Priority-Medium Priority-Critical Milestone-Release1.0 Comment #5 on issue 99 by SpencerJanssen: Move XMonad.Util.Replace to core http://code.google.com/p/xmonad/issues/detail?id=99 We'd like to be able to replace window managers. This should be done via a --replace flag. We'll also need to make the replacement conditional. We should also take a look at Jan's original WM replacement patches for the core, they're on darcswatch. -- 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 3

Re: Issue 310 in xmonad: XMonad.Main.handle eats WM_NAME property changes
by codesite-noreply＠google.com 07 Feb '10

07 Feb '10

Updates: Status: Accepted Labels: Type-Defect Component-Core Comment #1 on issue 310 by byorgey: XMonad.Main.handle eats WM_NAME property changes http://code.google.com/p/xmonad/issues/detail?id=310 I can reproduce this. Could a core developer take a look at this? If it is really as easy as amdragon suggests (and the suggested fix wouldn't be undesirable for other reasons), this ticket has no excuse for still being open. =) -- 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 2

darcs patch: Correct warnings with ghc-6.12 (and 1 more)
by Adam Vogt 07 Feb '10

07 Feb '10

Mon Jan 18 11:20:58 EST 2010 Adam Vogt <vogt.adam(a)gmail.com> * Correct warnings with ghc-6.12 Changes include: - compatibility with base-4 or 3 (base-2 untested) by using extensible-exceptions. This adds an additional dependency for users of ghc<6.10) - list all dependencies again when -ftesting (change in Cabal-1.8.0.2) - remove unnecessary imports - suppress -fwarn-unused-do-bind, with appropriate Cabal-1.8 workaround, described here: http://www.haskell.org/pipermail/xmonad/2010-January/009554.html Mon Jan 18 11:22:56 EST 2010 Adam Vogt <vogt.adam(a)gmail.com> * Rename numlockMask to numberlockMask to help users of the template config. Without the change, the errors are like: > [ unrelated error messages ] > No constructor has all these fields: `numlockMask', > `terminal', [every other field set] With the change: > `numlockMask' is not a record selector > [ context where numlockMask is named ]

4 5

xmobar add-ons
by Jose A. Ortega Ruiz 07 Feb '10

07 Feb '10

Hi, I hope i'm not off-topic. I'm posting here because i haven't been able to contact Andrea, xmobar's maintainer, and i thought some of you might be interested in a couple of add-ons to xmobar that i've been hacking on: - two new monitors, MultiCpu and Disk, providing cpu usage for multicores and disk I/O speeds, respectively. - new options to all monitors to set maximum/minimum field widths and padding characters. The code is available in this darcs repo: <http://darcs.hacks-galore.org/jao/xmobar> which you can also browse on-line at <http://darcs.hacks-galore.org/darcsweb/jao?r=xmobar;a=summary> The additions are documented in the README file. Since this is my first Haskell hacking beyond tutorial snippets, i'm sure the code can be improved, so feel free to criticise it as deserved, or to ask for other improvements. Thanks! jao -- Humans think they are smarter than dolphins because we build cars and buildings and start wars etc., and all that dolphins do is swim in the water, eat fish and play around. Dolphins believe that they are smarter for exactly the same reasons. -Douglas Adams

5 7

xmonad under ghc 6.12.1 -- progress
by Brent Yorgey 07 Feb '10

07 Feb '10

Hi all, I've been continuing to work on getting xmonad to build under ghc 6.12.1. We're almost there (I've attached a patch for xmonad-contrib; the core is a different story, read on). The main problem with building under 6.12.1 was that it generated three new sorts of warnings on the xmonad codebase (which was incompatible with our policy of using -Werror while testing, aside from simply being ugly). * Redundant imports. I've fixed all of these, see the attached patch. * Unused do binds. Per a previous discussion, this warning is silly so I've added a clause in the .cabal files to disable it for ghc >= 6.12.1. * Deprecated Prelude. xmonad currently requires base < 4 (because we're using the old exceptions framework) but this now generates a warning under ghc 6.12.1 that base-3 will soon be deprecated. For now, I've disabled this warning (unfortunately, this means all OTHER deprecation warnings are disabled too). Really we ought to update to use the extensible-exceptions package, which supposedly would provide a smooth migration path allowing xmonad to build under both base-3 and base-4. I'll let someone who knows more about exception stuff handle this. A couple problems I ran into along the way: * Cabal doesn't correctly order the flags to GHC in a certain situation (if you want to know details, see the recent thread "infelicitous (incorrect?) ordering of flags passed to GHC" on cabal-devel@haskell [1]). To get around this I had to do some minor silly hacks in the .cabal files, like this: if true ghc-flags: -Wall if impl (ghc >= 6.12.1) ghc-flags: -fno-warn-unused-do-bind and so on; putting the "ghc-flags: -Wall" by itself with no 'if true', which ought to be equivalent, does not work, since the flags get passed to ghc in the other order and the -Wall overrides the earlier -fno-warn... * As soon as I thought I was about to get the xmonad core to compile cleanly with no warnings... I got a GHC panic. Oh joy! I will keep looking into this. Hopefully by the time the platform comes out it will include some ghc 6.12.x where x > 1 and does not exhibit this bug. In the meantime, I have attached a patch which updates xmonad-contrib to compile cleanly under ghc 6.12.1. I also tested under ghc 6.10.4 with this patch applied, so as far as I know it shouldn't change or break anything. -Brent [1] http://www.haskell.org/pipermail/cabal-devel/2010-January/006004.html

3 3

make DynamicLog prefix workspace names with number
by Omari Norman 01 Feb '10

01 Feb '10

Hi, Is there any easy way to get DynamicLog to prefix the names of workspaces with numbers? For instance, I have workspaces named "web", "mail" and "local"; I want these to show up in my xmobar as "1:web", "2:mail", and "3:remote". Of course I would just name the workspaces that way, but I also use DynamicWorkspaces, which would make that tricky. Thanks! --Omari

3 4

problem with urxvt -tr
by Jose A. Ortega Ruiz 28 Jan '10

28 Jan '10

Hi, I use urxvt with a transparent background, using the -tr switch (that is, this is a 'faked' transparency, no composite manager is running). When a floating window pops up in front of a tiled urxvt one, the latter flickers *very* noticeably. This also happens when the terminal is resized in any way (e.g., by switching to a different layout). Without the -tr switch, the problem disappears. Although this could be a bug in urxvt, the fact is that the flickering is absent in other window managers (i've tried sawfish, stumpwm and pekwm): with them, i can resize urxvt terminal windows (or put other windows in front of them) without any flickering. Is anyone else observing this behaviour? TIA, jao -- A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away. - Antoine de Saint-Exupery

1 0

Creating a new package with cabal-install
by Ralph Hofmann 28 Jan '10

28 Jan '10

I am just trying to follow this tutorial: http://www.haskell.org/haskellwiki/Xmonad/xmonad_development_tutorial As I would like to use cabal-install, I tried "cabal install" from the XMonadContrib directory to build and install the HelloWorld module, but I got an error message in section 2.3 of the tutorial: Resolving dependencies... Configuring xmonad-contrib-0.9.1... Preprocessing library xmonad-contrib-0.9.1... cabal: can't find source for Xmonad.Actions.HelloWorld in ., dist/build/autogen cabal: Error: some packages failed to install: xmonad-contrib-0.9.1 failed during the building phase. The exception was: exit: ExitFailure 1 What's wrong? Cheers, Ralph

2 2