- xmonad - Haskell.org

Issue 108 in xmonad: When the compleations window is open in vimperator, xmonad does not respond
by codesite-noreply＠google.com 20 Dec '07

20 Dec '07

Issue 108: When the compleations window is open in vimperator, xmonad does not respond http://code.google.com/p/xmonad/issues/detail?id=108 New issue report by tim.thelion: What steps will reproduce the problem? 1. Go to google(classic home) 2. Press 'h' 3. Press down arrow(you should have a list of all things you have searched for that started with 'h'). 4. Press mod-2 What is the expected output? What do you see instead? That I be switched to workspace2. Instead, nothing happens. What version of the product are you using? On what operating system? Darcs, and Debian Sid Please provide any additional information below. If this error is due to a module from XMonadContrib, please tag this issue with 'Component-Contrib' below. 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

Debian packages for 0.5 − please Test
by Joachim Breitner 19 Dec '07

19 Dec '07

Hi, thanks to some bugging and help from dons and sjanssen, I finally got some 0.5 packages for debian. You can find them, together with the X11 1.4.1 dependency, here: http://people.debian.org/~nomeata/xmonad/ No xmonad contrib yet, sorry, I’ll look at that next. The packages are beta-quality and not tested very much, I hope that you can help me there :-) I decided to split the package up, here is the quote from README.Debian: > The packages for debian are split in four: > > * xmonad > This package contains only the xmonad binary (with it’s man page) in the > default configuration. You do not have to install the haskell compiler to > use this package, but you also cannot reconfigure it to your needs. To do > that, you need the libghc6-xmonad-dev package. If that is installed, xmonad > will detect your configuration when you start it and compile a custom > executable in ~/.xmonad transparently. > > * libghc6-xmonad-dev > This package contains the actual xmonad library, which you need to compile > your custom configuration. > > * libghc6-xmonad-doc > This package contains the documentation for xmonad, including an example > configuration file. > > * libghc6-xmonad-prof > Profiling information. You’ll know when you need it. If you want to help out, I manage the xmonad package in a darcs repository that contains the regular patches from upstream with the addition of the debian files and my own adjustments to the xmonad sources: http://darcs.nomeata.de/xmonad/ http://darcs.nomeata.de/cgi-bin/darcsweb.cgi?r=xmonad;a=summary Comments and patches are very appreciated. Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata(a)debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nomeata(a)joachim-breitner.de | http://people.debian.org/~nomeata

2 1

xmonad-contrib, Haddock, and You!
by Brent Yorgey 19 Dec '07

19 Dec '07

Hi all! In order to help encourage good documentation, I just pushed a patch to xmonad-contrib to include haddock generation in the automatic darcs test. In other words, the haddock documentation must build without errors in order to record a patch. To ease the pain a bit, here's a quick summary of Things You Should Know about haddock documentation for contributed extension modules: * all exported functions in contributed modules should have a haddock-style comment saying what they do. Haddock-style comments look like this: -- | This is a haddock-style comment Note the vertical pipe character (and the spaces around it!). * You can quote literal code blocks by using "birdtracks", like this: > foo x = x + h > where h = 3 Be sure to leave blank lines both before and after any such code blocks! It won't parse correctly without the blank lines. * Inline literal code fragments can be surrounded by @at symbols@. * To include a hyperlink to another function in the module, surround the function name in 'single quotes'. To link to another module, surround the module name in "double quotes". * To include literal single or double quotes, frontslashes, backslashes, at symbols, etc., escape them with backslashes, \"like this\". Not escaping things like this is another common reason your documentation might fail to compile. For more detail, you should have a look at the Haddock user guide<http://www.haskell.org/haddock/haddock-html-0.8/index.html>. And of course, the best advice overall is to just look at the style of other extensions, and emulate it. Happy hacking! -Brent

1 0

Issue 107 in xmonad: Floating windows cause combo-boxes and other widgets in applications to faill.
by codesite-noreply＠google.com 19 Dec '07

19 Dec '07

Issue 107: Floating windows cause combo-boxes and other widgets in applications to faill. http://code.google.com/p/xmonad/issues/detail?id=107 New issue report by thomas.adam22: What steps will reproduce the problem? 1. Have some windows in the floating layer on the same workspace/screen as, say, Firefox. 2. Try and use a drop-down menu in said browser either with or without the floating windows present. What is the expected output? What do you see instead? Sometimes (often randomly) the drop-down menu will be unusable. I would expect it to Just Work, but it's as if it is sent to the wrong layer. What version of the product are you using? On what operating system? xmonad-darcs (but observed in xmonad 0.5 and 0.4.1). Please provide any additional information below. I suspect this to be related to the floating window support absolute. More likely, it's related to the fact that the floating layer has absolutely no concept of stacking/layer support (as mentioned in the ICCCM), such that when a *widget* of an application is mapped, it is somehow susceptible to this. But this is bad, widgets in this sense have no part in window management. 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

Issue 105 in xmonad: Tabs become managed windows upon xmonad restart on multi-screen setups
by codesite-noreply＠google.com 19 Dec '07

19 Dec '07

Issue 105: Tabs become managed windows upon xmonad restart on multi-screen setups http://code.google.com/p/xmonad/issues/detail?id=105 Comment #6 by andrea.rossato: in the previous comment I was wrong: broadcastMessage works properly and the tab windows get properly destroyed. The problem is located in the bootstrap of the windowset when resuming: the tabs related to windows located in the visible (but not current) workspaces get created in the current workspace. I hope to come up with a fix shortly. (sorry for the noise but I just wanted everyone to know that the previous comment was misleading). andrea -- 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 105 in xmonad: Tabs become managed windows upon xmonad restart on multi-screen setups
by codesite-noreply＠google.com 19 Dec '07

19 Dec '07

Issue 105: Tabs become managed windows upon xmonad restart on multi-screen setups http://code.google.com/p/xmonad/issues/detail?id=105 Comment #5 by andrea.rossato: ok, just reproduced (thanks to the droundy's LayoutScreens!!). I'm trying to fix it (I'll do it as soon as I understand why broadcastMessage doesn't reach visible layouts...;) andrea -- 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

Re: XMonad.Layout.NoBorders
by David Roundy 19 Dec '07

19 Dec '07

No, I don't have time. And I'm not sure why one would want no borders on floating windows... David On Dec 18, 2007 12:54 AM, Roberth Sjonøy <roberth.sjonoy(a)gmail.com> wrote: > Hello > > Your Xmonad extension Layout.NoBorders doesn't work with floating > windows, could you fix this please?

1 0

Issue 106 in xmonad: LayoutCombinators disallows custom key-bindings to work?
by codesite-noreply＠google.com 19 Dec '07

19 Dec '07

Issue 106: LayoutCombinators disallows custom key-bindings to work? http://code.google.com/p/xmonad/issues/detail?id=106 Comment #1 by daveroundy: This is specifig to the "Go" function in WindowNavigation, which won't work with Combo. That's just the way it is. Noone but me seems to want nested stacks, so we have to use horribly ugly hacks, which have nasty effects, sorry. -- 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

darcs patch: Fix typo.
by Roman Cheplyaka 19 Dec '07

19 Dec '07

Wed Dec 19 09:38:57 EET 2007 Roman Cheplyaka <roma(a)ro-che.info> * Fix typo.

2 1

Darcs patch: Multiple architectures per home dir
by Timothy 19 Dec '07

19 Dec '07

I have no way of testing this, as I don't share my home directory across architectures, but I implemented it as was described to me by dons so it should work.

2 1