Home liberachat/#xmonad: Logs Calendar

Logs on 2023-01-27 (liberachat/#xmonad)

00:03:39 <scrungus> https://paste.tomsmeding.com/ghE9cgri
00:04:00 <scrungus> This is my xmonad.hs and xinitrc
00:04:28 <scrungus> Sorry if I just did something really dumb and didn't realize :p
00:08:09 <geekosaur> looks fine to me including the xrandr settings (weird things can happen if you get the screen offsets wrong)
00:08:37 <geekosaur> I had been wondering f you perhaps XMonad.Actions.Warp set up and possibly misconfigured
00:09:07 <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
00:09:40 <scrungus> I've just been troubleshooting.
00:10:19 <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
00:11:49 <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
00:12:35 <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
00:13:56 <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
00:14:25 <scrungus> Yeah that's true. I probably took the less error-prone path already in that regard
00:15:04 <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
00:15:20 <geekosaur> hrm
00:15:40 <geekosaur> that sounds like we missed a rescreen somehow
00:15:50 <geekosaur> does mod-n do anything?
00:16:14 <scrungus> No it doesn't
00:16:24 <scrungus> What is it supposed to do? I'm not super familiar with the keybindings
00:16:30 <geekosaur> …wait, we can't have missed it, you rearrange the screens before starting xmonad and we should get the current xrandr setup
00:16:36 <geekosaur> it does a forced rescreen
00:16:39 <scrungus> Oh I see
00:17:27 <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
00:17:40 <scrungus> And I've just been using startx
00:17:49 <geekosaur> unless the video driver is doing something screwy, which has been known to happen
00:18:01 <scrungus> That's possible.
00:18:17 <geekosaur> okay, if you used stack to set up xmonad, run `stack ghci`. otherwise, run `ghci`
00:18:32 <scrungus> Okay
00:18:40 <geekosaur> at the prompt, enter: openDisplay "" >>= getCleanedScreenInfo
00:19:24 <geekosaur> this should print a list of rectangles
00:19:46 <scrungus> Hm, "variable not in scope"
00:19:56 <scrungus> That's probably not good :p
00:20:04 <geekosaur> hm. are you in your xmonad config directory?
00:20:37 <geekosaur> you'll need to be for this to work
00:20:58 <scrungus> Okay I wasn't but I switched to it and it's saying the same thing
00:21:00 <geekosaur> it's possible you need to do `import XMonad` first
00:21:05 <scrungus> Oh probably
00:21:13 <scrungus> So those are xmonad functions right?
00:21:29 <scrungus> Okay it worked
00:21:55 <scrungus> ghci> openDisplay "" >>= getCleanedScreenInfo
00:21:56 <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}]
00:21:56 <scrungus> ghci>
00:22:01 <geekosaur> okay, so the rectangles in order should reflect what you have in the xrandr command
00:22:53 <scrungus> What is "rect_x = 3840" referring to?
00:23:36 <geekosaur> the "x" part of the `--pos` parameter, which is `x`x`y`
00:24:46 <scrungus> I guess tit's not the same order
00:24:50 <scrungus> it's*
00:24:56 <geekosaur> looks to me like the rectangles are sorted by reverse x offset
00:25:07 <geekosaur> which is odd
00:25:42 <scrungus> Why would that happen then?
00:26:34 <geekosaur> that's almost always the video driver's fault; it's supposed to report them in xrandr order
00:26:48 <scrungus> So I should look into my video drivers?
00:27:04 <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
00:27:24 <geekosaur> it sounds like it, yes
00:27:36 <scrungus> Would the physical screens module be able negate this issue you think?
00:28:26 <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
00:29:19 <scrungus> Well thank you so much for helping me out!
00:29:28 <scrungus> I'm always worried about being annoying when I ask for help with stuff
00:29:44 <geekosaur> no problem, it's what we're here for
00:31:06 <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
00:34:48 × scrungus quits (~scrungus@bras-base-aurron9127w-grc-54-70-24-71-72.dsl.bell.ca) (Quit: Client closed)
00:54:34 × td_ quits (~td@i53870925.versanet.de) (Ping timeout: 260 seconds)
00:56:06 td_ joins (~td@i53870931.versanet.de)
00:57:16 yaslam joins (~yaslam@user/yaslam)
00:57:36 yaslam parts (~yaslam@user/yaslam) ()
03:02:55 × banc quits (banc@gateway/vpn/protonvpn/banc) (Ping timeout: 248 seconds)
03:18:04 × td_ quits (~td@i53870931.versanet.de) (Ping timeout: 260 seconds)
03:19:35 td_ joins (~td@i53870938.versanet.de)
03:24:23 banc joins (banc@gateway/vpn/protonvpn/banc)
03:33:56 × ghormoon quits (~ghormoon@ghorland.net) (Ping timeout: 268 seconds)
04:02:54 ghormoon joins (~ghormoon@ghorland.net)
06:27:55 × jao quits (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 252 seconds)
07:24:34 qbt joins (~qbt@user/edun)
08:40:17 × ft quits (~ft@p4fc2a257.dip0.t-ipconnect.de) (Quit: leaving)
09:25:03 × scardinal quits (~supreme@customer-212-237-101-39.ip4.gigabit.dk) (Ping timeout: 252 seconds)
09:30:37 scardinal joins (~supreme@customer-212-237-101-39.ip4.gigabit.dk)
11:10:23 × qbt quits (~qbt@user/edun) (Ping timeout: 248 seconds)
12:57:50 qbt joins (~qbt@user/edun)
13:00:35 jao joins (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
14:26:42 telser_ joins (~quassel@user/telser)
14:27:12 × telser quits (~quassel@user/telser) (Ping timeout: 248 seconds)
14:54:26 ft joins (~ft@p4fc2a257.dip0.t-ipconnect.de)
16:00:04 × uhoreg quits (~uhoreg@2001:470:69fc:105::35f) (Quit: You have been kicked for being idle)
16:00:08 × unclechu quits (~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle)
16:05:30 × fjMSX quits (~hypni2p@89-179-32-81.broadband.corbina.ru) (Quit: Уш'лЪЬ їз єтой IRC сетї)
16:15:52 × ml| quits (~ml|@user/ml/x-5298235) (Quit: WeeChat 3.6)
16:32:10 ml| joins (~ml|@user/ml/x-5298235)
16:32:46 × ml| quits (~ml|@user/ml/x-5298235) (Client Quit)
17:12:43 × ectospasm quits (~ectospasm@user/ectospasm) (Ping timeout: 248 seconds)
17:16:10 ectospasm joins (~ectospasm@user/ectospasm)
17:46:04 × qbt quits (~qbt@user/edun) (Ping timeout: 252 seconds)
19:35:28 tremon joins (~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl)
19:46:44 <xmonadtrack> New xmonad-contrib branch created: pull/796 (1 commit) https://github.com/xmonad/xmonad-contrib/pull/796
19:46:59 unclechu joins (~unclechu@2001:470:69fc:105::354)
20:21:52 × telser_ quits (~quassel@user/telser) (Ping timeout: 248 seconds)
20:22:22 telser joins (~quassel@user/telser)
20:54:28 × tremon quits (~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl) (Quit: getting boxed in)

All times are in UTC on 2023-01-27.