- xmonad - Haskell.org

Re: Issue 344 in xmonad: xmonad does not manage docks and other windows that have been 'doIgnored'
by codesite-noreply＠google.com 25 Nov '09

25 Nov '09

Updates: Summary: xmonad does not manage docks and other windows that have been 'doIgnored' Status: Accepted Labels: Priority-Low Type-Defect Comment #1 on issue 344 by SpencerJanssen: xmonad does not manage docks and other windows that have been 'doIgnored' http://code.google.com/p/xmonad/issues/detail?id=344 This has been an issue waiting to happen for quite some time now. Docks are currently "managed" by doIgnore, which means that xmonad is completely unaware of the windows. This has several symptoms: * xmonad doesn't maintain a proper stacking order of these windows, meaning that we can't guarantee where dock, desktop and regular client windows stack in relation to each other * it is difficult to give keyboard focus to docks and the like * the issue in the original report, not all clients are listed in the stacking window prop I've been considering adding a component to xmonad that acts as an intermediary between xmonad's high level domain (StackSet and layout algorithms) and X. This component would be able to manage these windows that don't go in StackSet. -- 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 344 in xmonad: _NET_CLIENT_LIST_STACKING property lacks docked windows
by codesite-noreply＠google.com 24 Nov '09

24 Nov '09

Status: New Owner: ---- New issue 344 by dotted...(a)dottedmag.net: _NET_CLIENT_LIST_STACKING property lacks docked windows http://code.google.com/p/xmonad/issues/detail?id=344 What steps will reproduce the problem? 1. Run gnome-panel 2. xprop -root | grep '_NET_CLIENT_LIST_STACKING(WINDOW)' 2. Note that gnome-panel window does not appear in output What is the expected output? What do you see instead? All visible windows, including panels should appear at output. This breaks e.g. notification bubbles in Ubuntu as notification daemon can't locate gnome-panel. What version of the product are you using? On what operating system? xmonad 0.9, Linux (Ubuntu 9.10) Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". xmonad --recompile does not output anything. Please provide any additional information below. Attachments: xmonad.hs 1.2 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

FBpanel Lohook
by Jan Snyder 24 Nov '09

24 Nov '09

Hi, I am interested to use loghook in FBpanel or any other panel like perl-panel. I have fbpanel now. I like the plain script lohook that shows workspace-names and tile-names. I know this can be ported to gnome-panel through a loghook applet, but would prefer to use fbpanel. NOt sure how to make a loghook applet for fbpanel. Is there a simple script to link the loghook to EWMH in fbpanel? thanks, Jan Snyder On Fri, Nov 20, 2009 at 7:25 PM, <xmonad-request(a)haskell.org> wrote: > Send xmonad mailing list submissions to > xmonad(a)haskell.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://www.haskell.org/mailman/listinfo/xmonad > or, via email, send a message with subject or body 'help' to > xmonad-request(a)haskell.org > > You can reach the person managing the list at > xmonad-owner(a)haskell.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of xmonad digest..." > > > Today's Topics: > > 1. darcs patch: X.H.DynamicLog: fix xmonadPropLog > double-encoding of U... (Tomas Janousek) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 21 Nov 2009 01:50:11 +0100 > From: Tomas Janousek <tomi(a)nomi.cz> > Subject: [xmonad] darcs patch: X.H.DynamicLog: fix xmonadPropLog > double-encoding of U... > To: xmonad(a)haskell.org > Message-ID: <20091121005011.GA10957(a)notes.lisk.in> > Content-Type: text/plain; charset="utf-8" > > Sat Nov 21 01:48:29 CET 2009 Tomas Janousek <tomi(a)nomi.cz> > * X.H.DynamicLog: fix xmonadPropLog double-encoding of UTF-8 > > dynamicLogString utf-8 encodes its output, xmonadPropLog shouldn't do that > again. > > -- > Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/ >

1 0

Issue 343 in xmonad: XMonad.Prompt.RunOrRaise doesnt always detect an already running program
by codesite-noreply＠google.com 23 Nov '09

23 Nov '09

Status: New Owner: ---- New issue 343 by h2oz7v: XMonad.Prompt.RunOrRaise doesnt always detect an already running program http://code.google.com/p/xmonad/issues/detail?id=343 What steps will reproduce the problem? 1. Launch a Firefox instance using RunOrRaise 2. Switch workspaces 3. Launch Firefox again in RunOrRaise What is the expected output? What do you see instead? I expect the already running instance of Firefox to be moved ("raised") to the different workspace. Instead, a new Firefox window is opened. What version of the product are you using? On what operating system? Linux, xmonad v0.9 -- 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 5

Re: Issue 317 in xmonad: Implement a working X.U.putSelection
by codesite-noreply＠google.com 21 Nov '09

21 Nov '09

Updates: Summary: Implement a working X.U.putSelection Comment #13 on issue 317 by daniel.schoepe: Implement a working X.U.putSelection http://code.google.com/p/xmonad/issues/detail?id=317 putSelection has been removed for now until we have a clean way to do this. For now, someone who wants to use this feature can define a function that uses xclip/xsel to set the selection and use that function in his prompt keymap. -- 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 7

darcs patch: X.H.DynamicLog: fix xmonadPropLog double-encoding of U...
by Tomas Janousek 21 Nov '09

21 Nov '09

