- xmonad - Haskell.org

Call for xmonad.hs
by Gwern Branwen 17 Jan '10

17 Jan '10

Hi everyone. So a while ago we were discussing how to improve defaults and what sorts of types and functions XM and XMC could provide which encapsulate common behavior, when Devon asked me what exactly I saw being repeated (besides the 2 or 3 examples I provided), and it occurred to me that I really didn't know. There're ~30 xmonad.hs's here <http://haskell.org/haskellwiki/Xmonad/Config_archive>, but perhaps 1/3 to 1/2 are obsolete or don't compile with darcs XM/XMC (at a very rough guess). I'd like more. So here's what I would greatly appreciate everyone doing: 1) Upload your config 2) If you've uploaded your config, update it! 3) If you use someone else's config, why not mention it? I'd appreciate knowing who's using what, so I can count the popular configurations proportionately* 4) If you don't want to do any of 1-3, perhaps you could email me privately with your config? Thanks in advance all. * I think it's fair to say that if 10 people are using a particular xmonad.hs, and there's a simplification which could be made, that change should count 10x -- gwern ANZUS nuclear Lebed .ch Domination .tm top Amherst USSS Hugo

10 27

darcs patch: X.L.Decoration: avoid flicker by not showing decowins ...
by Tomas Janousek 16 Jan '10

16 Jan '10

Sat Jan 16 12:20:54 CET 2010 Tomas Janousek <tomi(a)nomi.cz> * X.L.Decoration: avoid flicker by not showing decowins without rectangles These would be hidden by updateDecos immediately after being shown. This caused flicker with simpleTabbed and only one window on a workspace. -- Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/

3 2

DynamicWorkspaces: New WS not accessible with mod+number
by Ralph Hofmann 16 Jan '10

16 Jan '10

I prefer using only few workspaces by default and adding one if needed, whether by adding a workspace with addWorkspace and rename it or, more easily, by using selectWorkspace and entering a number that doesn't exist. In both cases, i can't access the new workspace by "mod + number of workspace". Is there a workaround? My xmonad has version 0.9-1. Ralph

2 6

Re: [xmonad] DynamicWorkspaces: New WS not accessible with mod+number
by Ralph Hofmann 14 Jan '10

14 Jan '10

I forgot to mention, in my example, that I am not on the virtualbox workspace 4, when I press mod+5, but on one of the workspaces 1 - 3. So virtualbox is not on the screen and doesn't catch the keys. Ralph Am Donnerstag, den 14.01.2010, 15:20 -0500 schrieb wagnerdm(a)seas.upenn.edu: > Have you tried pressing the "return to host" key first? By default, I > think this is right control. > ~d > > Quoting Ralph Hofmann <hofmann2004(a)arcor.de>: > > > I just found out, that this behaviour only occurs with a running > > virtualbox machine. If virtualbox is, let's say, running on workspace 4 > > and I create a new workspace 5, it can't be accessed with mod+5. > > > > Without virtualbox, everything works fine. So no big issue. > > > > Ralph > > > > Am Donnerstag, den 14.01.2010, 20:07 +0100 schrieb Ralph Hofmann: > >> I prefer using only few workspaces by default and adding one if needed, > >> whether by adding a workspace with addWorkspace and rename it or, more > >> easily, by using selectWorkspace and entering a number that doesn't > >> exist. In both cases, i can't access the new workspace by "mod + number > >> of workspace". > >> > >> Is there a workaround? > >> > >> My xmonad has version 0.9-1. > >> > >> Ralph > >> > >> _______________________________________________ > >> xmonad mailing list > >> xmonad(a)haskell.org > >> http://www.haskell.org/mailman/listinfo/xmonad > > > > > > _______________________________________________ > > xmonad mailing list > > xmonad(a)haskell.org > > http://www.haskell.org/mailman/listinfo/xmonad > > > > > >

1 0

X.U.WorkspaceCompare getSortByXineramaRule
by Anders Engström 13 Jan '10

13 Jan '10

