| 2023-01-25 00:00:26 +0100 | <georgesboris[m]> | hello folks :) I'm a nix+xmonad+linux noob -- but everything was working correctly until I decided to plug in an additional monitor with a different resolution (don't know if that is important or not tbh) |
| 2023-01-25 00:01:07 +0100 | <georgesboris[m]> | my xmonad is getting reeeally funky when I try to make things work. I think it is a mix of not wrapping my head around xmonad's multiple monitors logic yet but also something wrong with my setup. |
| 2023-01-25 00:01:39 +0100 | <georgesboris[m]> | I was wondering if someone was using a similar set up that could possibly share some light? :) |
| 2023-01-25 00:01:39 +0100 | <georgesboris[m]> | s/nix/nixos/ |
| 2023-01-25 00:02:14 +0100 | <georgesboris[m]> | for instance, even when I do make my second monitor "useful", xmonad renders the background on top of some windows when I'm focusing on the other monitor. it is just really confusing. |
| 2023-01-25 00:02:33 +0100 | <geekosaur> | xmonad should handle it about as well as X11 can, although it also depends on video driver |
| 2023-01-25 00:02:47 +0100 | <geekosaur> | and something like that sounds like video driver (or compositor) |
| 2023-01-25 00:02:50 +0100 | <georgesboris[m]> | I'm researching stuff about xrandr, autorandr, xmonad, arandr, ... it is a bit too much 😅 |
| 2023-01-25 00:03:09 +0100 | <geekosaur> | hm, actually that'd be really weird for a compositor too |
| 2023-01-25 00:03:10 +0100 | <georgesboris[m]> | as I'm using picom |
| 2023-01-25 00:03:11 +0100 | <georgesboris[m]> | oh... compositor might be something |
| 2023-01-25 00:03:40 +0100 | <geekosaur> | if you kill it, do things improve? (I was actually about to sugggest running one to see if it helped) |
| 2023-01-25 00:04:09 +0100 | <georgesboris[m]> | however, I also think my xrandr setup by itself is just not properly set... which might be causing all of this. but just using arandr doesn't solve things as well... seems like the different resolutions are not dealt with very well. |
| 2023-01-25 00:04:16 +0100 | <georgesboris[m]> | kill the compositor you mean? |
| 2023-01-25 00:04:38 +0100 | <geekosaur> | I personally have had weirrdness like that when connecting a monitor while X was running, but it's entirely independent of window manager or compositor in my case, it's something about the video driver and/or Intel video |
| 2023-01-25 00:04:48 +0100 | <geekosaur> | yes |
| 2023-01-25 00:05:17 +0100 | <georgesboris[m]> | yeah... didn't help. |
| 2023-01-25 00:05:34 +0100 | <georgesboris[m]> | do you also use nixos? |
| 2023-01-25 00:06:00 +0100 | <geekosaur> | nope, debian |
| 2023-01-25 00:06:05 +0100 | <geekosaur> | er, ubuntu |
| 2023-01-25 00:06:10 +0100 | <georgesboris[m]> | I feel like the whole declarative + immutable setup doesn't help either in this case. as things might be running in an unexpected order and I'm trying not to rely on temporary system state. |
| 2023-01-25 00:08:33 +0100 | <geekosaur> | order shouldn't matter aside from the X server needing to be running before you start a window manager, compositor, etc. |
| 2023-01-25 00:08:48 +0100 | <geekosaur> | but they'd just error out in that case, not draw strangely |
| 2023-01-25 00:11:33 +0100 | <georgesboris[m]> | when you specify different resolutions using xrandr do you need to match the different resolutions to the same virtual screen or does it handle that automatically? for instance having a 1440p to the side of a 1080p monitor |
| 2023-01-25 00:11:52 +0100 | <georgesboris[m]> | sorry for the off-topic direction 😅 but I feel this might be related. |
| 2023-01-25 00:12:01 +0100 | <geekosaur> | it handles it automatically |
| 2023-01-25 00:18:35 +0100 | <geekosaur> | to explain a little: window managers do no drawing, they're about window placement policy |
| 2023-01-25 00:18:51 +0100 | <geekosaur> | compositors, if running, specify what to draw |
| 2023-01-25 00:19:22 +0100 | <geekosaur> | the X server does the actual drawing, by passing it on to the video driver according to window visibility |
| 2023-01-25 00:21:08 +0100 | <geekosaur> | xrandr tells the X server and thereby the video driver the size, position, and orientation of displays, but shouldn't affect how windows are drawn beyond specifying what counts as "on screen" |
| 2023-01-25 00:22:48 +0100 | <liskin> | georgesboris[m]: if you just do "xrandr --output NAME --auto --output NAME2 --auto --right-of NAME" and you get weird stuff then… probably take a photo and post it because weird stuff isn't expected |
| 2023-01-25 01:01:03 +0100 | <georgesboris[m]> | yeah... I just run that and it's the best I've ever gotten but it is still weird. I'll do a deep dive into how xmonad deals with multi monitors because that is at least part of the weirdness. |
| 2023-01-25 01:01:33 +0100 | <georgesboris[m]> | however, I've also noticed that the wallpaper on one of the monitors is being drawn on top of unfocused windows. |
| 2023-01-25 01:02:24 +0100 | <georgesboris[m]> | kinda of like xmonad is just reordering the z-axis of windows to make them appear or not but since my wallpaper is not the right ratio as the new monitor. |
| 2023-01-25 01:02:37 +0100 | <georgesboris[m]> | thanks for the help! I will get there! one day... |
| 2023-01-25 01:33:15 +0100 | td_ | (~td@i53870917.versanet.de) (Ping timeout: 255 seconds) |
| 2023-01-25 01:35:05 +0100 | td_ | (~td@i53870917.versanet.de) |
| 2023-01-25 01:41:40 +0100 | Lears | (~Leary]@user/Leary/x-0910699) (Remote host closed the connection) |
| 2023-01-25 01:42:23 +0100 | [Leary] | (~Leary]@user/Leary/x-0910699) |
| 2023-01-25 02:55:20 +0100 | sugarbeet | (~barbas@2a00:d880:3:1::df17:eb0c) |
| 2023-01-25 02:55:24 +0100 | sugarbeet | (~barbas@2a00:d880:3:1::df17:eb0c) () |
| 2023-01-25 04:02:59 +0100 | banc | (banc@gateway/vpn/protonvpn/banc) (Ping timeout: 260 seconds) |
| 2023-01-25 04:14:11 +0100 | <HB[m]> | Hi guys. What dimensions do I provide namedscratchpad to make it fullscreen? |
| 2023-01-25 04:14:31 +0100 | <HB[m]> | `(noTaskbar <> customFloating (W.RationalRect (1/30) (1/30) (9/10) (9/10)))` This was my current setting |
| 2023-01-25 04:15:00 +0100 | <HB[m]> | I also tried defaultFloating but that's not fullscreen apparently |
| 2023-01-25 04:15:02 +0100 | <[Leary]> | 0 0 1 1? Probably. |
| 2023-01-25 04:15:24 +0100 | <HB[m]> | -- 1/6 of screen width from the left, 1/6 of screen height |
| 2023-01-25 04:15:24 +0100 | <HB[m]> | -- from the top, 2/3 of screen width by 2/3 of screen height |
| 2023-01-25 04:15:31 +0100 | <HB[m]> | Hi |
| 2023-01-25 04:15:46 +0100 | <HB[m]> | How exactly are these dimensions specified? Does it have to be fractions? |
| 2023-01-25 04:17:31 +0100 | <HB[m]> | [Leary]: I see, thanks! |
| 2023-01-25 04:17:47 +0100 | <[Leary]> | > [0, 1, 1/2, 0.5] :: [Rational] |
| 2023-01-25 04:17:49 +0100 | <lambdabot> | [0 % 1,1 % 1,1 % 2,1 % 2] |
| 2023-01-25 04:17:59 +0100 | <HB[m]> | I see |
| 2023-01-25 04:18:02 +0100 | <[Leary]> | They print funny, but you can write `Rational`s like any other number. |
| 2023-01-25 04:18:14 +0100 | <HB[m]> | It takes over the panels, though. |
| 2023-01-25 04:18:39 +0100 | <HB[m]> | * panels, though. Is there a way to prevent it from doing that? I'd like the kde panels and xmobar etc. to remain visible. |
| 2023-01-25 04:24:30 +0100 | banc | (banc@gateway/vpn/protonvpn/banc) |
| 2023-01-25 04:25:56 +0100 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2023-01-25 04:29:14 +0100 | <HB[m]> | I guess I'll have to resize it somehow to be between the top and bottom panels. |
| 2023-01-25 04:30:15 +0100 | <[Leary]> | HB[m]: I'm not that familiar with bars/struts, but it looks like you can hack something up with `X.H.ManageDocks.calcGap`. |
| 2023-01-25 04:47:54 +0100 | td_ | (~td@i53870917.versanet.de) (Ping timeout: 260 seconds) |
| 2023-01-25 04:49:24 +0100 | td_ | (~td@i53870930.versanet.de) |
| 2023-01-25 04:54:34 +0100 | <[Leary]> | HB[m]: I took a stab at it: https://gist.github.com/LSLeary/72add95f8bbc16c9362d85dd8680cba5 |
| 2023-01-25 05:07:07 +0100 | rundown | (~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) (Ping timeout: 248 seconds) |
| 2023-01-25 05:25:55 +0100 | <HB[m]> | Oh wow, thank you so much! |
| 2023-01-25 05:26:07 +0100 | <HB[m]> | Let me try to make sense out of this one |
| 2023-01-25 05:28:49 +0100 | HB[m] | sent a haskell code block: https://libera.ems.host/_matrix/media/v3/download/libera.chat/a88631105ff9c0e5204afba1aefffcfbb2c9… |
| 2023-01-25 05:31:19 +0100 | <HB[m]> | So first define a function called strutlessRR, takes set Diretion2D and produces X rationalrect |
| 2023-01-25 05:32:07 +0100 | <HB[m]> | then do |
| 2023-01-25 05:32:07 +0100 | <HB[m]> | calculate Gap and haskell sytnax is so alien to me always. I gotta look up arrow |
| 2023-01-25 05:36:49 +0100 | <HB[m]> | * Then run calcGap and put it into ds (or calc) |
| 2023-01-25 05:36:49 +0100 | <HB[m]> | Then SD rect gets screen detail from current screen in the current window set |
| 2023-01-25 05:36:49 +0100 | <HB[m]> | Then calc rectangle |
| 2023-01-25 05:36:49 +0100 | <HB[m]> | Then strutless floating function, and passin the strutlessRR function into the customFloating |
| 2023-01-25 05:37:01 +0100 | <HB[m]> | I gotta learn haskell one day, after exams. |
| 2023-01-25 05:37:48 +0100 | <HB[m]> | `(W.RationalRect 0 (18/1080) 1 (1041/1080)))` BTW, I was also able to do this. |
| 2023-01-25 05:37:48 +0100 | <HB[m]> | I figured specify actual pixel specific positioning for my mysetup |
| 2023-01-25 07:34:57 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 256 seconds) |
| 2023-01-25 07:41:45 +0100 | banc | (banc@gateway/vpn/protonvpn/banc) (Ping timeout: 256 seconds) |
| 2023-01-25 07:49:54 +0100 | <xmonadtrack> | xmonad-contrib Tony Zorman * v0.17.1-125-g49904ec4: X.U.NamedScratchpad: Fix typo in exclusive docs (89 seconds ago, 1 file, 4+ 3-) https://github.com/xmonad/xmonad-contrib/commit/49904ec4d3a7 |
| 2023-01-25 08:55:51 +0100 | banc | (banc@gateway/vpn/protonvpn/banc) |
| 2023-01-25 09:00:05 +0100 | mc47 | (~mc47@xmonad/TheMC47) |
| 2023-01-25 10:04:17 +0100 | ft | (~ft@p4fc2a257.dip0.t-ipconnect.de) (Quit: leaving) |
| 2023-01-25 11:44:30 +0100 | rundown | (~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) |
| 2023-01-25 12:16:22 +0100 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2023-01-25 13:08:13 +0100 | mc47 | (~mc47@xmonad/TheMC47) |
| 2023-01-25 13:14:47 +0100 | qbt | (~qbt@user/edun) |
| 2023-01-25 13:17:14 +0100 | qbt | (~qbt@user/edun) (Client Quit) |
| 2023-01-25 13:17:29 +0100 | qbt | (~qbt@user/edun) |
| 2023-01-25 13:17:50 +0100 | qbt | (~qbt@user/edun) (Client Quit) |
| 2023-01-25 13:18:05 +0100 | qbt | (~qbt@user/edun) |
| 2023-01-25 13:22:34 +0100 | qbt | (~qbt@user/edun) (Client Quit) |
| 2023-01-25 13:22:50 +0100 | qbt | (~qbt@user/edun) |
| 2023-01-25 13:25:25 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2023-01-25 14:15:19 +0100 | <T_X> | is there a way to convert a KeySym to a KeyMask? I'm thinking about only using the left Alt key instead of both Alt + AltGr, if that's possible |
| 2023-01-25 14:16:24 +0100 | <T_X> | (and hoogle seems to fail me, unless I'm overlooking something: https://hoogle.haskell.org/?q=words&hoogle=KeySym%20-%3E%20KeyMask) |
| 2023-01-25 14:22:42 +0100 | thyriaen | (~thyriaen@2a01:aea0:dd4:4fa4:6245:cbff:fe9f:48b1) |
| 2023-01-25 14:23:19 +0100 | <thyriaen> | Could you do something to reach out to fedora from a xmonad dev point of view and ask for inclusion of xmonad-0.17.1 in fedora38 ? |
| 2023-01-25 14:27:11 +0100 | <thyriaen> | otherwise i don't know how to get the newest version running on f36/f37 |
| 2023-01-25 14:38:41 +0100 | <[Leary]> | T_X: That's a matter of keyboard (xkb or xmodmap) configuration. You want to exclude AltGr from the modifier mask it shares with Alt. |
| 2023-01-25 14:50:31 +0100 | <T_X> | [Leary]: ok, thanks! was hoping to avoid that, but will do that with xmodmap then, I guess. would be nice, if ~/.config/xkb/symbols/... worked on X11, too and not only on Wayland :) |
| 2023-01-25 14:58:11 +0100 | <T_X> | hm, I get a strange error with xmodmap though: https://paste.linuxlounge.net/54 |
| 2023-01-25 15:06:49 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 252 seconds) |
| 2023-01-25 15:19:55 +0100 | <geekosaur> | T_X, I think it's just that the xkb stuff in X11 was never updated to use XDG paths. |
| 2023-01-25 15:20:17 +0100 | <geekosaur> | The dotfiles for X11 xkb just go right in ~ |
| 2023-01-25 16:52:42 +0100 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2023-01-25 17:00:06 +0100 | unclechu | (~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle) |
| 2023-01-25 17:42:33 +0100 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Remote host closed the connection) |
| 2023-01-25 17:58:55 +0100 | <thyriaen> | how can i install xmonad in a different way other than from my distro ? |
| 2023-01-25 17:59:10 +0100 | unclechu | (~unclechu@2001:470:69fc:105::354) |
| 2023-01-25 18:01:57 +0100 | <geekosaur> | https://xmonad.org/INSTALL.html#download-xmonad-sources |
| 2023-01-25 18:02:10 +0100 | <thyriaen> | should i use stack ? |
| 2023-01-25 18:02:15 +0100 | <thyriaen> | or cabal ? |
| 2023-01-25 18:02:29 +0100 | <geekosaur> | stack vs., cabal is up to you; the installation guide explains both |
| 2023-01-25 18:02:42 +0100 | <thyriaen> | i don't know what the difference is |
| 2023-01-25 18:02:54 +0100 | <geekosaur> | I personally use cabal, but I think the other maintainers all use stack |
| 2023-01-25 18:03:12 +0100 | <thyriaen> | ok |
| 2023-01-25 18:03:46 +0100 | <geekosaur> | they're pretty much the same if you're working from git. they differ more if you use xmonad from stackage (stack) or hackage (cabal) |
| 2023-01-25 18:04:37 +0100 | <geekosaur> | stack believes in curated sets of packages which may be somewhat out of date but are tested to work together; cabal works with the most recent compatible packages on hackage directly |
| 2023-01-25 18:10:47 +0100 | <thyriaen> | geekosaur, ah but both can be used with git so then it doesn't matter ? |
| 2023-01-25 18:11:00 +0100 | <geekosaur> | right |
| 2023-01-25 18:11:06 +0100 | <thyriaen> | i understand thanks |
| 2023-01-25 18:11:08 +0100 | <thyriaen> | i will try |
| 2023-01-25 18:11:47 +0100 | <geekosaur> | either by cloning it locally or by pointing it to a git refspec via `stack.yaml` / `cabal.project` |
| 2023-01-25 18:11:59 +0100 | <thyriaen> | the guide clones it |
| 2023-01-25 18:12:12 +0100 | <geekosaur> | yes, I saw. |
| 2023-01-25 18:12:48 +0100 | <geekosaur> | I clone it locally as well, but I',m a developer so I may be testing stuff on a branch that I'll eventually push and make a PR from |
| 2023-01-25 18:14:34 +0100 | <geekosaur> | there's also an option not shown there: if you don't want to track git but want the latest release version, you can use minimally configured stack/cabal to get the most recent release from stackage/hackage |
| 2023-01-25 18:20:29 +0100 | qbt | (~qbt@user/edun) (Ping timeout: 260 seconds) |
| 2023-01-25 18:43:28 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2023-01-25 18:44:26 +0100 | jeeeun | (~jeeeun@78.40.148.178) (Quit: The Lounge - https://thelounge.chat) |
| 2023-01-25 18:45:44 +0100 | jeeeun | (~jeeeun@78.40.148.178) |
| 2023-01-25 19:13:54 +0100 | qbt | (~qbt@user/edun) |
| 2023-01-25 19:17:12 +0100 | jeeeun | (~jeeeun@78.40.148.178) (Quit: The Lounge - https://thelounge.chat) |
| 2023-01-25 19:20:32 +0100 | jeeeun | (~jeeeun@78.40.148.178) |
| 2023-01-25 19:31:08 +0100 | tv | (~tv@user/tv) (Quit: derp) |
| 2023-01-25 19:31:35 +0100 | tv | (~tv@user/tv) |
| 2023-01-25 19:44:26 +0100 | hrberg | (~quassel@171.79-160-161.customer.lyse.net) (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) |
| 2023-01-25 19:47:34 +0100 | hrberg | (~quassel@171.79-160-161.customer.lyse.net) |
| 2023-01-25 19:50:25 +0100 | <thyriaen> | geekosaur, that would be ideal - is there a guide you can point me to where this is explained ? |
| 2023-01-25 19:51:22 +0100 | <geekosaur> | just put dependencies in your cabal file and stack or cabal will fetch them |
| 2023-01-25 19:51:39 +0100 | <geekosaur> | you still need a stack.yaml but it'll only specify a resolver |
| 2023-01-25 19:51:53 +0100 | <thyriaen> | geekosaur, i have no experience with cabal |
| 2023-01-25 19:55:46 +0100 | <geekosaur> | https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad-bsa.cabal but you won't need unix, dbus, or utf8-string (I need those because my xmonad config talks over dbus to mate-panel) |
| 2023-01-25 19:56:30 +0100 | <geekosaur> | although this is a more complete cabal config than the INSTALL.html uses, partly because of the dbus stuff and partly so HLS works with my xmonad config |
| 2023-01-25 19:57:23 +0100 | <geekosaur> | if you use this directly you'll need a build script (https://github.com/geekosaur/xmonad.hs/blob/skkukuk/build) |
| 2023-01-25 19:58:38 +0100 | rundown | (~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) (Ping timeout: 246 seconds) |
| 2023-01-25 20:02:07 +0100 | ft | (~ft@p4fc2a257.dip0.t-ipconnect.de) |
| 2023-01-25 20:09:03 +0100 | <geekosaur> | hm, actually INSTALL.html says how to do this simply without actually saying so. skip the git checkout and skip creating `cabal.project` |
| 2023-01-25 20:09:36 +0100 | <geekosaur> | start at "Install everything" |
| 2023-01-25 20:10:30 +0100 | <geekosaur> | then you don't need the build script or cabal file (the package-env options do what's needed for it to find them) |
| 2023-01-25 20:15:49 +0100 | zxrenpbjr[m] | (~zxrenpbjr@2001:470:69fc:105::2:fce6) |
| 2023-01-25 21:01:35 +0100 | qbt | (~qbt@user/edun) (Ping timeout: 260 seconds) |
| 2023-01-25 21:02:07 +0100 | telser | (~quassel@user/telser) (Ping timeout: 252 seconds) |
| 2023-01-25 21:03:16 +0100 | telser | (~quassel@user/telser) |
| 2023-01-25 21:03:26 +0100 | <xmonadtrack> | xmonad-contrib Tony Zorman * v0.17.1-123-g0afbbf91: X.U.EZConfig: Add remapKeysP (5 days ago, 2 files, 40+ 0-) https://github.com/xmonad/xmonad-contrib/commit/0afbbf9129cc |
| 2023-01-25 21:03:26 +0100 | <xmonadtrack> | xmonad-contrib Tony Zorman {GitHub} * v0.17.1-127-g33c1e242: Merge pull request #794 from slotThe/ezconfig/remapkeysp (31 seconds ago, 0 files, 0+ 0-) https://github.com/xmonad/xmonad-contrib/commit/33c1e242881e |
| 2023-01-25 21:08:45 +0100 | <geekosaur> | wrt that, how would people feel about changing xmonad's key mapping stuff to use `data Keymap = Submap (Maybe String) (Map (KeyMask,KeySym) Keymap) | Action (Maybe String) (X ())` (or maybe factor the `Maybe String` out) |
| 2023-01-25 21:08:56 +0100 | <geekosaur> | after xmonad 1.0 |
| 2023-01-25 21:10:43 +0100 | <geekosaur> | the Maybe String would allow mod-shift-/ to show the actual keymap with optional key grouping |
| 2023-01-25 21:12:55 +0100 | <geekosaur> | (just spitballing right now) |
| 2023-01-25 21:32:24 +0100 | telser | (~quassel@user/telser) (Ping timeout: 260 seconds) |
| 2023-01-25 21:32:28 +0100 | telser_ | (~quassel@user/telser) |
| 2023-01-25 22:18:27 +0100 | Forkk_ | (~forkk@li926-228.members.linode.com) (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) |
| 2023-01-25 22:18:55 +0100 | Forkk | (~forkk@li926-228.members.linode.com) |
| 2023-01-25 22:43:00 +0100 | rundown | (~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) |
| 2023-01-25 23:00:47 +0100 | <liskin> | what's the benefit of having that in the core rather than a contrib module that tells core the raw mappings? |
| 2023-01-25 23:03:54 +0100 | thyriaen | (~thyriaen@2a01:aea0:dd4:4fa4:6245:cbff:fe9f:48b1) (Remote host closed the connection) |
| 2023-01-25 23:12:01 +0100 | <geekosaur> | the problems with handling `Submap`s when combining `remapKeysP` with `additionalKeysP`, or with remapping something in a `Submap` |
| 2023-01-25 23:12:26 +0100 | <geekosaur> | see discussion in the `remapKeysP` PR |
| 2023-01-25 23:43:00 +0100 | habib | (~habib@78-110-166-168.as42831.net) |