| 2024-01-14 00:54:31 +0100 | CyberTrekker | (~cybertrek@user/CyberTrekker) |
| 2024-01-14 01:48:29 +0100 | <haskellbridge> | <calx> hi, i have a question, why is `XMonad/Actions/ToggleFullFloat.hs` file not present in the tar release of xmonad-contrib? it is present in the source |
| 2024-01-14 01:49:23 +0100 | <haskellbridge> | <calx> also, how can i use this module on arch? |
| 2024-01-14 01:51:05 +0100 | <geekosaur> | it's not in the most recent release but it is in git and will be in the next release |
| 2024-01-14 01:51:38 +0100 | <geekosaur> | on Arch you may be interested in the xmonad-git package in AUR |
| 2024-01-14 01:56:12 +0100 | <haskellbridge> | <calx> ohh, i see |
| 2024-01-14 01:56:14 +0100 | <haskellbridge> | <calx> thanx |
| 2024-01-14 02:10:13 +0100 | CyberTrekker | (~cybertrek@user/CyberTrekker) (Quit: Leaving) |
| 2024-01-14 04:42:01 +0100 | td_ | (~td@i53870935.versanet.de) (Ping timeout: 245 seconds) |
| 2024-01-14 04:44:01 +0100 | td_ | (~td@i53870903.versanet.de) |
| 2024-01-14 05:51:37 +0100 | tv | (~tv@user/tv) (Ping timeout: 255 seconds) |
| 2024-01-14 06:05:50 +0100 | tv | (~tv@user/tv) |
| 2024-01-14 09:04:31 +0100 | thunderrd | (~thunderrd@183.182.111.140) |
| 2024-01-14 10:25:20 +0100 | Enrico63 | (~Enrico63@81.109.143.226) |
| 2024-01-14 10:28:58 +0100 | <Enrico63> | Hi, I want to use the xmobar.hs approach to make xmobar work with xmonad, and I'm quite there, but at the moment, the thing that doesn't work is that the windows I open end up covering the bar. Additionally, I can't really understand why if I change `StdinReader` to `XMonadLog`, that part of the bar with the workspace numbers doesn't work anymore, |
| 2024-01-14 10:28:59 +0100 | <Enrico63> | in the sense that it doesn't reflect what workspace I'm on. More information, including the minimal xmobar.hs and xmonad.hs that manifest the issue, is at https://stackoverflow.com/questions/77803491/how-do-i-make-xmonad-use-a-haskell-based-xmobar |
| 2024-01-14 10:29:29 +0100 | <Enrico63> | I've not got much feedback there, so I'm asking here. And using that as the pastebin :D |
| 2024-01-14 10:32:17 +0100 | <Solid> | Enrico63: Please refer to the [tutorial](https://xmonad.org/TUTORIAL.html) |
| 2024-01-14 10:45:58 +0100 | <Enrico63> | The tutorial refer to the xmobarrc approach, and refers to other sources for the approach of using xmobar as a library and configuring it via xmobar.hs |
| 2024-01-14 10:47:39 +0100 | <Enrico63> | The tutorial you link to is how I have my working xmobar right now. But I'm experimenting in the attempt of switching to the other approach (mentioned at the beginning and at the end of the "Configuring Xmobar" section at the link you provided) |
| 2024-01-14 10:47:59 +0100 | <Solid> | The only difference is how you start xmobar |
| 2024-01-14 10:49:07 +0100 | <Enrico63> | Well, I guess that's what I'd like to observe too, but there must be something wrong in what I'm doing |
| 2024-01-14 10:51:22 +0100 | <Solid> | If you configure xmonad/xmobar as advised in the tutorial (using XMonadLog, not the pipes approach!) then your minimal example of `main = xmobar defaultConfig { commands = [Run XMonadLog], template = "%XMonadLog%" }` should indeed "just work" (using the resulting executable, I have no experience with doing shenanigans like `xmobar xmobar.hs`, although that should use a process similar to what xmonad does) |
| 2024-01-14 11:15:34 +0100 | <Enrico63> | Ok, I think I've partly understood what is wrong. In going from the approach in the tutorial (xmonad.hs + xmobarrc), call it A, to the other approach (xmonad.hs + xmobar.hs), call it B, I was also removing the usage of `withEasySB` to launch xmobar and just using `spawnPipe`, thinking that with the approach B the configuration of xmobar was all |
| 2024-01-14 11:15:35 +0100 | <Enrico63> | up to xmobar.hs. But apparently I still need to tell xmonad how much space to give to xmobar? Or am I still misunderstanding? |
| 2024-01-14 11:18:40 +0100 | <liskin> | yes you do |
| 2024-01-14 11:19:16 +0100 | <liskin> | I mean, not exactly, you just need to have some bits in xmonad.hs that make it recognize the struts and make the layout avoid them |
| 2024-01-14 11:19:48 +0100 | <liskin> | (some bits being just "avoidStruts" and "docks" these days) |
| 2024-01-14 11:23:20 +0100 | <xmonadtrack> | xmonad-contrib Tomas Janousek * v0.17.1-246-g4bb6a2ee: X.H.EwmhDesktops: Fix haddock markup (3 minutes ago, 1 file, 1+ 1-) https://github.com/xmonad/xmonad-contrib/commit/4bb6a2eedb54 |
| 2024-01-14 11:27:06 +0100 | <Enrico63> | And where do I find an example? Because at the moment I feel my xmonad.hs+xmobar.hs are a bit messy. For instance, in xmonad.hs I have `withEasySB (statusBarProp "xmobar /path/to/xmobar.hs" (pure myXmobarPP)) toggleStrutsKey` with `myXmobarPP` being `def` with some properties overridden, e.g. `ppTitleSanitize = xmobarStrip`, and `toggleStrutsKey` |
| 2024-01-14 11:27:06 +0100 | <Enrico63> | being defined as `toggleStrutsKey XConfig { modMask = m } = (m, xK_b)`. Are these things meant to be in xmonad.hs? |
| 2024-01-14 11:28:45 +0100 | <liskin> | Probably the TUTORIAL mentioned before, and then there's more details in https://xmonad.github.io/xmonad-docs/xmonad-contrib-0.17.1.9/XMonad-Hooks-ManageDocks.html and https://xmonad.github.io/xmonad-docs/xmonad-contrib-0.17.1.9/XMonad-Hooks-StatusBar.html |
| 2024-01-14 11:28:53 +0100 | <liskin> | and yes those things are meant to be there |
| 2024-01-14 11:29:03 +0100 | <liskin> | xmonad-specific bits to be shown in xmobar are formatted by xmonad |
| 2024-01-14 11:29:32 +0100 | <liskin> | xmonad generates markup that xmobar understands and turns into colors and icons and clickable areas and whatever |
| 2024-01-14 11:30:11 +0100 | <liskin> | (gotta go, sry) |
| 2024-01-14 11:30:44 +0100 | <Enrico63> | Thanks! |
| 2024-01-14 12:22:03 +0100 | Enrico63 | (~Enrico63@81.109.143.226) (Quit: Client closed) |
| 2024-01-14 13:14:48 +0100 | mc47 | (~mc47@xmonad/TheMC47) |
| 2024-01-14 15:11:33 +0100 | thunderrd | (~thunderrd@183.182.111.140) (Remote host closed the connection) |
| 2024-01-14 15:26:50 +0100 | guest912 | (~wenzel@dl40mv8f3blcv0qzxl2dy-3.rev.dnainternet.fi) (Quit: Leaving) |
| 2024-01-14 15:37:08 +0100 | guest912 | (~wenzel@dl40mv8f3blcv0qzxl2dy-3.rev.dnainternet.fi) |
| 2024-01-14 15:59:28 +0100 | hightower2 | (~hightower@213.186.15.36) (Ping timeout: 246 seconds) |
| 2024-01-14 16:22:42 +0100 | hightower2 | (~hightower@244-36.dsl.iskon.hr) |
| 2024-01-14 18:33:49 +0100 | td_ | (~td@i53870903.versanet.de) (Ping timeout: 256 seconds) |
| 2024-01-14 18:45:46 +0100 | td_ | (~td@i5387090D.versanet.de) |
| 2024-01-14 19:33:55 +0100 | portnov | (~portnov@v-20678-unlim.vpn.mgn.ru) |
| 2024-01-14 19:54:10 +0100 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2024-01-14 19:54:20 +0100 | portnov | (~portnov@v-20678-unlim.vpn.mgn.ru) (Remote host closed the connection) |
| 2024-01-14 20:18:07 +0100 | Guest59 | (~Guest59@49.148.180.234) |
| 2024-01-14 20:20:14 +0100 | Guest59 | (~Guest59@49.148.180.234) () |
| 2024-01-14 21:31:24 +0100 | guest912 | (~wenzel@dl40mv8f3blcv0qzxl2dy-3.rev.dnainternet.fi) (Quit: Leaving) |
| 2024-01-14 21:32:10 +0100 | guest912 | (~wenzel@dl40mv8f3blcv0qzxl2dy-3.rev.dnainternet.fi) |
| 2024-01-14 21:44:07 +0100 | <guest912> | New windows appearing at the place of currently focused window xmonad by default, can I change this behavior? |
| 2024-01-14 21:44:19 +0100 | <guest912> | So that new windows are appearing *after* currently focused one |
| 2024-01-14 21:45:04 +0100 | <guest912> | If not by an option maybe there’s some way to make a hack. Like a new window hook that would move the new window one step forward in the window stack? |
| 2024-01-14 21:48:21 +0100 | <guest912> | It seems I found a potential solution here https://wiki.haskell.org/Xmonad/Frequently_asked_questions#Make_new_windows_appear_.27below.27_rat… |
| 2024-01-14 21:52:14 +0100 | [Leary] | (~Leary]@user/Leary/x-0910699) (Remote host closed the connection) |
| 2024-01-14 21:55:51 +0100 | <geekosaur> | sounds like you want https://hackage.haskell.org/package/xmonad-contrib-0.17.1/docs/XMonad-Hooks-InsertPosition.html |