- xmonad - Haskell.org

Issue 257 in xmonad: OpenOffice Impress - Presentation-Mode damaged whole windowmanager
by codesite-noreply＠google.com 02 Jan '09

02 Jan '09

Status: New Owner: ---- New issue 257 by domi...(a)dbruhn.de: OpenOffice Impress - Presentation-Mode damaged whole windowmanager http://code.google.com/p/xmonad/issues/detail?id=257 What steps will reproduce the problem? 1. Install OpenOffice.org 3.0 impress (doesnt seem to work with 2.x) 2. Create a new presentation (one slide is enough) 3. Start the presentation (Pres F5) 4. While in presentation-mode press Mod+n to switch to another workspace (not the one the presentation was started on) 5. End the presentation by clicking through all slides 6. Now the window-manager is damaged: The mouse-cursor is a cross, no hotkey works. The only solution is to kill X. What is the expected output? What do you see instead? I expect xmonad to work! :P What version of the product are you using? On what operating system? XMonad from darcs, OpenOffice.org 3.x from debian experimental, Debian unstable -- 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 228 in xmonad: OpenOffice fullscreen presentation is tiled
by codesite-noreply＠google.com 02 Jan '09

02 Jan '09

Comment #4 on issue 228 by domi...(a)dbruhn.de: OpenOffice fullscreen presentation is tiled http://code.google.com/p/xmonad/issues/detail?id=228 Doesnt seem to be a issue in ooimpress 3.0, the presentation-window is fullscreen there, dont know why! -- 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 246 in xmonad: ewmhDesktopsLogHookCustom throws(?) Maybe.fromJust: Nothing
by codesite-noreply＠google.com 02 Jan '09

02 Jan '09

Updates: Status: Fixed Comment #1 on issue 246 by byorgey: ewmhDesktopsLogHookCustom throws(?) Maybe.fromJust: Nothing http://code.google.com/p/xmonad/issues/detail?id=246 (No comment was entered for this change.) -- 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

patch for ewmhDesktopLogHookCustom
by rupa 02 Jan '09

02 Jan '09

Hi, I hope this patch is formatted correctly. I have tested it to the best of my ability and it fixes my issues nicely.

2 1

Issue 244 in xmonad: .xmonad/history permissions may allow information leakage
by codesite-noreply＠google.com 02 Jan '09

02 Jan '09

Updates: Status: Fixed Comment #3 on issue 244 by byorgey: .xmonad/history permissions may allow information leakage http://code.google.com/p/xmonad/issues/detail?id=244 (No comment was entered for this change.) -- 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: Prompt: Change Filemode to 600 for history-file (fixe...
by Dominik Bruhn 02 Jan '09

02 Jan '09

Thu Dec 18 01:16:01 CET 2008 Dominik Bruhn <dominik(a)dbruhn.de> * Prompt: Change Filemode to 600 for history-file (fixes bug 244)

2 1

Issue 254 in xmonad: XMonad.Contrib.Util.Run.runInTerm does not work with terminal = "gnome-terminal"
by codesite-noreply＠google.com 01 Jan '09

01 Jan '09

Comment #5 on issue 254 by twpayne: XMonad.Contrib.Util.Run.runInTerm does not work with terminal = "gnome-terminal" http://code.google.com/p/xmonad/issues/detail?id=254 I've only got basic notions of Haskell, but my understanding is that safeRunInTerm avoids the shell but the command to be run is still converted to a string. Basically: runInTerm (based on unsafeSpawn) does this (pseudo code): exec 'sh -c "terminal -e ssh localhost"' -- convert to string, pass to sh safeRunInTerm (based on safeSpawn) does this: exec 'terminal -e ssh localhost' -- convert to string. don't pass to sh but what's really needed is this: exec ['terminal', '-e', 'ssh localhost'] -- don't convert to string, invoke -- exec with list of arguments Note how in the last example 'ssh localhost' is passed as a single argument, where in both runInTerm and safeRunInTerm it is split into two arguments (because a string passed to exec is implicitly split on whitespace to produce the list of arguments). So, unfortunately I think the changes run a bit deeper than just using safeSpawn :-( -- 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 254 in xmonad: XMonad.Contrib.Util.Run.runInTerm does not work with terminal = "gnome-terminal"
by codesite-noreply＠google.com 01 Jan '09

01 Jan '09

Comment #4 on issue 254 by gwern0: XMonad.Contrib.Util.Run.runInTerm does not work with terminal = "gnome-terminal" http://code.google.com/p/xmonad/issues/detail?id=254 OK. If you really want to not go through the shell, is there something wrong with 'safeRunInTerm'? I recall that this was the use-case the safe/unsafe distinction was meant to cover. If there is nothing wrong with safeRunInTerm, perhaps you should lobby the maintainers of Prompt.Man and Prompt.Ssh to use that instead. -- 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 256 in xmonad: Xmonad should start programs in the workspace they were launched
by codesite-noreply＠google.com 31 Dec '08

31 Dec '08

Comment #3 on issue 256 by oscar.boykin: Xmonad should start programs in the workspace they were launched http://code.google.com/p/xmonad/issues/detail?id=256 This is a shame that the X11 protocol is not sufficient to support this. I'll look into using managehook to get the job done. Thanks. -- 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 256 in xmonad: Xmonad should start programs in the workspace they were launched
by codesite-noreply＠google.com 31 Dec '08

31 Dec '08

Comment #2 on issue 256 by allbery.b: Xmonad should start programs in the workspace they were launched http://code.google.com/p/xmonad/issues/detail?id=256 X11 makes this difficult if not impossible for arbitrary programs. As mentioned above you can do it with a ManageHook; also some window manager/menu combinations may tell the window manager to place the next window that is created (or the next one with a given title) in a specific workspace, but this is highly unreliable. -- 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