- xmonad - Haskell.org

darcs patch: runLayout is now a LayoutClass method an... (and 1 more)
by Andrea Rossato 25 Feb '08

25 Feb '08

Hi, since I'm starting to believe that the new version of runLayout is quite a interesting addition to the LayoutClass, I invested a bit on it and I ported Choose (it took me a second, actually... just some point-free to get rid of). I think I will port ModifiedLayout and the other David's combinators too. Then I'll start buzzing Spenser and Donald with hourly spam messages (crontab will be my friend with that), till those changes will be included in the core - or I'll be persuaded of their uselessness. Cheers, Andrea Fri Feb 22 18:58:15 CET 2008 Andrea Rossato <andrea.rossato(a)unibz.it> * runLayout is now a LayoutClass method and takes the Workspace and the screen Rectangle Fri Feb 22 20:31:19 CET 2008 Andrea Rossato <andrea.rossato(a)unibz.it> * Reimplement Choose with runLayout

4 4

my repositories
by Andrea Rossato 24 Feb '08

24 Feb '08

Hi, while talking with Roman it came up the problem of applying patches from the mailing list. I understand it, and I understand that sending patches to the mailing list, when you have write access to the repository, should be avoided when possible. Unfortunately the last issues to be solved require core support: 1. the way Combo handles focus interacts not very well with keayboard window move/resize. This is a known issue, and David sent a proposal for nested stacks.[1] As far as I know no comments or follow up were posted by core developers; 2. PerWorkspace doesn't implement emptyLayout (and has some other issues). This requires some core support. Brent sent a proposal for that support [2] and a new PerWorkspace implementation [3] but, as far as I know, no comments or follow up were posted by core developers; I also sent my proposal, as you know. But this was just 2 days ago; 3. Issue #111: my first proposal for just 3 days old, so we will have to wait a few weeks before start complaining for delays in its review. While I find strange the fact that half of the members of what is called the "xmonad team" are forced to run patched versions of xmonad (and not to develop new features, but just to run the features they have been coding for), still this is the case. The only thing I can do to make it easier for the brave ones who want test the code I run - without any warranty that it will be included in the core - is to public my own repositories: http://gorgias.mine.nu/repos/xmonad/ http://gorgias.mine.nu/repos/xmonad-contrib/ >From now on I'll only put there my contributions, without spamming this list anymore. Cheers, Andrea [1] http://www.haskell.org/pipermail/xmonad/2007-December/003972.html [2] http://www.haskell.org/pipermail/xmonad/2008-February/004632.html [3] http://www.haskell.org/pipermail/xmonad/2008-February/004635.html

3 2

darcs patch: Fix haddock hyperlink.
by Roman Cheplyaka 24 Feb '08

24 Feb '08

Sun Feb 24 22:54:16 EET 2008 Roman Cheplyaka <roma(a)ro-che.info> * Fix haddock hyperlink.

2 1

darcs patch: Applicative instance for X; new startupHook
by Brent Yorgey 24 Feb '08

24 Feb '08

Hi all, Here are two patches to the core, one to add an Applicative instance for X, and another which adds a startupHook :: X () to the config. I wrote them to support updates to PerWorkspace (patch to follow shortly), but I think they're both useful in and of themselves, especially the startupHook. Mon Feb 4 14:24:45 EST 2008 Brent Yorgey <byorgey(a)gmail.com> * Add a startupHook. The only thing I am not sure about here is at what exact point the startupHook should get run. I picked a place that seems to make sense: as late as possible, right before entering the main loop. That way all the layouts/workspaces/other state are set up and the startupHook can manipulate them. Mon Feb 4 14:23:48 EST 2008 Brent Yorgey <byorgey(a)gmail.com> * Core.hs: add an Applicative instance for X

2 7

Remote Controlling XMonad: Cases and Materials
by Andrea Rossato 24 Feb '08

24 Feb '08

