October 2007 - xmonad

possible bug in tabbed window extension
by Michael Vanier 10 Oct '07

10 Oct '07

I've just upgraded to the latest xmonad in darcs, and it's great! However, one thing that used to work doesn't work anymore. I bind mod-button3 to the kill command, and when I put the cursor on a tab and hit mod-button3 the entire X server crashes! When I do it outside of a tab it works fine. FWIW the relevant part of my Config.hs is: -- | -- default actions bound to mouse events -- mouseBindings :: M.Map (KeyMask, Button) (Window -> X ()) mouseBindings = M.fromList $ -- mod-button1 %! Set the window to floating mode and move by dragging [ ((modMask, button1), (\w -> focus w >> mouseMoveWindow w)) -- mod-button2 %! Set the window to floating mode and resize by dragging , ((modMask, button2), (\w -> focus w >> mouseResizeWindow w)) -- mod-button3 %! Kill a window , ((modMask, button3), (\_ -> kill)) -- Extension-provided mouse bindings ] Anybody have any idea what's going wrong? TIA, Mike

7 10

More user-friendly hook system
by Joachim Breitner 10 Oct '07

10 Oct '07

Hi, I’ve been given some thought on the way we make the user install the hooks from extensions. Currently, we have two hooks (manageHook and logHook), with a different logic for combining hooks: For manageHook, we pass the window some hopefully useful data as paramenters (name, class) and exepect to get a X (WindowSet -> WindowSet) back. The user can use guards to select which hook to run. Advantage: - relatively easy for the user to add simple custom hooks Disadvantage: - hard to add hooks that need to do X stuff to find out if they have to run (e.g. by getting other Properties of the window). - hard to install hooks so that more than one can run for a window. For loogHook, we just require the user to return an X () action. Advantage: - flexible Disadvantage: - different method than manageHook - user needs to know Monad syntax Additionally, it is hard to add more hook (init hook, hooks on ClientMessage events that would be needed for EWMH interaction), and the user is confused by different hook mechanism. I propose therefore this system: User interface ============== For the user, it should be very simple to add extensions that need hooks. Therefore, there should just be a simple XMonadHook type (where the implementation should not matter to the user), and a single function in the config: > hooks :: [XMonadHook] > hooks = [ewmhHook > , loatGimpHook > , someHookWithAString "text" > , someHookWithConfig someConfig > ] > > someConfig = -- more complicated per-hook information Functionality such as matching a window name on manage (as provided by the current system) should be make possible through an extension on it’s own: See the PropManage extension, which already works like this. Possible implementation ======================= Note that given this user interface, there might other ways to implement this. This is just my idea. Assume we want to support four hooks: initHook, manageHook, clientMessageHook and logHook. We also don’t want to change code in Extensions when new hooks are added. I’d give types to the single hooks: > type InitHook :: X () > type MangageHook :: Window -> X (WindowSet -> WindowSet) > type ClientMessageHook :: ClientMessage -> X () > type logHook :: X() for every hook, we have a “no nothing” default hook: > defaultInitHook :: InitHook > defaultInitHook = return () > defaultManageHook :: ManageHook > defaultManageHook _ = return (id) > defaultClientMessageHook :: ClientMessageHook > defaultClientMessageHook _ = return () > defaultLogHook :: LogHook > defaultLogHook = return () The XMonadHook is then a record of possible hooks, and we bunde the default hooks: > type XMonadHook = XMonadHook { > initHook :: InitHook > ,manageHook :: MangeHook > ,clientMessageHock :: ClientMessageHook > ,logHook :: LogHook > } > defaultXMonadHook :: XMonadHook > defaultXMonadHook = XMonadHook defaultInitHook defaultManageHook defaultClientMessageHook defaultLogHook To run the hooks given by the user, we map the appropriate accessor over config list and fold the types together, depending on the type > runInitHooks :: [XMonadHook] -> X () > runInitHooks = foldl (>>) (return ()) . map initHook > runManageHooks :: [XMonadHook] -> Window -> X (WindowSet -> WindowSet) > runManageHooks hooks window = foldl (.) (id) `fmap` mapM (($window) . manageHook) hooks > runClientMessageHooks :: [XMonadHook] -> ClientMessage -> X () > runClientMessageHooks hooks cm = foldl (>>) (return ()) . map (($ cm) . initHook) > runLogHooks :: [XMonadHook] -> X () > runLogHooks = foldl (>>) (return ()) . map logHook Extensions then can write their own hook(s) and override the appropriate fields of defaultXMonadHook: > module StupidLogger where > > myLogHook :: LogHook > myLogHook = io $ print "State changed" > > stupidLoggerHook :: XMonadHook > stupidLoggerHook = defaultXMonadHook { logHook = myLogHook } As you can see, adding new hooks would not break this module. Hooks that need some configuration (e.g. PropManage the list things to match), you just require a parameter for your hook > module NameMatcher where > > type NameMatcherConf = [String, X()] > > myManageHook :: NameMatcherConf -> ManageHook > myManageHook = ... > > nameMatcherHook :: NameMatcherConf -> XMonadHook > nameMatcherHook conf = defaultXMonadHook { manageHook = myManageHook conf } That’s it so far. Note that this code is untested. If you think this would be a viable user interface or even a reasonable implementation, I’d be willing to implement that today. Greetings, Joachim -- Joachim Breitner e-Mail: mail(a)joachim-breitner.de Homepage: http://www.joachim-breitner.de ICQ#: 74513189

