- xmonad - Haskell.org

Vote for the new XMonad logo!
by Solid 09 Jan '22

09 Jan '22

Hi, this is a quick reminder that people have one week left to vote for a new XMonad logo! Since there were some concerns regarding having to have a GitHub account in order to participate, we'd like to offer an alternative way of voting—simply reply to this thread. Below are the summarised rules; for more information, as well as the logos themselves, see the GitHub Discussions page[1]: For voting, we will use an instant-runoff[2] type system. In short: - Users rank _a minimum of five (5) submissions_ (by name) according to their preferences in decreasing order (you can vote for your own submission). - If a logo wins a majority of first-preference votes (> 50%) it is chosen. - If not, we eliminate the logo with the least amount of first preference votes, exposing the second preference of those who voted for it. - Rinse and repeat until we have a majority. - If at the end of all that we still don't have a majority, we will act as a tiebreaker and internally vote for a winner from the remaining logos. We will retain veto power in case of inappropriate logos. Team members whose submitted entries are amongst the remaining choices will not partake in the potential tiebreaking vote. Cheers, Tony [1]: https://github.com/xmonad/xmonad/discussions/359 [2]: https://en.wikipedia.org/wiki/Instant-runoff_voting

4 3

withWorkspace (Actions.DynamicWorkspaces): use fuzzyMatch?
by Ramon Diaz-Uriarte 28 Dec '21

28 Dec '21

