- xmonad - Haskell.org

Ambiguous focus after some commands...
by Allen S. Rout 05 Jan '12

05 Jan '12

I've recently encountered an odd focus behavior, and I'm not certain whether I'm thinking about it incorrectly, or if it's a bug. I do a lot of document editing in Emacs' org-mode. (and I highly recommend it: anyone who groks xmonad will probably find Emacs a pleasant environment). In that universe, you compose in a plain-text format, and then direct an 'export' process. On export, Emacs translates your 'org-mode' document into a LaTeX one, then makes PDF out of it, and optionally displays it. If you're doing this with evince as the display engine, you get the result of the document view updating, but no new window. I frequently have my Evince on a screen adjacent to the Emacs, so each has plenty of space. So: with my focus on the Emacs, I [C-c C-e d] (control-c, control-e, d) and watch the export process go. Evince updates with the view of the new document. ... And my focus is now oddly inconsistent. The Emacs window still has the red border by which xmonad attempts to communicate focus, and if I do things like 'onNextNeighbour W.view' it becomes clear that xmonad thinks my focus is there. But my keystrokes are going to evince. If I had started a new client, which appeared on a currently displayed desktop, I would expect that client to grab focus. But I'm not starting a new client, here; I'm sending a message to an existing one. Or at least I think that's what I'm doing, it's possible I guess that Evince is slaying the old process and starting anew, but I'd then expect it to appear on the same workspace as the Emacs. Does this ring any bells? -Allen S Rout

3 2

Why RationalRects for floating windows?
by Norbert Zeh 05 Jan '12

05 Jan '12

Hi folks, I'm wondering whether anybody can enlighten me why the geometry of a floating window is stored as a RationalRect relative to the screen size. I can see one advantage to this approach: a centered window is centered on every screen. Apart from that, I see only disadvantages to this approach, as it means that windows get resized when workspaces shift between screens of different sizes. If at least the aspect ratios of all screens are the same, this may be acceptable, though not ideal. My newest setup combines two portrait screens (1080x1920) with two landscape screens (1920x1080). A window that has a reasonable geometry on one of the landscape screens now gets long and skinny on the portrait screens. I'd also appreciate any ideas on how to work around this issue, as I think changing the way xmonad stores information about floating windows would just break too many modules and thus isn't an option. Thanks, Norbert -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments

3 4

Unity appmenu compatible with XMonad?
by Jacek Generowcz 04 Jan '12

04 Jan '12

Greetings, Has anyone managed to get the Ubuntu's Unity appmenus (a.k.a. global menus: application menus appear on the panel rather than in the application window) to work with XMonad? Starting with a clean installation of Ubuntu 11.10, the appmenus work, in the standard X session. Inspired by http://www.haskell.org/haskellwiki/Xmonad/Using_xmonad_in_Unity_2D, I created the following files in order to create a xmonad-and-unity X session. /usr/share/applications/xmonad.desktop: [Desktop Entry] Type=Application Encoding=UTF-8 Name=Xmonad Exec=xmonad NoDisplay=true X-GNOME-WMName=Xmonad X-GNOME-Autostart-Phase=WindowManager X-GNOME-Provides=windowmanager X-GNOME-Autostart-Notify=true /usr/share/gnome-session/sessions/xmonad.session: [GNOME Session] Name=Xmonad Unity RequiredComponents=gnome-settings-daemon; RequiredProviders=windowmanager;panel; DefaultProvider-windowmanager=xmonad DefaultProvider-panel=unity-2d-panel /usr/share/xsessions/xmonad-unity-session.desktop: [Desktop Entry] Name=XMonad Unity Comment=Tiling window manager TryExec=/usr/bin/gnome-session Exec=gnome-session --session=xmonad Type=XSession I also include , className =? "Unity-2d-panel" --> doIgnore , className =? "Unity-2d-launcher" --> doFloat in my xmonad.hs hooks. XMonad then runs beautifully, except for one serious problem: no application menus appear at all, neither in the application windows, nor on the panel (appmenu). For the time being I have switched off appmenus by UNinstalling the packages appmenu-gtk3 appmenu-qt appmenu-qt thunderbird-globalmenu firefox-globalmenu and the menus now all appear in the application windows. However not wasting space on menubars is in line with the sorts of reasons why I use XMonad, so I would like to try to get appmenus working. Can anyone suggest how to go about trying to get Unity appmenus to work with XMonad? Thanks.