3 8

Current darcs version doesn't compile
by David Benbennick 10 Oct '07

10 Oct '07

The current version of xmonad in darcs doesn't compile for me: $ darcs get http://code.haskell.org/xmonad Copying patch 694 of 694... done! Applying patch 694 of 694... done. Finished getting. $ cd xmonad/ $ chmod u+x Setup.lhs $ ./Setup.lhs configure Configuring xmonad-0.3... configure: Dependency base>=2.0: using base-2.1.1 configure: Dependency X11>=1.2.1: using X11-1.2.1 configure: Dependency X11-extras>=0.3: using X11-extras-0.3 configure: Dependency mtl>=1.0: using mtl-1.0.1 configure: Dependency unix>=1.0: using unix-2.1 configure: Using install prefix: /usr/local configure: Binaries installed in: /usr/local/bin configure: Libraries installed in: /usr/local/lib/xmonad-0.3/ghc-6.6.1 configure: Private binaries installed in: /usr/local/libexec configure: Data files installed in: /usr/local/share/xmonad-0.3 configure: Using compiler: /home/dbenbenn/apps/bin/ghc configure: Compiler flavor: GHC configure: Compiler version: 6.6.1 configure: Using package tool: /home/dbenbenn/apps/bin/ghc-pkg configure: Using ar found on system at: /usr/bin/ar configure: No haddock found configure: No pfesetup found configure: Using ranlib found on system at: /usr/bin/ranlib configure: Using runghc found on system at: /home/dbenbenn/apps/bin/runghc configure: No runhugs found configure: No happy found configure: No alex found configure: Using hsc2hs: /home/dbenbenn/apps/bin/hsc2hs configure: No c2hs found configure: No cpphs found configure: No greencard found $ ./Setup.lhs build Preprocessing executables for xmonad-0.3... Building xmonad-0.3... [1 of 6] Compiling StackSet ( StackSet.hs, dist/build/xmonad/xmonad-tmp/StackSet.o ) StackSet.hs:234:0: Warning: Pattern match(es) are non-exhaustive In the definition of `view': Patterns not matched: _ _ [2 of 6] Compiling XMonad ( XMonad.hs, dist/build/xmonad/xmonad-tmp/XMonad.o ) [3 of 6] Compiling Config[boot] ( Config.hs-boot, nothing ) [4 of 6] Compiling Operations ( Operations.hs, dist/build/xmonad/xmonad-tmp/Operations.o ) [5 of 6] Compiling Config ( Config.hs, dist/build/xmonad/xmonad-tmp/Config.o ) [6 of 6] Compiling Main ( Main.hs, dist/build/xmonad/xmonad-tmp/Main.o ) Main.hs:258:7: Not in scope: data constructor `PropertyEvent' Main.hs:258:42: Not in scope: `ev_atom' Maybe a dependency is missing from the configure step? Any ideas? I was able to compile from darcs two weeks ago.

4 5

darcs patch: XSelection.hs: a new module for XMonadCo... (and 1 more)
by gwern0＠gmail.com 10 Oct '07

10 Oct '07