Dear All, Summary: ======== I think withWorkspace, from Actions.DynamicWorkspaces, does not honor fuzzyMatch (Prompt.FuzzyMatch). In contrast, selectWorkspace and renameWorkspace (also from DynamicWorkspaces) do work with fuzzyMatch. workspacePrompt (Prompt.Workspace) and switchProjectPrompt (Actions.DynamicProjects) also work with fuzzyMatch. Details ======== With this in my xmonad.hs mySPcentered = def { searchPredicate = fuzzyMatch , sorter = fuzzySort } the following , ("M-m", withWorkspace mySPcentered (windows . W.shift)) does not use fuzzy matching but , ("M-m", workspacePrompt mySPcentered (windows . W.shift)) does use fuzzy matching. Note that , ("M-a", selectWorkspace mySPcentered) , ("M-s", renameWorkspace mySPcentered) both use fuzzy matching (and both selectWorkspace and renameWorkspace are from DynamicWorkspaces). And note that , ("M-w", switchProjectPrompt myProjectConfig) with switchProjectPrompt from Actions.DynamicProjects, also works with fuzzyMatch. Workaround? =========== Complete Haskell ignorant here, but from looking at the source of withWorkspace (Actions.DynamicWorkspaces) and workspacePrompt (Prompt.Workspace), I wonder if withWorkspace should be written as withWorkspace c job = do ws <- gets (workspaces . windowset) sort <- getSortByIndex let ts = map W.tag $ sort ws job' t | t `elem` ts = job t | otherwise = addHiddenWorkspace t >> job t mkXPrompt (Wor "") c (mkComplFunFromList' c ts) job' I have changed the last line from mkXPrompt (Wor "") c (mkCompl ts) job' to mkXPrompt (Wor "") c (mkComplFunFromList' c ts) job' Using this in my xmonad.hs seems to work fine with windows' shift, copy and shiftThenView (last one from Ivan Malison's https://github.com/ivanmalison/dotfiles/blob/0a84ad772e21155cfc00458b66ccb7…) Best, -- Ramon Diaz-Uriarte Department of Biochemistry, Lab B-31 Facultad de Medicina Universidad Autónoma de Madrid Arzobispo Morcillo, 4 28029 Madrid Spain Phone: +34-91-497-2412 Email: rdiaz02(a)gmail.com r.diaz(a)uam.es https://ligarto.org/rdiaz

2 2

Different xmonad configs?
by nyam 15 Dec '21

15 Dec '21

Hi all! Is there an option to compile and (re)start etc. individual 'xmonad.hs', such as one has different DE/WMs and wants to use e. g. together with their own adapted xmonad? – Like: $ xmonad --file=/path/to/xmonad-de1.hs --recompile $ exec xmonad --file=/path/to/xmonad-de1.hs or $ xmonad --file=/path/to/xmonad-de2.hs --recompile $ xmonad --restart --file=/path/to/xmonad-de2.hs or $ xmonad --recompile --file=/path/to/xmonad-pure.hs $ exec xmonad --file=/path/to/xmonad-pure.hs Would be a cool feature, though so far the manpage or any web resources don't mention it. Cheers!

4 3

xmonad 0.17.0, xmonad-contrib 0.17.0 released!
by Solid 27 Oct '21

27 Oct '21

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ XMONAD AND XMONAD-CONTRIB 0.17.0 ARE AVAILABLE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ New versions of xmonad and xmonad-contrib have been released. Check out our [download page] for instructions on where to get them. It's been a little over 3 years since xmonad 0.15, and a little over 2 years since xmonad-contrib 0.16. A lot has happened. This post is an overview of the most important changes. To celebrate this milestone, we would like to announce a contest for a new xmonad logo (see section 3). Last but not least, in section 4 we're looking to raise funds to keep the XMonad project and community alive and relevant in the next decade. With the [final X.Org Server 21.1 release] being announced today, there are some obvious challenges ahead of us. [download page]: <https://xmonad.org/download.html> [final X.Org Server 21.1 release]: <https://lists.x.org/archives/xorg/2021-October/060799.html> 1 xmonad 0.17.0 ═══════════════ This release includes 156 non-merge commits by 22 contributors! For a full summary of all the changes, see [xmonad's CHANGES.md] file. [xmonad's CHANGES.md]: <https://github.com/xmonad/xmonad/blob/v0.17.0/CHANGES.md> 1.1 Major Breaking Changes ────────────────────────── • `util/GenerateManpage.hs' is no longer distributed in the tarball. 1.2 Selected Features and Improvements ────────────────────────────────────── • Migrated `X.L.LayoutCombinators.(|||)' into `XMonad.Layout', providing the ability to directly jump to a layout with the `JumpToLayout' message. • Improved handling of XDG directories. 1. If all three of xmonad's environment variables (`XMONAD_DATA_DIR', `XMONAD_CONFIG_DIR', and `XMONAD_CACHE_DIR') are set, use them. 2. If there is a build script called `build' (see [here] for usage examples) or configuration `xmonad.hs' in `~/.xmonad', set all three directories to `~/.xmonad'. 3. Otherwise, use the `xmonad' directory in `XDG_DATA_HOME', `XDG_CONFIG_HOME', and `XDG_CACHE_HOME' (or their respective fallbacks). These directories are created if necessary. In the cases of 1. and 3., the build script or executable is expected to be in the config dir. Additionally, the xmonad config binary and intermediate object files were moved to the cache directory (only relevant if using XDG or `XMONAD_CACHE_DIR'). • Recompilation now detects `stack.yaml' (can be a symlink) alongside `xmonad.hs' and switches to using `stack ghc'. Additionally, deprecation warnings during recompilation are no longer suppressed. These can still be suppressed manually using an `OPTIONS_GHC' pragma with `-Wno-deprecations'. [here]: <https://github.com/xmonad/xmonad-testing/tree/master/build-scripts> 2 xmonad-contrib 0.17.0 ═══════════════════════ This release includes 582 non-merge commits by 57 contributors! For a full summary of all the changes, see [xmonad-contrib's CHANGES.md] file. [xmonad-contrib's CHANGES.md]: <https://github.com/xmonad/xmonad-contrib/blob/v0.17.0/CHANGES.md> 2.1 Major Breaking Changes ────────────────────────── • All modules that export bitmap fonts as their default • If xmonad is compiled with XFT support (the default), use an XFT font instead. The previous default expected an X11 misc font (PCF), which is not supported in pango 1.44 anymore and thus some distributions have stopped shipping these. • All modules still exporting a `defaultFoo' constructor • All of these were now removed. You can use the re-exported `def' from `Data.Default' instead. • `XMonad.Hooks.StatusBar', `XMonad.Hooks.StatusBar.PP' (previously `XMonad.Hooks.DynamicLog') and `XMonad.Util.Run' • `spawnPipe' no longer uses binary mode handles and defaults to the current locale encoding instead, `xmonadPropLog' and `xmonadPropLog'' now encode their input string in UTF-8, and `dynamicLogString' no longer encodes its output in UTF-8. When these functions are used together, everything should continue to work as it always has, but in isolation behaviour might change. To get the old `spawnPipe' behaviour, `spawnPipeWithNoEncoding' can now be used, and `spawnPipeWithUtf8Encoding' was added as well to force UTF-8 regardless of locale. • `XMonad.Hooks.DynamicLog' will be deprecated soon in favor of `XMonad.Hooks.StatusBar' which offers a nicer and easier to use interface for status bars. Laptop users who (dis)connect external monitors dynamically should definitely try this new interface: `XMonad.Hooks.DynamicBars' has been deprecated already. • `XMonad.Hooks.EwmhDesktops' • It is no longer recommended to use standalone hooks directly: Instead of `ewmhDesktopsStartup', `ewmhDesktopsLogHook(Custom)' and `ewmhDesktopsEventHook(Custom)', users should now use the `ewmh' combinator. The `Custom' variants have been replaced by a [more composable interface] which now also allows simply marking windows that request focus as urgent instead of immediately focusing them. Instead of `fullscreenEventHook', use `ewmhFullscreen', which now advertises fullscreen support to applications, fixing fullscreen in [mpv] and many others. • `XMonad.Hooks.Script' • `execScriptHook' now has an `X' constraint (was: `MonadIO'), due to changes in how the xmonad core handles XDG directories. • `XMonad.Actions.WorkspaceNames' • The type of `getWorkspaceNames' was changed to fit into the new `ppRename' field of `PP'. [more composable interface]: <https://xmonad.github.io/xmonad-docs/xmonad-contrib-0.17.0/XMonad-Hooks-Ewm…> [mpv]: <https://mpv.io/> 2.2 Selected Features and Improvements ────────────────────────────────────── • `XMonad.Actions.EasyMotion' A new module that allows selection of visible screens using a key chord—inspired by [vim-easymotion]. See the animation in the vim-easymotion repo to get some idea of the functionality of this EasyMotion module. • `XMonad.Prompt.OrgMode' A prompt for interacting with [org-mode]. It can be used to quickly save TODOs, NOTEs, and the like with the additional capability to schedule/deadline a task, or use the primary selection as the contents of the note. • `XMonad.Hooks.StatusBar' A new module, providing a nicer, composable interface for status bars that replaces `XMonad.Hooks.DynamicLog' and `XMonad.Hooks.DynamicBars'. Supports property-based as well as pipe-based status bars, multiple status bars (Xinerama), and takes care of restarting the bars as needed. • `XMonad.Hooks.Rescreen' A new module, providing custom hooks for screen (xrandr) configuration changes. These are used internally by `XMonad.Hooks.StatusBar' to restart status bars/systrays after xrandr, and can also be used to invoke xrandr or autorandr when an output is (dis)connected. • `XMonad.Util.Hacks' A collection of hacks and fixes that should be easily accessible to users, like a fix for the fullscreen behaviour of chromium based applications when using windowed fullscreen, or a fix to make certain Java applications play more nicely with xmonad. • `XMonad.Hooks.WindowSwallowing' A new module to implement window swallowing; optionally via sublayouting. Hide parent windows like terminals when opening other programs (like image viewers) from within them, restoring them once the child application closes. • `XMonad.Util.ClickableWorkspaces' A new module providing `clickablePP', which when applied to the `PP' pretty-printer used by `XMonad.Hooks.StatusBar.PP', will make the workspace tags clickable in XMobar (for switching focus). Note that `XMonad.Layout.IndependentScreens' and `XMonad.Actions.WorkspaceNames' now also use the same composable `ppRename' interface as `XMonad.Util.ClickableWorkspaces' so it's much easier to use them with one another. • `XMonad.Util.Loggers' • Added `logTitles' to log all window titles (focused and unfocused ones) on the focused workspace, as well as `logTitlesOnScreen' as a screen-specific variant thereof. • `XMonad.Actions.TopicSpace' • Added `TopicItem', as well as the helper functions `topicNames', `tiActions', `tiDirs', `noAction', and `inHome' for a drastically simpler specification of topics. • `XMonad.Hooks.ServerMode' • To make it easier to use, the `xmonadctl' client is now included in `scripts/'. [vim-easymotion]: <https://github.com/easymotion/vim-easymotion> [org-mode]: <https://orgmode.org/> 3 Logo Contest ══════════════ We'd also like to announce a contest to create a new xmonad logo to replace the current one. If you want to participate, please submit at most /three/ logos (in SVG format) to [this GitHub Discussion] by the 31st of January. Please do not vote for a logo yet—voting will start after the above deadline. Your logo will need to be licensed under a suitable freely distributable license; for example, the CC BY-SA 4.0. The prize for the winner is `$100'! For voting, we will use an [instant-runoff] type system. In short: • Users rank a minimum of three submissions according to their preferences in decreasing order. • If a logo wins a majority of first-preference votes (> 50%) it is chosen. • If not, we eliminate the logo with the least amount of first preference votes, exposing the second preference of those who voted for it. • Rinse and repeat until we have a majority. • If at the end of all that we still don't have a majority, we will act as a tiebreaker and internally vote for a winner from the remaining logos. We will retain veto power in case of inappropriate logos. Team members whose submitted entries are amongst the remaining choices will not partake in the potential tiebreaking vote. [this GitHub Discussion]: https://github.com/xmonad/xmonad/discussions/343 [instant-runoff]: <https://en.wikipedia.org/wiki/Instant-runoff_voting> 4 Looking for Funding ═════════════════════ TL;DR: We would love your support to keep xmonad alive! You can support us via [GitHub Sponsors] and the [Open Collective] is our fiscal host such that our funds are fully transparent. [GitHub Sponsors]: <https://github.com/sponsors/xmonad> [Open Collective]: <https://opencollective.com/xmonad> XMonad has been around since 2007 and has a great track record in stability. There's an active, vibrant community of users and developers who help each other and contribute fixes and extensions. Keeping this community organized, reviewing and merging contributions and responding to bug reports is almost a full-time job, however, not to mention doing actual development. We've been struggling to find volunteers to do all this work, especially the less exciting bits like documentation. Despite that struggle, we managed to repay a portion of our technological and organizational debt over the last year, and to pick up the [pace of development]. We're worried about the sustainability of that pace, however. As with the previous generations of maintainers, our studies and sabbaticals won't last forever. Your help is needed to keep the project alive and well! We'd like to raise enough funds to enable at least one core developer to work on XMonad full-time (or several part-time). To learn more about our plans for the future, see our [GitHub Sponsors] profile. Thanks to [one unexpected appearance on the Hacker News front page], we already gathered a couple dozen sponsors who donate in total over $300 a month. We're incredibly grateful for this support! Our fiscal host is the [Open Source Collective], so our budget is fully transparent on [our Collective's page]. If you also want to aid our efforts going forward, please consider becoming a supporter as well. We accept both monthly and one-time donations through [GitHub Sponsors] and [Open Collective]. Thank you! [pace of development]: https://xmonad.org/images/xmonad-0-17/commits.svg [GitHub Sponsors]: <https://github.com/sponsors/xmonad> [one unexpected appearance on the Hacker News front page]: <https://news.ycombinator.com/item?id=28793941> [Open Source Collective]: <https://www.oscollective.org/> [our Collective's page]: <https://opencollective.com/xmonad> [Open Collective]: <https://opencollective.com/xmonad>

1 0

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