- xmonad - Haskell.org

Re: [xmonad] xmonad.hs to update
by Platon Pronko 04 Oct '21

04 Oct '21

Hi! Congratulations! I don't use spiral layout, but something like this should probably work: -- add to imports import XMonad.Layout.Spiral -- replace layoutHook in main layoutHook = avoidStruts $ spiral (6/7) Best regards, Platon Pronko On 2021-10-04 09:36, Alain Bertrand wrote: > Hi thanks for you answer, > > Xmonad does compile and run. Moreover, I have understood that the cross shaped cursor is displayed when I am on an empty workspace or on xfce4-panel window (I can bear it). > > I have fixed the empty workspace problem with spawnOn "bg" "feh --bg-tile /usr/share/WindowMaker/Backgrounds/BlueImage.jpeg". Thanks Gauthier. > > the only thing that I still need is how to use the spiral layout. > > Thanks in advance, and have a good day, > > Alain > On 03/10/2021 14:33, Platon Pronko wrote: >> Hi! >> >> Does it still compile sucessfully? (check with `xmonad --recompile`) >> Does it start at all? (check with `ps -ef | grep xmonad`) >> >> Your description sounds like window manager failed to start completely. >> >> Best regards, >> Platon Pronko >> >> On 2021-10-02 11:15, Alain Bertrand wrote: >>> Hi, >>> >>> On Debian 11, the following xmonad.hs seems not to work anymore. >>> >>> Cursor is changed to a cross and empty workspaces display the last used workspace screen. >>> >>> Moreover, I would like to add the spiral layout which seems to be so great. I feel a little bit ashamed that after all these years using Xmonad, I still can't configure it by myself but in fact it breaks so rarely that there is no point in tinkering with it. >>> >>> Thanks in advance. >>> >>> >>> Alain >>> >>> import XMonad >>> import XMonad.Hooks.SetWMName >>> import XMonad.Hooks.ManageDocks >>> import qualified Data.Map as M >>> import Graphics.X11.Xlib >>> import XMonad.Config.Azerty >>> import XMonad.Prompt >>> import XMonad.Prompt.Shell >>> import XMonad.Prompt.XMonad >>> import XMonad.Actions.SpawnOn >>> >>> myStartUpHook :: X () >>> myStartUpHook = do >>> spawnOn "panel" "xfce4-panel" >>> spawnOn "clavier" "/home/alain/bin/clavier_conf" >>> spawnOn "1" "/usr/bin/firefox" >>> spawnOn "1" "/usr/bin/thunderbird" >>> setWMName "LG3D" >>> >>> >>> main=do >>> xmonad $ docks def >>> { >>> layoutHook=avoidStruts $ layoutHook defaultConfig >>> , manageHook=manageHook defaultConfig <+> manageDocks >>> , modMask = mod4Mask >>> , keys = myKeys <+> keys azertyConfig >>> , startupHook = myStartUpHook >>> } >>> >>> >>> -- main=do >>> -- xmonad { keys = myKeys <+> keys azertyConfig } >>> -- { >>> -- layoutHook=avoidStruts $ layoutHook defaultConfig >>> -- , manageHook=manageHook defaultConfig <+> manageDocks >>> -- , startupHook = setWMName "LG3D" >>> -- } >>> -- >>> -- >>> myKeys conf@(XConfig {XMonad.modMask = modm}) = M.fromList >>> [ ((modm, xK_F12), xmonadPrompt defaultXPConfig) >>> , ((modm, xK_F3 ), shellPrompt defaultXPConfig) >>> ] >>> >>> _______________________________________________ >>> xmonad mailing list >>> xmonad(a)haskell.org >>> http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad > >

1 0

xmonad.hs to update
by Alain Bertrand 03 Oct '21

03 Oct '21