Sat Nov 21 01:48:29 CET 2009 Tomas Janousek <tomi(a)nomi.cz> * X.H.DynamicLog: fix xmonadPropLog double-encoding of UTF-8 dynamicLogString utf-8 encodes its output, xmonadPropLog shouldn't do that again. -- Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/

2 1

Re: XMonad.Hooks.FadeInactive with floating windows
by Justin Bogner 20 Nov '09

20 Nov '09

This seems generally useful, so I'm sending your idea and patch to the xmonad mailing list. It's best to send ideas about xmonad/xmonad-contrib improvements there, so they get a wider audience. On Thu, Nov 19, 2009 at 1:16 AM, Jasper van der Jeugt <jaspervdj(a)gmail.com> wrote: > Hello, > > I recently installed the XMonad.Hooks.FadeInactive into my xmonad.hs. I > think it is very usable, altough there is one drawback: floating windows. > > I (and most people, I think) use floating windows mostly for many-window > applications like, for example, the GIMP. In the GIMP, you wouldn't want a > window to become transparent, since you want a clear view of your image, > even when you're clicking around in the toolbox window. > > I therefore propose to add a Query that returns true if the window is > unfocused, and in the tiling layer. I attached the code as a diff. I'd like > to know what you think. > > Kind regards, > Jasper Van der Jeugt

2 1

Re: [xmonad] xmonad 0.9 on ubuntu 9.10
by Tony Morris 20 Nov '09

20 Nov '09

I tried that and it seems xmonad was running i.e. windows weren't decorated, but they didn't fill tile across the screen and had their usual gnome size. Scuz wrote: > I used the windowmanager gconf setting and its works fine for me. > Can't remember what it is offhand but its in the guide for using with > gnome. > > -Ryan Souza > > > > On Wed, Nov 18, 2009 at 4:32 PM, Tony Morris <tonymorris(a)gmail.com> wrote: > >> Sorry that's what I meant. >> >> Spencer Janssen wrote: >> >>> On Thu, Nov 19, 2009 at 10:08:19AM +1000, Tony Morris wrote: >>> >>> >>>> Hello, I am trying to get xmonad running on ubuntu 9.10 per >>>> http://www.haskell.org/haskellwiki/Xmonad/Using_xmonad_in_Gnome#Ubuntu_Karm… >>>> >>>> I have set the WINDOW_MANAGER in ~/.gnomerc but when gnome starts I get >>>> a background screen, no gnome panel/menu and no ability to use xmonad >>>> keys (e.g. CTRL-mod-enter does not start a terminal). >>>> >>>> I have tried other methods mentioned on the link above and encountered >>>> no to poor success. >>>> >>>> Any hints? >>>> >>>> >>> CTRL-mod-enter isn't an xmonad keybinding, mod-shift-enter is the key binding >>> for a terminal. Other than that, I'm not sure what the problem might be. >>> >>> >>> Cheers, >>> Spencer Janssen >>> _______________________________________________ >>> xmonad mailing list >>> xmonad(a)haskell.org >>> http://www.haskell.org/mailman/listinfo/xmonad >>> >>> >>> >> -- >> Tony Morris >> http://tmorris.net/ >> >> >> _______________________________________________ >> xmonad mailing list >> xmonad(a)haskell.org >> http://www.haskell.org/mailman/listinfo/xmonad >> >> > > -- Tony Morris http://tmorris.net/

3 6

darcs patch: X.H.ManageDocks: ignore struts that cover an entire sc...
by Tomas Janousek 19 Nov '09

19 Nov '09

Thu Nov 19 15:50:43 CET 2009 Tomas Janousek <tomi(a)nomi.cz> * X.H.ManageDocks: ignore struts that cover an entire screen on that screen Imagine a screen layout like this: 11111111 11111111 11111111 222222 <--- xmobar here 222222 222222 When placing xmobar as indicated, the partial strut property indicates that an entire height of screen 1 is covered by the strut, as well as a few lines at the top of screen 2. The original code would create a screen rectangle of negative height and wreak havoc. This patch causes such strut to be ignored on the screen it covers entirely, resulting in the desired behaviour of a small strut at the top of screen 2. Please note that this semantics of _NET_WM_STRUT and _NET_WM_STRUT_PARTIAL is different to what is in wm-spec. The "correct" thing to do would be to discard the covered portion of screen 1 leaving two narrow areas at the sides, but this new behaviour is probably more desirable in many cases, at least for xmonad/xmobar users. The correct solution of having separate _NET_WM_STRUT_PARTIAL for each Xinerama screen was mentioned in wm-spec maillist in 2007, but has never really been proposed, discussed and included in wm-spec. Hence this "hack". -- Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/

2 1

xmonad 0.9 on ubuntu 9.10
by Tony Morris 19 Nov '09

19 Nov '09

Hello, I am trying to get xmonad running on ubuntu 9.10 per http://www.haskell.org/haskellwiki/Xmonad/Using_xmonad_in_Gnome#Ubuntu_Karm… I have set the WINDOW_MANAGER in ~/.gnomerc but when gnome starts I get a background screen, no gnome panel/menu and no ability to use xmonad keys (e.g. CTRL-mod-enter does not start a terminal). I have tried other methods mentioned on the link above and encountered no to poor success. Any hints? -- Tony Morris http://tmorris.net/

3 3