3 2

switching to the workspace where a window just went?
by Lara Michaels 04 Jan '12

04 Jan '12

Every year or so i get too ambitious and try to extract yet more functionality from this awesome piece of software. With the past help of this mailing list in my xmonad.hs i have set up a hotkey to send a window to the next empty workspace: myKeys = [ -- .... , ("M-<F1>", shiftTo Next EmptyWS) ] Now, I would like to have a different key combination (eg, M-<F2>) to - send the current window to the next empty workspace AND THEN - automatically take me to it (meaning, display the workspace to which that window was just sent on the physical display that currently has focus). Is there a way to combine this sequence of actions? Or am I stuck with sending the window to the next empty workspace and then fishing around for it? :) happy 2012 ~l

5 7

Re: Issue 339 in xmonad: Support for toggling totem movie player fullscreen
by codesite-noreply＠google.com 02 Jan '12

02 Jan '12

Updates: Summary: Support for toggling totem movie player fullscreen Status: Accepted Labels: -Priority-Low Priority-Medium Comment #5 on issue 339 by wirtwo...(a)gmail.com: Support for toggling totem movie player fullscreen http://code.google.com/p/xmonad/issues/detail?id=339 Nice work audunskaugen. Thanks for researching this and providing the _NET_WM_STATE_FULLSCREEN event hook (totemFullscreen.hs sample xmonad.hs). IMO, this will be good to get into contrib soon to make it available for more usage, testing and further development. There are some aspects to improve so if anyone wants to take on ownership and submit a patch addressing them that would be great. Otherwise if no action in a week or so I'll send a patch to add it to EwmhDesktops as is, initially as a standalone 'fullscreenEventHook'. Eventually, though, I think it would be good to include an improved version in the standard ewmhDesktopsEventHook, plus having it available by itself. (sjanssen feedback on IRC when asked for thoughts as to where to put this: "enabling the full screen event hook in EWMH would be fine, and would probably make sense.") As is it gives more function for totem users and surely some other similar apps too than the current (0.9) situation, but also with some additional work it seems like it can cover uses of the doFullFloat manageHooks with isFullscreen and the fullscreen query alexey attached to http://code.google.com/p/xmonad/issues/detail?id=333 It seems it covers tiled to fullscreen and back usage plus allowing multihead users to focus other screens without affecting fullscreened apps. In my quick tests it works for totem, flash, mplayer, mplayer-plugin, gnome-mplayer plugin. (This is with all fullscreen manageHooks disabled.) It doesn't seem to help with ooimpress unfortunately, nor evince. Areas to address: * Toggling seems less smooth than it should be. In my tests it appears that the window untiles, goes to hinted float size, then finally fullscreen although it's hard to tell as it's very rapid. There is some glitch anyway that I didn't research yet as to cause. Also other tiled windows from the same workspace look briefly as if they are composited with the fullscreen app since they change size to fill the space as the fullscreen app floats. Not sure how much improvement can practically be made here, but hopefully can something close to the nice mapping with fullscreen manageHook. * Whether a window starts out tiled or floating, once toggled fullscreen and back it restores to tiled state. My reading of wm-spec and probably most users expectations is that floats return to float instead. I don't think PositionStore would be needed for this but didn't look into it yet either. audunskaugen, thanks again. If you'd like please send a darcs patch to X.Hooks.EwmhDesktops, or if you want to be credited by some other name you are welcome to email me privately with your preference and I'll include in any patch I prepare. -- 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 12