Hi, On Debian 11, the following xmonad.hs seems not to work anymore. Cursor is changed to a cross and empty workspaces display the last used workspace screen. Moreover, I would like to add the spiral layout which seems to be so great. I feel a little bit ashamed that after all these years using Xmonad, I still can't configure it by myself but in fact it breaks so rarely that there is no point in tinkering with it. Thanks in advance. Alain import XMonad import XMonad.Hooks.SetWMName import XMonad.Hooks.ManageDocks import qualified Data.Map as M import Graphics.X11.Xlib import XMonad.Config.Azerty import XMonad.Prompt import XMonad.Prompt.Shell import XMonad.Prompt.XMonad import XMonad.Actions.SpawnOn myStartUpHook :: X () myStartUpHook = do spawnOn "panel" "xfce4-panel" spawnOn "clavier" "/home/alain/bin/clavier_conf" spawnOn "1" "/usr/bin/firefox" spawnOn "1" "/usr/bin/thunderbird" setWMName "LG3D" main=do xmonad $ docks def { layoutHook=avoidStruts $ layoutHook defaultConfig , manageHook=manageHook defaultConfig <+> manageDocks , modMask = mod4Mask , keys = myKeys <+> keys azertyConfig , startupHook = myStartUpHook } -- main=do -- xmonad { keys = myKeys <+> keys azertyConfig } -- { -- layoutHook=avoidStruts $ layoutHook defaultConfig -- , manageHook=manageHook defaultConfig <+> manageDocks -- , startupHook = setWMName "LG3D" -- } -- -- myKeys conf@(XConfig {XMonad.modMask = modm}) = M.fromList [ ((modm, xK_F12), xmonadPrompt defaultXPConfig) , ((modm, xK_F3 ), shellPrompt defaultXPConfig) ]

3 2

Re: [xmonad] xmonad becomes inoperable in random situations
by Platon Pronko 21 Sep '21

21 Sep '21

