- xmonad - Haskell.org

Issue 582 in xmonad: Add <XF86AudioMicMute> to EZConfig multimediaKeys
by codesite-noreply＠google.com 22 Dec '14

22 Dec '14

Status: New Owner: ---- New issue 582 by enm...(a)gmail.com: Add <XF86AudioMicMute> to EZConfig multimediaKeys https://code.google.com/p/xmonad/issues/detail?id=582 What steps will reproduce the problem? 1. Assuming a script exists called "toggle-mic" in the user's PATH 2. Create keybinding for ("<XF86AudioMicMute>", spawn "toggle-mic") 3. Recompile/restart xmonad 4. Press <XF86AudioMicMute> 5. "toggle-mic is never called What is the expected output? What do you see instead? The script "toggle-mic" should have been called. It is not. What version of the product are you using? On what operating system? community/xmonad 0.11-9 (Arch Linux, not from haskell-core) Linux 3.17.4-1 (Arch Linux) Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". xmonad --recompile (no output) Please provide any additional information below. I'm currently forced to use xbindkeys to recognize <XF86AudioMicMute> and launch my script to toggle to mic input. Attachments: xmonad.hs 8.4 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 1

(DynamicWorkspaces) Generalize new workspace addition functions to support arbitrary insertion
by Arjun Comar 21 Dec '14

21 Dec '14

This patch was developed based on a request for functionality at: http://www.reddit.com/r/xmonad/comments/2pnjse/dynamic_workspaces_appending… * Generalize new workspace addition functions to support arbitrary insertion. The current DynamicWorkspaces module only supports adding new workspaces at the start of the list of workspaces. This means when binding workspaces to keys based on the position in the list, key bindings can change as workspaces are added in removed in a far more destructive way than necessary. Instead, supporting appending and arbitrary insertion allows the user to determine where the new workspace should be added. This patch is a straight generalization of the addHiddenWorkspace' function. Rather than always using `(:)` to insert the new workspace into the list of workspaces, this patches causes it to use an arbitrary list insertion function instead. A few new functions are added to prevent breakage of external code while exported functions are left unchanged. List of new functions: appendWorkspace appendWorkspacePrompt addWorkspaceAt addHiddenWorkspaceAt Existing functions were modified to call their generalized brethren where possible without changing functionality. This patch should not change behavior for any existing users of this module.

3 2

Re: [xmonad] darcs patch: X.L.Master: Add FixMaster layout modifier
by adam vogt 21 Dec '14

21 Dec '14