Using xmonad 0.10 from cabal in Ubuntu 11.10 Oneiric
by Eyal Erez 02 Jan '12

02 Jan '12

Hi, I've just recently upgrade to Ubuntu 11.10. I've successfully managed to get xmonad to work following the instructions on haskell.org: http://www.haskell.org/haskellwiki/Xmonad/Using_xmonad_in_Gnome#Ubuntu_Onei… However, the xmonad version that comes with Ubuntu is 0.9.2, I would like to use the latest. I've followed the instructions on xmonad.org and installed xmonad via cabal: http://xmonad.org/intro.html So, now I have a ~/.cabal directory which contains a fully built version of xmonad. However, I'm not sure how to put that into the Gnome setup mentioned above. Has anyone been able to get that to work? Thank you, -- *Eyal Erez <**oneself(a)gmail.com* <oneself(a)gmail.com>*>* There are 10 types of people, those who know binary and those who don't.

1 1

Debugging xmonad (also issue 225)
by Ivan S. Freitas 01 Jan '12

01 Jan '12

Hello all, I'm trying to improve the proposed patch for issue 225, by adding a configuration option to toggle its behavior. So far, I applied the old patch, added the variable to control the behavior, and tried to use the setting to decide which behavior to use (see the attached patch, sorry if it's wrongly formatted but I'm not used to darcs yet). The problem: with clickToFocus (the option I've added) turned to False (i.e., the click changes the focus but still goes to the application), everything works as expected. But setting it to True (i.e., keeps the default xmonad's behavior) xmonad just freezes after I click on any window (setting before calling startx or recompiling inside xmonad doesn't solve that, either). So, how do I debug xmonad to find where I made a mistake? Also, note that I'm somewhat new to haskell, so imperative programming still cripples my thought. -- Ivan Sichmann Freitas GNU/Linux user #509059

2 1

Spotify advertisement and Xmonad
by Toni Cebrian 31 Dec '11

31 Dec '11

Hi, Recently I noticed that the Linux version of Spotify no longer requires a Premium account and I installed it again. But when using with Xmonad I can not get rid of the advertising popups that appear when you are inactive in Spotify. Without Xmonad you just click and it goes, but now it stays forever. It is very annoying. Any ideas about how to fix this? Does it happen to you also? Regards.

1 0

Issue 440 in xmonad: Lives preference dialog infinite loop
by codesite-noreply＠google.com 29 Dec '11

29 Dec '11

Status: New Owner: ---- New issue 440 by vox.cogi...(a)gmail.com: Lives preference dialog infinite loop http://code.google.com/p/xmonad/issues/detail?id=440 Steps to reproduce: 1. Install and start the Lives video editor. 2. Open preferences window(C-p). The preference window will then cycle very rapidly between two sizes, using near-100% CPU. Tested using xmonad-0.9.2 on Arch linux. Attachments: xmonad.hs 1.3 KB

1 6

mod-shift-q is Harmful
by Michael Witten 26 Dec '11

26 Dec '11

I just lost a lot of computation when a long-running program of mine was unceremoniously destroyed by xmonad. Now, I take almost full responsibility for this mishap, because I *did* in fact instruct xmonad to obliterate my entire X11 session by issuing the keys `mod-shift-q'. However, that instruction was a mistake; I didn't at all have that action in mind when my fingers went for it---and I'm a longtime user who almost never presses that! A goal of xmonad is to make the user more efficient, but I think this kind of efficiency is not what is intended! I'm no fan of forcibly hand-holding people, but I think it would be wise at least to show people up front how to configure xmonad to confirm this request (especially if it can be determined that information would be destroyed). Even better, a vanilla xmonad should probably come already configured with such a basic safety mechanism (a power user who doesn't want to be pestered with such trivial second-guessing could disable it). Sincerely, Michael Witten

4 4