Hi! hPutStrLn is needed here to send the current window title to xmobar (you have the current window title displayed in your bottom bar, and that's how it gets it). So removing it from xmprocB will result in no window title being displayed. Can you still unfreeze your system by killing the xmobar? If yes, then which one do you need to kill - top or bottom? Best regards, Platon Pronko On 2021-09-20 23:03, Björn Kessler wrote: > Sorry, back again. > > Seems like I celebrated to early. It happened again. But to me it seems as > if it was much later then normally. I never understood, what the hPutStrLn > is for. Would it be worth a try to remove it from xmprocB too? > > With kind regards, > > Bjoern > > Am Mo., 20. Sept. 2021 um 21:39 Uhr schrieb Björn Kessler < > bjoern.lindig(a)gmail.com>: > >> Hey Platon, >> >> this is really great! It seems you've hit the nail to its head. The system >> runs every test safe and easy. I forgot how comfortable it is to have a >> reliable system! Seriously! This is just wonderful! >> >> Thank you so much! >> >> Best Bjoern >> >> Am Mo., 20. Sept. 2021 um 19:48 Uhr schrieb Platon Pronko < >> platon7pronko(a)gmail.com>: >> >>> Hi! >>> >>> Just a stab in the dark, but can you try removing `hPutStrLn xmprocT` >>> from ppOutput? >>> I suspect that without StdinReader your top xmobar just never reads its >>> stdin, but Xmonad continues to send it the output until it hits the >>> pipe limit, and after that everything blocks. >>> >>> Best regards, >>> Platon Pronko >>> >>> On 2021-09-20 20:32, Björn Kessler wrote: >>>> Hey Platon, >>>> >>>> thanks for the hint. Somehow it didn't come to my mind to try that. >>>> Actually I was fiddling around a lot on my Xmonad config because I >>> wanted >>>> to have both a bar on top and on the bottom of the screen. And as it >>> turns >>>> out you where right. If I violently kill xmobar after the issue occurs, >>>> everything works fine again. >>>> >>>> Hm, so what did I do wrong? >>>> >>>> I've created a pastie with my config in case someone is having the time >>> to >>>> check it. It would be awesome! >>>> >>>> https://pastie.iem.at/view/d4d44ce1 --> xmonad.hs >>>> https://pastie.iem.at/view/9374a807 --> xmobar-top.hs >>>> https://pastie.iem.at/view/189e5014 --> xmobar-buttom.hs >>>> >>>> Best, >>>> >>>> Bjoern >>>> >>>> Am So., 19. Sept. 2021 um 18:46 Uhr schrieb Platon Pronko < >>>> platon7pronko(a)gmail.com>: >>>> >>>>> Hi! >>>>> >>>>> I'm not an expert in this by any means, but I'll try giving some >>> pointers >>>>> in case you haven't explored them already. >>>>> >>>>> Have you looked at the `top` output to see what process is consuming >>>>> CPU or disk resources? Since you say that only X is affected, then ttys >>>>> should be available on Ctrl-Alt-F2 (3,4,etc) and you can run top there. >>>>> >>>>> How complex is your Xmonad config? Have you tried removing most >>>>> customizations >>>>> and running the simplest config possible? >>>>> >>>>> I doubt that rotated monitor is relevant here, but you can easily check >>>>> that - >>>>> just run non-rotated monitor for a while, after the first time it >>> freezes >>>>> again >>>>> you will be sure that rotated monitor wasn't the issue. >>>>> >>>>> Best regards, >>>>> Platon Pronko >>>>> >>>>> On 2021-09-18 14:35, Björn Kessler wrote: >>>>>> Hi there, >>>>>> >>>>>> I'm new to the list and poppin in with a question. But before getting >>> to >>>>>> that, I would like to send out a big "thank you" to the community, >>> that >>>>> is >>>>>> providing this greatest windowmanager ever! I'm using it since more >>> than >>>>> 5 >>>>>> years now and never had an issue... >>>>>> >>>>>> ... up to now: My xmonad is freezing again and again and I don't >>> really >>>>>> know how to figure out what causes the issue. It happens when I use >>>>>> programs like musescore or radium. I don't know, maybe because they >>> put >>>>>> heavy load on graphics or something!? Anyway, when it happens, some >>>>>> functionalities of the program stay functional, but changing the >>> screen >>>>> in >>>>>> xmonad or starting new programms via dmenu is impossible then. >>>>>> >>>>>> I'm on archlinux and xmonad.errors doesn't show anything, as far as I >>> can >>>>>> see. I'm using xorg and I'm launching it with startx from the command >>>>>> prompt. >>>>>> >>>>>> In my Xorg.0.log I get the following error: >>>>>> >>>>>>> [ 6588.014] (EE) event6 - LITE-ON Technology USB NetVista Full >>> Width >>>>>> Keyboard.: client bug: event processing lagging behind by 13ms, your >>>>> system >>>>>> is too slow >>>>>> >>>>>> The slowest device in my setup is the harddrive. I now it needs >>>>> replacement >>>>>> soon. Can it be, that X freezes because of a slow harddrive? >>>>>> >>>>>> I'm also using a rotated monitor. Can it be that the issue is >>> concerned >>>>>> with the portrait view? >>>>>> >>>>>> Here is my script that I use to do the rotation >>>>>>> xrandr --output VGA-1 --off --output DP-1 --off --output HDMI-1 >>> --off >>>>>> --output DP-2 --mode 1680x1050 --pos 0x0 --rotate left --output >>> HDMI-2 >>>>>> --off >>>>>> >>>>>> If someone is having any idea on how to narrow this down, I'd be very >>>>>> thankfull. Even only to figure out whether it is concerned with >>> xmonad or >>>>>> not, would help a lot. I'm suspecting xmonad, because after killing it >>>>> and >>>>>> restarting X everything works fine again, but I know that by killing >>>>> xmonad >>>>>> I'm also stopping a whole lot of other processes too... >>>>>> >>>>>> With kind regards, >>>>>> >>>>>> Bjroern >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> xmonad mailing list >>>>>> xmonad(a)haskell.org >>>>>> http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad >>>>>> >>>>> _______________________________________________ >>>>> xmonad mailing list >>>>> xmonad(a)haskell.org >>>>> http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad >>>>> >>>> >>> >> >

1 0

Re: [xmonad] xmonad becomes inoperable in random situations
by Platon Pronko 20 Sep '21

20 Sep '21

Hi! Just a stab in the dark, but can you try removing `hPutStrLn xmprocT` from ppOutput? I suspect that without StdinReader your top xmobar just never reads its stdin, but Xmonad continues to send it the output until it hits the pipe limit, and after that everything blocks. Best regards, Platon Pronko On 2021-09-20 20:32, Björn Kessler wrote: > Hey Platon, > > thanks for the hint. Somehow it didn't come to my mind to try that. > Actually I was fiddling around a lot on my Xmonad config because I wanted > to have both a bar on top and on the bottom of the screen. And as it turns > out you where right. If I violently kill xmobar after the issue occurs, > everything works fine again. > > Hm, so what did I do wrong? > > I've created a pastie with my config in case someone is having the time to > check it. It would be awesome! > > https://pastie.iem.at/view/d4d44ce1 --> xmonad.hs > https://pastie.iem.at/view/9374a807 --> xmobar-top.hs > https://pastie.iem.at/view/189e5014 --> xmobar-buttom.hs > > Best, > > Bjoern > > Am So., 19. Sept. 2021 um 18:46 Uhr schrieb Platon Pronko < > platon7pronko(a)gmail.com>: > >> Hi! >> >> I'm not an expert in this by any means, but I'll try giving some pointers >> in case you haven't explored them already. >> >> Have you looked at the `top` output to see what process is consuming >> CPU or disk resources? Since you say that only X is affected, then ttys >> should be available on Ctrl-Alt-F2 (3,4,etc) and you can run top there. >> >> How complex is your Xmonad config? Have you tried removing most >> customizations >> and running the simplest config possible? >> >> I doubt that rotated monitor is relevant here, but you can easily check >> that - >> just run non-rotated monitor for a while, after the first time it freezes >> again >> you will be sure that rotated monitor wasn't the issue. >> >> Best regards, >> Platon Pronko >> >> On 2021-09-18 14:35, Björn Kessler wrote: >>> Hi there, >>> >>> I'm new to the list and poppin in with a question. But before getting to >>> that, I would like to send out a big "thank you" to the community, that >> is >>> providing this greatest windowmanager ever! I'm using it since more than >> 5 >>> years now and never had an issue... >>> >>> ... up to now: My xmonad is freezing again and again and I don't really >>> know how to figure out what causes the issue. It happens when I use >>> programs like musescore or radium. I don't know, maybe because they put >>> heavy load on graphics or something!? Anyway, when it happens, some >>> functionalities of the program stay functional, but changing the screen >> in >>> xmonad or starting new programms via dmenu is impossible then. >>> >>> I'm on archlinux and xmonad.errors doesn't show anything, as far as I can >>> see. I'm using xorg and I'm launching it with startx from the command >>> prompt. >>> >>> In my Xorg.0.log I get the following error: >>> >>>> [ 6588.014] (EE) event6 - LITE-ON Technology USB NetVista Full Width >>> Keyboard.: client bug: event processing lagging behind by 13ms, your >> system >>> is too slow >>> >>> The slowest device in my setup is the harddrive. I now it needs >> replacement >>> soon. Can it be, that X freezes because of a slow harddrive? >>> >>> I'm also using a rotated monitor. Can it be that the issue is concerned >>> with the portrait view? >>> >>> Here is my script that I use to do the rotation >>>> xrandr --output VGA-1 --off --output DP-1 --off --output HDMI-1 --off >>> --output DP-2 --mode 1680x1050 --pos 0x0 --rotate left --output HDMI-2 >>> --off >>> >>> If someone is having any idea on how to narrow this down, I'd be very >>> thankfull. Even only to figure out whether it is concerned with xmonad or >>> not, would help a lot. I'm suspecting xmonad, because after killing it >> and >>> restarting X everything works fine again, but I know that by killing >> xmonad >>> I'm also stopping a whole lot of other processes too... >>> >>> With kind regards, >>> >>> Bjroern >>> >>> >>> _______________________________________________ >>> xmonad mailing list >>> xmonad(a)haskell.org >>> http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad >>> >> _______________________________________________ >> xmonad mailing list >> xmonad(a)haskell.org >> http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad >> >

1 0

xmonad becomes inoperable in random situations
by Björn Kessler 19 Sep '21

19 Sep '21

Hi there, I'm new to the list and poppin in with a question. But before getting to that, I would like to send out a big "thank you" to the community, that is providing this greatest windowmanager ever! I'm using it since more than 5 years now and never had an issue... ... up to now: My xmonad is freezing again and again and I don't really know how to figure out what causes the issue. It happens when I use programs like musescore or radium. I don't know, maybe because they put heavy load on graphics or something!? Anyway, when it happens, some functionalities of the program stay functional, but changing the screen in xmonad or starting new programms via dmenu is impossible then. I'm on archlinux and xmonad.errors doesn't show anything, as far as I can see. I'm using xorg and I'm launching it with startx from the command prompt. In my Xorg.0.log I get the following error: > [ 6588.014] (EE) event6 - LITE-ON Technology USB NetVista Full Width Keyboard.: client bug: event processing lagging behind by 13ms, your system is too slow The slowest device in my setup is the harddrive. I now it needs replacement soon. Can it be, that X freezes because of a slow harddrive? I'm also using a rotated monitor. Can it be that the issue is concerned with the portrait view? Here is my script that I use to do the rotation > xrandr --output VGA-1 --off --output DP-1 --off --output HDMI-1 --off --output DP-2 --mode 1680x1050 --pos 0x0 --rotate left --output HDMI-2 --off If someone is having any idea on how to narrow this down, I'd be very thankfull. Even only to figure out whether it is concerned with xmonad or not, would help a lot. I'm suspecting xmonad, because after killing it and restarting X everything works fine again, but I know that by killing xmonad I'm also stopping a whole lot of other processes too... With kind regards, Bjroern

3 2

Best "go to previous window" solution
by Ruben Astudillo 12 Aug '21

12 Aug '21

Hello list. To move to the previous selected window, I use the module `XMonad.Actions.GroupNavigation` and its `historyHook` with a key set up to `nextMatch History (pure True)`. With this I can alternate to the previously selected window. But it is not a repeatable process, because once I jump to the previous window, the window from which I jumped becomes the "previous window". That means I can only alternate between two windows with this setup. What I would like is to have the equivalent of `C-o` on vim or `C-u C-<space>` on emacs but without it being limited to two movements. What modules on contrib should I be using? -- -- Rubén. pgp: 4EE9 28F7 932E F4AD

3 2

Is there a way to reparent a window manually?
by Platon Pronko 26 Jul '21

26 Jul '21

Hi! I'm trying to run Unity Editor under XMonad. Unfortunately I'm having issues - sub-windows of the main window are not redrawn properly, resulting in ugly mess (previously-opened menu lists do not disappear, etc). It seems that this could be happening due to XMonad being non-reparenting (I ran the same app under XFCE, and it seems to work okay). Is there a way to reparent a window manually? I tried creating a new X window via Python and Xlib, as in this example: https://rosettacode.org/wiki/Window_creation/X11#Python and then reparenting the window to it via `xdotool windowreparent` and subsequently `xdotool windowmap` plus `xdotool windowsize`. It partially worked - the app window correctly resized to fill the parent window, seems to be reacting to mouse move and mouse scroll events (interface elements are highlighted), reacts to keyboard events, but completely ignores mouse button events (clicks/drags). I'm attaching create_window.py script I used to create the window. Any idea about what am I missing? Maybe my event masks are wrong? Best regards, Platon Pronko

3 15

tweaking xmonad into a reparenting window manager
by Platon Pronko 24 Jul '21

24 Jul '21

Hi! Is there some fundamental reason why Xmonad is non-reparenting? My current (naive) understanding is that Xmonad does not reparent the windows simply as a small optimization (why create a second window if you can live with one window just fine). If that's the case, then adding a tweak that allows Xmonad to do reparenting should be doable. However I understand that it will be non-trivial undertaking, so I wanted advice of more experienced developers before I sink in a lot of time to find out that this is fundamentally impossible for some reason. Best regards, Platon Pronko

2 1

Managing Multiple Displays
by Eyal Erez 20 Jul '21

20 Jul '21

Hi, I often use multiple displays. Here are some configurations that I've used with my laptop: 1. Laptop monitor only 2. External monitor only (laptop lid closed) 3. External and laptop monitor at the same time. 4. Two external monitors (laptop lid closed). In order to show display correctly (which monitor is to the right/left of which and which is on/off) and shift trayer around to the right monitor and position, I've written a script that parses the output of xrandr, figures out if the laptop lid is open or not, then calls xrandr again to activate the right monitors and kills and relaunches trayer and places it in the correct position. I launch this script from a keybinding configured in xmonad.hs. This works, however, it has several disadvantages. The first is that adding a new configuration is a bit tedious -- this doesn't happen very often so it's not a huge deal. The other is that I can only activate the script if my screen is unlocked. This means that if my laptop is suspended and I want to disconnect the external monitor and put it in my bag for later use, I need to first wake it up, unlock it, launch the script to turn the laptop monitor on, and then put it away. Otherwise, I'll be staring at a blank screen when I turn it on and have to guess what to press to unlock and use the script. I was wondering how others deal with this challenge? Are there other, more well-built tools, than the script I have to do this more robustly and automatically? Thank you, -- There are 10 types of people, those who know binary and those who don't.

7 7

Re: [xmonad] question about code in XMonad.Actions.GridSelect
by Platon Pronko 15 Jul '21

15 Jul '21

Ah, yes, stack recommended to add it to extra deps. But I got scared of the long "sha256:30d72d..." string, wanted to keep it much simpler since I'm new here. I think if we want to update random then it would make sense to do it in separate PR - I can do it if you'd like. Best regards, Platon Pronko On 2021-07-15 13:20, Solid wrote: > On Thu, Jul 15 2021 11:34, Platon Pronko wrote: >> I've decided to just go with randomR, simpler and guaranteed to >> work. Here's the PR: > > You're probably right; though the whole Random class is (soft) > deprecated. Quoting from the docs[1] > >> Random exists primarily for backwards compatibility with version 1.1 >> of this library. In new code, use the better specified Uniform and >> UniformRange instead. > >> P.S. I don't see an attachment in your email. But if there was simply an addition of >> "random >= 1.2" to build-depends (library and tests), then I've already tried and >> stack gave me lots of new errors (apparently the ghc snapshot it downloaded >> already includes random-1.1?). > > Ah, silly me; sorry. Should be attached now. If it's not on stackage > yet, you also have to add the version to the extra-deps. > > [1]: https://hackage.haskell.org/package/random-1.2.0/docs/System-Random.html#v:… >

1 1