| 2023-01-27 00:03:39 +0000 | <scrungus> | https://paste.tomsmeding.com/ghE9cgri |
| 2023-01-27 00:04:00 +0000 | <scrungus> | This is my xmonad.hs and xinitrc |
| 2023-01-27 00:04:28 +0000 | <scrungus> | Sorry if I just did something really dumb and didn't realize :p |
| 2023-01-27 00:08:09 +0000 | <geekosaur> | looks fine to me including the xrandr settings (weird things can happen if you get the screen offsets wrong) |
| 2023-01-27 00:08:37 +0000 | <geekosaur> | I had been wondering f you perhaps XMonad.Actions.Warp set up and possibly misconfigured |
| 2023-01-27 00:09:07 +0000 | <scrungus> | I don't know what that is so I don't think so. I hadn't really started configuring much yet since I wanted to get this sorted out first |
| 2023-01-27 00:09:40 +0000 | <scrungus> | I've just been troubleshooting. |
| 2023-01-27 00:10:19 +0000 | <scrungus> | I actually used arandr to generate my xrandr config so I might try doing it manually to make sure it wasn't doing thing wrong in a way that I didn't realise |
| 2023-01-27 00:11:49 +0000 | <scrungus> | I thought I would check here to see if it was a problem other people had ran into before. I'm guessing it has to be xrandr or something else sending slightly weird values for my monitors to xmonad that's confusing it |
| 2023-01-27 00:12:35 +0000 | <geekosaur> | I think you'd have to have overlapping values for it to do that, but I checked the xrandr config and it's not overlapping |
| 2023-01-27 00:13:56 +0000 | <geekosaur> | arandr shouldn't be capable of outputting overlapping or gapped xrandr configurations anyway; I'd have recommended using it if you had written the xrandr config yourself |
| 2023-01-27 00:14:25 +0000 | <scrungus> | Yeah that's true. I probably took the less error-prone path already in that regard |
| 2023-01-27 00:15:04 +0000 | <scrungus> | I might try unplugging some of my monitors at a time to see if I can diagnose anything else about the issue.The weird thing is how it seems to work fine when they're out of order. By which I mean how xmonad behaves is how I would expect |
| 2023-01-27 00:15:20 +0000 | <geekosaur> | hrm |
| 2023-01-27 00:15:40 +0000 | <geekosaur> | that sounds like we missed a rescreen somehow |
| 2023-01-27 00:15:50 +0000 | <geekosaur> | does mod-n do anything? |
| 2023-01-27 00:16:14 +0000 | <scrungus> | No it doesn't |
| 2023-01-27 00:16:24 +0000 | <scrungus> | What is it supposed to do? I'm not super familiar with the keybindings |
| 2023-01-27 00:16:30 +0000 | <geekosaur> | …wait, we can't have missed it, you rearrange the screens before starting xmonad and we should get the current xrandr setup |
| 2023-01-27 00:16:36 +0000 | <geekosaur> | it does a forced rescreen |
| 2023-01-27 00:16:39 +0000 | <scrungus> | Oh I see |
| 2023-01-27 00:17:27 +0000 | <scrungus> | Yeah that's the weird part. It really seems like xmonad is still partially relying on the old default value or something but that shouldn't be possible |
| 2023-01-27 00:17:40 +0000 | <scrungus> | And I've just been using startx |
| 2023-01-27 00:17:49 +0000 | <geekosaur> | unless the video driver is doing something screwy, which has been known to happen |
| 2023-01-27 00:18:01 +0000 | <scrungus> | That's possible. |
| 2023-01-27 00:18:17 +0000 | <geekosaur> | okay, if you used stack to set up xmonad, run `stack ghci`. otherwise, run `ghci` |
| 2023-01-27 00:18:32 +0000 | <scrungus> | Okay |
| 2023-01-27 00:18:40 +0000 | <geekosaur> | at the prompt, enter: openDisplay "" >>= getCleanedScreenInfo |
| 2023-01-27 00:19:24 +0000 | <geekosaur> | this should print a list of rectangles |
| 2023-01-27 00:19:46 +0000 | <scrungus> | Hm, "variable not in scope" |
| 2023-01-27 00:19:56 +0000 | <scrungus> | That's probably not good :p |
| 2023-01-27 00:20:04 +0000 | <geekosaur> | hm. are you in your xmonad config directory? |
| 2023-01-27 00:20:37 +0000 | <geekosaur> | you'll need to be for this to work |
| 2023-01-27 00:20:58 +0000 | <scrungus> | Okay I wasn't but I switched to it and it's saying the same thing |
| 2023-01-27 00:21:00 +0000 | <geekosaur> | it's possible you need to do `import XMonad` first |
| 2023-01-27 00:21:05 +0000 | <scrungus> | Oh probably |
| 2023-01-27 00:21:13 +0000 | <scrungus> | So those are xmonad functions right? |
| 2023-01-27 00:21:29 +0000 | <scrungus> | Okay it worked |
| 2023-01-27 00:21:55 +0000 | <scrungus> | ghci> openDisplay "" >>= getCleanedScreenInfo |
| 2023-01-27 00:21:56 +0000 | <scrungus> | [Rectangle {rect_x = 3840, rect_y = 0, rect_width = 1920, rect_height = 1080},Rectangle {rect_x = 1920, rect_y = 0, rect_width = 1920, rect_height = 1080},Rectangle {rect_x = 0, rect_y = 0, rect_width = 1920, rect_height = 1080}] |
| 2023-01-27 00:21:56 +0000 | <scrungus> | ghci> |
| 2023-01-27 00:22:01 +0000 | <geekosaur> | okay, so the rectangles in order should reflect what you have in the xrandr command |
| 2023-01-27 00:22:53 +0000 | <scrungus> | What is "rect_x = 3840" referring to? |
| 2023-01-27 00:23:36 +0000 | <geekosaur> | the "x" part of the `--pos` parameter, which is `x`x`y` |
| 2023-01-27 00:24:46 +0000 | <scrungus> | I guess tit's not the same order |
| 2023-01-27 00:24:50 +0000 | <scrungus> | it's* |
| 2023-01-27 00:24:56 +0000 | <geekosaur> | looks to me like the rectangles are sorted by reverse x offset |
| 2023-01-27 00:25:07 +0000 | <geekosaur> | which is odd |
| 2023-01-27 00:25:42 +0000 | <scrungus> | Why would that happen then? |
| 2023-01-27 00:26:34 +0000 | <geekosaur> | that's almost always the video driver's fault; it's supposed to report them in xrandr order |
| 2023-01-27 00:26:48 +0000 | <scrungus> | So I should look into my video drivers? |
| 2023-01-27 00:27:04 +0000 | <geekosaur> | https://wiki.haskell.org/Xmonad/Frequently_asked_questions#Screens_are_in_wrong_order might help, although it's a bit of work and won't help with the mouse. the PhysicalScreens module might work better here |
| 2023-01-27 00:27:24 +0000 | <geekosaur> | it sounds like it, yes |
| 2023-01-27 00:27:36 +0000 | <scrungus> | Would the physical screens module be able negate this issue you think? |
| 2023-01-27 00:28:26 +0000 | <geekosaur> | it lets you rearrange the screen rectangles as xmonad sees them, instead of just remapping the screen-focusing keys like the first link I gave you. so it should work |
| 2023-01-27 00:29:19 +0000 | <scrungus> | Well thank you so much for helping me out! |
| 2023-01-27 00:29:28 +0000 | <scrungus> | I'm always worried about being annoying when I ask for help with stuff |
| 2023-01-27 00:29:44 +0000 | <geekosaur> | no problem, it's what we're here for |
| 2023-01-27 00:31:06 +0000 | <scrungus> | My path here was actually that I started learning Haskell and I found out about xmonad and I was kind of surprised and wanted to use it. I've used tiling WMs before but not a dynamic one so it's been interesting |
| 2023-01-27 00:34:48 +0000 | scrungus | (~scrungus@bras-base-aurron9127w-grc-54-70-24-71-72.dsl.bell.ca) (Quit: Client closed) |
| 2023-01-27 00:54:34 +0000 | td_ | (~td@i53870925.versanet.de) (Ping timeout: 260 seconds) |
| 2023-01-27 00:56:06 +0000 | td_ | (~td@i53870931.versanet.de) |
| 2023-01-27 00:57:16 +0000 | yaslam | (~yaslam@user/yaslam) |
| 2023-01-27 00:57:36 +0000 | yaslam | (~yaslam@user/yaslam) () |
| 2023-01-27 03:02:55 +0000 | banc | (banc@gateway/vpn/protonvpn/banc) (Ping timeout: 248 seconds) |
| 2023-01-27 03:18:04 +0000 | td_ | (~td@i53870931.versanet.de) (Ping timeout: 260 seconds) |
| 2023-01-27 03:19:35 +0000 | td_ | (~td@i53870938.versanet.de) |
| 2023-01-27 03:24:23 +0000 | banc | (banc@gateway/vpn/protonvpn/banc) |
| 2023-01-27 03:33:56 +0000 | ghormoon | (~ghormoon@ghorland.net) (Ping timeout: 268 seconds) |
| 2023-01-27 04:02:54 +0000 | ghormoon | (~ghormoon@ghorland.net) |
| 2023-01-27 06:27:55 +0000 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 252 seconds) |
| 2023-01-27 07:24:34 +0000 | qbt | (~qbt@user/edun) |
| 2023-01-27 08:40:17 +0000 | ft | (~ft@p4fc2a257.dip0.t-ipconnect.de) (Quit: leaving) |
| 2023-01-27 09:25:03 +0000 | scardinal | (~supreme@customer-212-237-101-39.ip4.gigabit.dk) (Ping timeout: 252 seconds) |
| 2023-01-27 09:30:37 +0000 | scardinal | (~supreme@customer-212-237-101-39.ip4.gigabit.dk) |
| 2023-01-27 11:10:23 +0000 | qbt | (~qbt@user/edun) (Ping timeout: 248 seconds) |
| 2023-01-27 12:57:50 +0000 | qbt | (~qbt@user/edun) |
| 2023-01-27 13:00:35 +0000 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2023-01-27 14:26:42 +0000 | telser_ | (~quassel@user/telser) |
| 2023-01-27 14:27:12 +0000 | telser | (~quassel@user/telser) (Ping timeout: 248 seconds) |
| 2023-01-27 14:54:26 +0000 | ft | (~ft@p4fc2a257.dip0.t-ipconnect.de) |
| 2023-01-27 16:00:04 +0000 | uhoreg | (~uhoreg@2001:470:69fc:105::35f) (Quit: You have been kicked for being idle) |
| 2023-01-27 16:00:08 +0000 | unclechu | (~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle) |
| 2023-01-27 16:05:30 +0000 | fjMSX | (~hypni2p@89-179-32-81.broadband.corbina.ru) (Quit: Уш'лЪЬ їз єтой IRC сетї) |
| 2023-01-27 16:15:52 +0000 | ml| | (~ml|@user/ml/x-5298235) (Quit: WeeChat 3.6) |
| 2023-01-27 16:32:10 +0000 | ml| | (~ml|@user/ml/x-5298235) |
| 2023-01-27 16:32:46 +0000 | ml| | (~ml|@user/ml/x-5298235) (Client Quit) |
| 2023-01-27 17:12:43 +0000 | ectospasm | (~ectospasm@user/ectospasm) (Ping timeout: 248 seconds) |
| 2023-01-27 17:16:10 +0000 | ectospasm | (~ectospasm@user/ectospasm) |
| 2023-01-27 17:46:04 +0000 | qbt | (~qbt@user/edun) (Ping timeout: 252 seconds) |
| 2023-01-27 19:35:28 +0000 | tremon | (~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl) |
| 2023-01-27 19:46:44 +0000 | <xmonadtrack> | New xmonad-contrib branch created: pull/796 (1 commit) https://github.com/xmonad/xmonad-contrib/pull/796 |
| 2023-01-27 19:46:59 +0000 | unclechu | (~unclechu@2001:470:69fc:105::354) |
| 2023-01-27 20:21:52 +0000 | telser_ | (~quassel@user/telser) (Ping timeout: 248 seconds) |
| 2023-01-27 20:22:22 +0000 | telser | (~quassel@user/telser) |
| 2023-01-27 20:54:28 +0000 | tremon | (~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl) (Quit: getting boxed in) |