Hi, this is a follow up of the thread started by Zed Lopez[1] on controlling XMonad remotely. Stefan O'Rear proposed a solution[2] and I implemented it[3]. We briefly discussed this solution on the #xmonad channel[4] and I thought some more documentation was needed on the methodology to use to achieve the goal. allbery_b reported that such an approach has been used by Mozilla, so I wanted to find more examples to study. Zed said that it was missing this feature from Ratpoison.[5] BTW, the successor of Ratpoison, Stumpwm is developed in Common Lisp...;-) So I went to have a look at how ratpoison deals with the subject and this is what I discovered[7,8]. This is what happens in Ratpoison: a. the Client (that sends the command): 1. creates w simple window 1 pixel width 2. sets an atom (RP_COMMAND) with a command to that window 3. sets an atom (RP_COMMAND_REQUEST) in the root window with XChangeProperty: this atom carries the first window id 4. waits for a propertyNotify to be sent to this window b. Ratpoison: 1. gets the property of the root window (which will return the id of the window containing the command string) 2. searches the window with the command string and executes the command 3. writes an atom (RP_COMMAND_RESULT) to the window with the command result. This will send the propertyNotify the will unblock the client. A similar approach is also used by Enlightment (see src/comms.c) and its remote shell Eesh (see Eesh.xs). WMII, instead, uses libipx and a Plan9 approach (I must confess I don't know much about P9), while DWM has no remote control capability. Now, attached you'll find two archives. The first one is a simple way of running commands from an external program, without a two way communication. It is basically a refactoring of the patch I've already sent[3]. It is simple and effective. I had no problem running it here. The second archive (xrcRatpoisonWay.tar.gz) instead is the ratpoison implementation: I literally copied the algorithm. And there's is a problem. This code produces an X server crash every now and then. I cannot reproduce it and, no matter how many times I read it, I cannot find a bug in my code. I believe there's something wrong with Xlib.Extras.rawGetWindowProperty (a null pointer?). Indeed if you change in ServerMode.hs: let c' = Just [118,105,101,119,49] --c' <- io $ getWindowProperty8 dpy c win no more crashes. You may also see that the command execution sometimes fails. Is that something that used to happen in Ratpoison too? Anyway it is something I think it is worth to investigate a bit more. And I think I will. BTW, these patches require a vary small modification to XMonad itself. XMonad has just to wait for a propertyNotify event sent to the root window. If that happens a hook is called (I named that hook serverHook). I do not want you to equivocate: I'm not pushing for this patch to be included, but I thought to report here some of the information I was able to gather on the subject. Moreover, as far as I can understand, there's is not so much interest in this feature. But here this stuff proved to be quite addictive...;-) Thanks for your kind attention. Andrea [1] see http://www.haskell.org/pipermail/xmonad/2007-July/001502.html [2] see http://www.haskell.org/pipermail/xmonad/2007-July/001509.html [3] see http://www.haskell.org/pipermail/xmonad/2007-July/001533.html [4] see http://www.cse.unsw.edu.au/~dons/irc/xmonad/2007-07-26.txt [5] http://www.nongnu.org/ratpoison/ [6] http://www.nongnu.org/stumpwm/ [7] see also http://cvs.savannah.nongnu.org/viewvc/ratpoison/src/communications.c?root=r… [8] see also receive_command() and execute_remote_command() and related comments here: http://cvs.savannah.nongnu.org/viewvc/ratpoison/src/events.c?root=ratpoison… [9] http://search.cpan.org/~rbs/Eesh-0.3/

7 11

Issue 143 in xmonad: XEvent hook or similar needed
by codesite-noreply＠google.com 24 Feb '08

24 Feb '08

Issue 143: XEvent hook or similar needed http://code.google.com/p/xmonad/issues/detail?id=143 Comment #8 by andrea.rossato: I know I promised not to send patches... and indeed I'm not sending this one... I'm just attaching it here...;) Since I like this idea I did some improvements and so I amended the previous patch: 1. now the modifier will activate itself on the first current workspace (and not on the first one); 2. I added haddock documentation; 3. I changed the Test eventHook into EventHookExample that will log to stderr every event, but will specifically handle a button event. To test, just click over the decoration of a decorated layout. Maybe some would like to play with it. This code requires my other patches I listed above. I'm on vacation now...:-) Attachments: eventHookImproved.dpatch 39.6 KB -- 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

Strange Thunar CPU idling phenomenon
by semdornus 24 Feb '08

24 Feb '08

I'm using XFCE's filemanager Thunar and am witnessing something strange when using xmonad. I would like to know if this is a problem with xmonad, or with my system. So if anyone uses Thunar could you please check if this happens? I tried this with my own config, but it happens with no config (=default one) as well. Steps to reproduce: 1. Start xmonad. 2. Start Thunar. 3. Move Thunar to a different workspace. 4. Observe Thunar's idling CPU state in htop or similar. On my PC it is now idling at 3-7%. 5. Switch to workspace where Thunar now is and change Thunar to a different directory. 6. Check CPU idling again. It is now 0% as expected. Strange thing is that just focusing Thunar on the second workspace isn't enough; you have to change the directory. I have no idea what causes this strange behavior. I tried other (tiling) window managers and they all start idling Thunar at 0% as expected. Anybody have an insight?

4 7

Issue 143 in xmonad: XEvent hook or similar needed
by codesite-noreply＠google.com 24 Feb '08

24 Feb '08

Issue 143: XEvent hook or similar needed http://code.google.com/p/xmonad/issues/detail?id=143 Comment #7 by andrea.rossato: ;-) -- 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 143 in xmonad: XEvent hook or similar needed
by codesite-noreply＠google.com 23 Feb '08

23 Feb '08

Issue 143: XEvent hook or similar needed http://code.google.com/p/xmonad/issues/detail?id=143 Comment #6 by nomeata: Nice. I'll be on a week's holyday now, but I'll see what's in the core by then :-) -- 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 143 in xmonad: XEvent hook or similar needed
by codesite-noreply＠google.com 23 Feb '08

23 Feb '08

Issue 143: XEvent hook or similar needed http://code.google.com/p/xmonad/issues/detail?id=143 Comment #5 by andrea.rossato: ok. this is what I have in mind. Attached you'll find a patch that adds XMonad.Hooks.Eventhook. This is a sample usage: main = xmonad ddefaultConfig {layoutHook = eventHook Test (avoidStruts myLayoutHook)} where myLayoutHook us your layout hook. To create an event handler see Test (it should be quite straightforward), but I0m here for any kind of explanation you may want. This patch requires the new runLayout method: http://www.haskell.org/pipermail/xmonad/2008-February/004846.html and probably my other patches to port the contrib library to it: http://www.haskell.org/pipermail/xmonad/2008-February/004859.html and maybe the one that fixes issue #111 too: http://www.haskell.org/pipermail/xmonad/2008-February/004860.html since I'm starting to feel a bit stupid to keep on writing code base on code I'm not even sure will be included in xmonad, this is my last patch. I'll take a break and will not spam anymore. cheers Attachments: eventHook.dpatch 38.9 KB -- 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