Mon Oct 8 18:27:06 EDT 2007 gwern0(a)gmail.com * XSelection.hs: a new module for XMonadContrib dealing with copy-and-paste This is based on Andrea Rossato's standalone tools and is meant for integration straight into a Config.hs. It offers two main functions, 'getSelection' and 'putSelection', whose names should be self-explanatory. Tue Oct 9 22:06:16 EDT 2007 gwern0(a)gmail.com * XSelection.hs: Implement Andrea's idea for handling non-UTF-8 string cases

2 1

darcs patch: doco fix: s/SomeLayout/Layout/g
by Devin Mullins 10 Oct '07

10 Oct '07

Mon Oct 8 18:59:16 EDT 2007 Devin Mullins <me(a)twifkak.com> * doco fix: s/SomeLayout/Layout/g

2 1

darcs patch: subLayouts for Combo (and 2 more)
by Spencer Janssen 10 Oct '07

10 Oct '07

This is a companion to the possibleLayouts removal patches. David, I'd like to know if serialization still works for Combo with these changes. Cheers, Spencer Janssen Thu Oct 4 15:09:48 CDT 2007 Spencer Janssen <sjanssen(a)cse.unl.edu> * subLayouts for Combo Thu Oct 4 15:11:35 CDT 2007 Spencer Janssen <sjanssen(a)cse.unl.edu> * subLayouts for LayoutModifier Thu Oct 4 15:26:10 CDT 2007 Spencer Janssen <sjanssen(a)cse.unl.edu> * Include subLayouts of ModifiedLayouts too

2 1

darcs patch: The road to killing possibleLayouts: add... (and 2 more)
by Spencer Janssen 10 Oct '07

10 Oct '07

This is an exploratory change to remove possibleLayouts. I'd like to get some opinions on this patch before I push it. Cheers, Spencer Janssen Thu Oct 4 15:05:59 CDT 2007 Spencer Janssen <sjanssen(a)cse.unl.edu> * The road to killing possibleLayouts: add subLayouts Thu Oct 4 15:14:01 CDT 2007 Spencer Janssen <sjanssen(a)cse.unl.edu> * Remove possibleLayouts Thu Oct 4 15:31:45 CDT 2007 Spencer Janssen <sjanssen(a)cse.unl.edu> * subLayouts for Layout

2 1

darcs patch: MetaModule: added WindowPrompt (and 2 more)
by Andrea Rossato 10 Oct '07

10 Oct '07

After pulling and rewriting... I must confess I don't like windowMapWith too much... I find it a bit misleading, but probably it's just me. The code doesn't seem that bad to me, after all. andrea Tue Oct 9 18:34:45 CEST 2007 Andrea Rossato <andrea.rossato(a)unibz.it> * MetaModule: added WindowPrompt Tue Oct 9 18:35:05 CEST 2007 Andrea Rossato <andrea.rossato(a)unibz.it> * WindowBringer: export windowMapWith used by WindowPrompt Tue Oct 9 18:40:47 CEST 2007 Andrea Rossato <andrea.rossato(a)unibz.it> * Add WindowPrompt: the XPrompt equivalent of WindowBringer

2 2

Issue 57 in xmonad: Amarok OSD goes missing
by codesite-noreply＠google.com 09 Oct '07

09 Oct '07

Issue 57: Amarok OSD goes missing http://code.google.com/p/xmonad/issues/detail?id=57 New issue report by lit...(a)hethrael.com: What steps will reproduce the problem? 1. Run Amarok with the OSD enabled. 2. Create a new window (e.g. run xterm) on the screen on which the OSD appears. 3. Press Win+O or wait for a song change to display the OSD. What is the expected output? What do you see instead? The OSD should appear in front of all windows. Instead, the OSD is hidden behind all windows on the screen. If you move the window that is obscuring the OSD (with mod+mouse button 1), you can see the OSD behind it. What version of the product are you using? On what operating system? Xmonad from darcs, Amarok 1.4.7, Ubuntu Feisty. Please provide any additional information below. The OSD displays properly when Amarok is (re)started, until a new window is created on the screen that displays the OSD. Creating new windows on the non-OSD screen does not affect the OSD. 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

xmonad works ;)
by Alexander Solovyov 09 Oct '07

09 Oct '07

Hi, my apologies for previous message - I've solved this trouble. Spent on this over 2 hours and no success until writing of mail and speaking in irc. As always. :( Sorry, please. -- Alexander

1 0