So, I was hacking on X.U.WorkspaceCompare, or more precisely getSortByXineramaRule, since I got irritated that my screen identifiers did not match my physical layout. Therefore I added a new sorter (getSortByXineramaPhysicalRule) that shares most of the code with the old one, but treats screens the same way as X.A.PhysicalScreens. It now got me thinking, is this really such a good idea? Maybe The old rule should be changed instead? What is preferable? It would change the behaviour for already existing configs, but for those users the behaviour is most likely a "bug". So this would be more like a bug fix. The downside is that the positioning will not match the default keybindings. Those encountering this is more likely to use X.A.PhysicalScreens or X.A.CycleWS though (like me). So is it a good idea to change the already existing sort rule?

1 0

Set avoidStruts for an individual workspace
by Ones Self 12 Jan '10

12 Jan '10

Hi, I'm using avoidStruts to leave the Gnome status bar uncovered, but I have one workspace, used for watching movies, that I would like the window to cover the bar. I'm currently using a key combo to toggleStruts, but I would like that workspace to just have that set always. Is this possible? Thanks

3 2

Multi-head beamer presentations
by Ivan Lazar Miljenovic 11 Jan '10

11 Jan '10

I'm doing a presentation using Beamer [1] for LaTeX. It allows using the second screen for notes by basically creating two-screen wide "pages" with the idea of having the entire full screen presentation spread across both screens (and the projector only showing one screen). Now, this works well for how "traditional" window managers treat multi-head as one big workspace, but obviously doesn't work too well for xmonad. Is there any nice way I can do up a key combo or something (maybe even a ManageHook?) to have it automatically go floating and spread out across both screens (i.e. across the entire visible area)? [1] http://latex-beamer.sourceforge.net/ -- Ivan Lazar Miljenovic Ivan.Miljenovic(a)gmail.com IvanMiljenovic.wordpress.com

2 1

Issue 357 in xmonad: Ctrl+C in shellPrompt makes xmonad hang
by codesite-noreply＠google.com 11 Jan '10

11 Jan '10

Status: New Owner: ---- New issue 357 by akhilman: Ctrl+C in shellPrompt makes xmonad hang http://code.google.com/p/xmonad/issues/detail?id=357 What steps will reproduce the problem? 1. activate shellPrompt (modMask + P) 2. press Ctrl+C in shell prompt 3. do anything if you can do. xmonad hangs. What is the expected output? What do you see instead? I expect exiting from shell prompt. But have to restart X. What version of the product are you using? On what operating system? xmonad 0.9 gentoo linux and arch linux -- 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 1

[newbie] {visual preview of workspaces, ignoring current workspace} when using Actions.CycleWS
by Lara Michaels 11 Jan '10

11 Jan '10

Hello, I am brand new to xmonad and it has blown my mind away. FINALLY being able to discretionarily assign a workspace to a physical screen is amazing. : ) Two brief questions: 1 - Is it possible to get some sort of visual preview of what is in the next or previous workspace when moving with next|prevWS? (A little bit like regular window managers bring up for you to pick among windows when you press Alt-Tab?) Currently, I cycle blindly among all nine workspaces until I stumble upon the one I had in mind. 2- In the attached xmonad.hs, I have tried to combine cycling with Actions.CycleWS with the non-greedy view. My goal is that, when the focus is on a particular (physical) screen, doing (next|prev)WS will *skip* over the workspace currently visible in the *other* (physical) screen. In other words, I would like the focus never to leave the physical screen I am using, and that while cycling the workspace currently in the other screen would be ignored. Is there even a way to do this...? In any case, many thanks to the developers for this awesome tool! cheers lara

2 1

how to map XF86* keys?
by Chengqi Song 11 Jan '10

11 Jan '10

Hi All, I want to map my vol up and vol down keys. I used xev to capture their info as follows: KeyRelease event, serial 27, synthetic NO, window 0x1600001, root 0x115, subw 0x0, time 1035672, (320,301), root:(321,319), state 0x0, keycode 122 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 27, synthetic NO, window 0x1600001, root 0x115, subw 0x0, time 1036158, (320,301), root:(321,319), state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False but I dont know how to use them in my xmonad.hs like other keys: myKeys = \c -> mkKeymap c $ -- volume key binding [ ("M-=", spawn "aumix2pipe +10") , ("M--", spawn "aumix2pipe -10") Could anyone provide a solution? thanks lars

5 7