Thanks Anton, I've applied your patch On Fri, Dec 19, 2014 at 8:25 PM, Anton Vorontsov <anton(a)enomsg.org> wrote: > 1 patch for repository http://code.haskell.org/XMonadContrib: > > Fri Dec 19 17:13:39 PST 2014 Anton Vorontsov <anton(a)enomsg.org> > * X.L.Master: Add FixMaster layout modifier > > This layout modifier is useful for the case if you desire to add a master > pane that has fixed width (it's fixed even if there is just one window > opened). Especially nice feature if you don't want to have too wide > terminal in a master pane. > > The layout is implemented as an addition to Master layout, so it reuses > most of the code. > > > > [X.L.Master: Add FixMaster layout modifier > Anton Vorontsov <anton(a)enomsg.org>**20141220011339 > Ignore-this: 82e9736853287f753248af41843ceb6b > > This layout modifier is useful for the case if you desire to add a master > pane that has fixed width (it's fixed even if there is just one window > opened). Especially nice feature if you don't want to have too wide > terminal in a master pane. > > The layout is implemented as an addition to Master layout, so it reuses > most of the code. > ] { > hunk ./XMonad/Layout/Master.hs 21 > -- $usage > > mastered, > + fixMastered, > multimastered, > AddMaster, > ) where > hunk ./XMonad/Layout/Master.hs 29 > import XMonad > import qualified XMonad.StackSet as S > import XMonad.Layout.LayoutModifier > +import Control.Monad > > -- $usage > -- You can use this module with the following in your @~\/.xmonad\/xmonad.hs@: > hunk ./XMonad/Layout/Master.hs 41 > -- > -- > mastered (1/100) (1/2) $ Grid > -- > +-- Or if you prefer to have a master with fixed width: > +-- > +-- > fixMastered (1/100) (1/2) $ Grid > +-- > -- Or if you want multiple (here two) master windows from the beginning: > -- > -- > multimastered 2 (1/100) (1/2) $ Grid > hunk ./XMonad/Layout/Master.hs 62 > -- layout > data AddMaster a = AddMaster Int Rational Rational deriving (Show, Read) > > --- | Modifier which converts given layout to a mastered one > multimastered :: (LayoutClass l a) => > Int -- ^ @k@, number of master windows > -> Rational -- ^ @delta@, the ratio of the screen to resize by > hunk ./XMonad/Layout/Master.hs 78 > mastered delta frac = multimastered 1 delta frac > > instance LayoutModifier AddMaster Window where > - modifyLayout (AddMaster k delta frac) = applyMaster k delta frac > + modifyLayout (AddMaster k delta frac) = applyMaster False k delta frac > modifierDescription _ = "Mastered" > > pureMess (AddMaster k delta frac) m > hunk ./XMonad/Layout/Master.hs 88 > > pureMess _ _ = Nothing > > +data FixMaster a = FixMaster (AddMaster a) deriving (Show, Read) > + > +instance LayoutModifier FixMaster Window where > + modifyLayout (FixMaster (AddMaster k d f)) = applyMaster True k d f > + modifierDescription (FixMaster a) = "Fix" ++ modifierDescription a > + pureMess (FixMaster a) m = liftM FixMaster (pureMess a m) > + > +fixMastered :: (LayoutClass l a) => > + Rational -- ^ @delta@, the ratio of the screen to resize by > + -> Rational -- ^ @frac@, what portion of the screen to use for the master window > + -> l a -- ^ the layout to be modified > + -> ModifiedLayout FixMaster l a > +fixMastered delta frac = ModifiedLayout . FixMaster $ AddMaster 1 delta frac > + > -- | Internal function for adding a master window and let the modified > -- layout handle the rest of the windows > applyMaster :: (LayoutClass l Window) => > hunk ./XMonad/Layout/Master.hs 105 > - Int > + Bool > + -> Int > -> Rational > -> Rational > -> S.Workspace WorkspaceId (l Window) Window > hunk ./XMonad/Layout/Master.hs 112 > -> Rectangle > -> X ([(Window, Rectangle)], Maybe (l Window)) > -applyMaster k _ frac wksp rect = do > +applyMaster f k _ frac wksp rect = do > let st= S.stack wksp > let ws = S.integrate' $ st > hunk ./XMonad/Layout/Master.hs 115 > - let n = length ws > + let n = length ws + fromEnum f > if n > 1 then do > if(n<=k) then > return ((divideCol rect ws), Nothing) > } > > > _______________________________________________ > xmonad mailing list > xmonad(a)haskell.org > http://www.haskell.org/mailman/listinfo/xmonad >

1 0

darcs patch: X.L.Master: Add FixMaster layout modifier
by Anton Vorontsov 19 Dec '14

19 Dec '14

1 patch for repository http://code.haskell.org/XMonadContrib: Fri Dec 19 17:13:39 PST 2014 Anton Vorontsov <anton(a)enomsg.org> * X.L.Master: Add FixMaster layout modifier This layout modifier is useful for the case if you desire to add a master pane that has fixed width (it's fixed even if there is just one window opened). Especially nice feature if you don't want to have too wide terminal in a master pane. The layout is implemented as an addition to Master layout, so it reuses most of the code.

1 0

Issue 583 in xmonad: Lockup with runOrRaisePrompt
by codesite-noreply＠google.com 19 Dec '14

19 Dec '14

Status: New Owner: ---- New issue 583 by Frederic...(a)gmail.com: Lockup with runOrRaisePrompt https://code.google.com/p/xmonad/issues/detail?id=583 What steps will reproduce the problem? 1. Open a couple of windows. 2. Use key combinations for the runOrRaise prompt. 3. While the prompt is open, click on a window which didn't have the focus. What is the expected output? What do you see instead? Expected either the focus to change or at least the prompt to close. What actually happens is the whole xmonad session locks up. Unable to close the prompt, no key combinations work. Must kill the session. What version of the product are you using? On what operating system? XMonad 0.11 on NixOS. Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". Attachments: xmonad.hs 13.3 KB xmonad-x86_64-linux 3.3 MB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 0

Added a new simple layout
by Norbert Zeh 12 Dec '14

12 Dec '14

... and thought I'd share. Patch is attached. Cheers, Norbert

1 0

Use atomic window props in window manage hook
by Chris Bell 12 Dec '14

12 Dec '14

Hi, all I was wondering, how could I set a window to float based on its atomic window properties? I'm running Xmonad raw on top of X on Fedora 20; no DE. According to xprop, the only 'special' property of this window is: _NET_WM_STATE(ATOM) = _NET_WM_STATE_ABOVE, _NET_WM_STATE_STICKY particularly the STATE_ABOVE property. So far, I haven't found a reliable way to extract and check if this property exists is set within a mange hook. I've tried pulling the entire property as a stringProperty - and later as an atomic using getAtom - and looking for my string with IsInfixOf (but I think that was pretty misguided, since it wouldn't compile), and I've tried checking against: ( isInProperty "_NET_WM_STATE" "_NET_WM_STATE_ABOVE" ) and have also tried it with "_NET_WM_STATE(ATOM)". I don't get any compile errors, but... it doesn't automatically float the windows, either. I apologize if it's something simple I'm overlooking - I've found the Haskell difficulty curve to be more extreme than any other language I've worked with. With the possible exception of Matlab. The window is one of those fancy special new "panel" not-windows that Chrome is implementing; it's for the Hangouts extension with 'enable panels' turned on in chrome://flags/#enable-panels. They're frustrating, because Chrome can actually handle them as dockable internal window, docking them at the bottom of the browser. Or it can be handled by the OS WM. All of the window properties are identical to a normal Chrome window, except the STATE_ABOVE flag, so that's all I can think to use. Any suggestions are more than welcome. Regards, Chris Bell Ph.D. Candidate, Teaching Assistant, Gentleman, Scholar, Penguin Wrangler University of South Florida College of Engineering Department of Computer Science and Engineering NarMOS Research Team, Official Daemon Charmer

3 4

Issue 538 in xmonad: X.H.DynamicBars call to xrrSelectInput has no effect
by codesite-noreply＠google.com 10 Dec '14

10 Dec '14

Status: New Owner: ---- New issue 538 by johnnysp...(a)gmail.com: X.H.DynamicBars call to xrrSelectInput has no effect http://code.google.com/p/xmonad/issues/detail?id=538 What steps will reproduce the problem? 1. Use attached xmonad.hs (vanilla + minimal DynamicBars). 2. Turn second display off and on: xrandr --output VGA1 --off xrandr --output VGA1 --preferred --right-of LVDS1 Bonus: 3. Apply select_input_fix.dpatch, rebuild and restart xmonad. 4. Turn second display off and on. 5. Undo previous patch, apply select_input_not_fix.dpatch, rebuild and restart xmonad. 6. Turn second display off and on. What is the expected output? What do you see instead? Expected: In steps 2, 4, and 6: see "DESTROYING"/"CREATING" messages in xmonad output. Actual: Only step 4 produces the expected messages. Steps 2 and 6 produce no output. What version of the product are you using? On what operating system? xmonad 0.11 (darcs) xmonad-contrib 0.11 (darcs) xorg 1.14.0 xrandr 1.4.0 X11 (Haskell binding) 1.6.1.1 Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". "xmonad --recompile" produces no output. Please provide any additional information below. I'm expecting step 2 to work because dynStatusBarStartup calls xrrSelectInput. This apparently doesn't do what it's supposed to do for me, possibly for the same reason that step 6 doesn't work. Attachments: xmonad.hs 551 bytes select_input_fix.dpatch 2.2 KB select_input_not_fix.dpatch 2.3 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 4

Auto-detect multiple monitors ...
by aditya siram 09 Dec '14

09 Dec '14

Hi all, I've been using XMonad for a while but mostly just on my laptop. Recently I've started hooking it up to a monitor, but unfortunately I can't seem to tell XMonad that it's a second monitor. I have to mirror the current display or stretch it across multiple monitors. Can someone give me a starting point? I'm comfortable in Haskell. Thanks! -deech

2 1

xmonad as WM for Gnome 3 in Debian jessie
by Thomas Koch 08 Dec '14

08 Dec '14

Hi, I'm installing a new machine with debian jessie which comes with xmonad 0.11 and gnome 3.14. On debian wheezy I could easily use xmonad as the window manager for gnome. Has anybody managed to do the same with a more recent gnome (classic)? What would be a good strategy to try? I've opened a debian bug about this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772179 Regards, Thomas Koch

3 2