| 2023-01-26 00:33:42 +0000 | ghormoon | (~ghormoon@ghorland.net) (Ping timeout: 255 seconds) |
| 2023-01-26 01:02:08 +0000 | ghormoon | (~ghormoon@ghorland.net) |
| 2023-01-26 01:27:09 +0000 | telser_ | (~quassel@user/telser) (Ping timeout: 256 seconds) |
| 2023-01-26 01:27:37 +0000 | telser | (~quassel@user/telser) |
| 2023-01-26 02:15:14 +0000 | blaa | (~bla@83.24.73.237.ipv4.supernova.orange.pl) |
| 2023-01-26 02:15:59 +0000 | bla | (~bla@83.24.70.42.ipv4.supernova.orange.pl) (Ping timeout: 260 seconds) |
| 2023-01-26 02:37:37 +0000 | rundown | (~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) (Quit: WeeChat 3.0) |
| 2023-01-26 03:03:32 +0000 | banc | (banc@gateway/vpn/protonvpn/banc) (Ping timeout: 255 seconds) |
| 2023-01-26 03:13:43 +0000 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2023-01-26 03:24:29 +0000 | banc | (banc@gateway/vpn/protonvpn/banc) |
| 2023-01-26 03:47:27 +0000 | td_ | (~td@i53870930.versanet.de) (Ping timeout: 252 seconds) |
| 2023-01-26 03:49:10 +0000 | td_ | (~td@i53870925.versanet.de) |
| 2023-01-26 05:10:06 +0000 | thunderrd | (~thunderrd@183.182.111.166) (Read error: Connection reset by peer) |
| 2023-01-26 05:10:39 +0000 | thunderrd | (~thunderrd@183.182.111.166) |
| 2023-01-26 06:06:47 +0000 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 246 seconds) |
| 2023-01-26 06:36:14 +0000 | <Solid> | I think it would be valuable to have the core natively support [(KeyMask, KeySym)] bindings, making submap obsolete alltogether (perhaps even integrating NamedActions while we're at it) |
| 2023-01-26 06:36:22 +0000 | <Solid> | But realistically that's never going to really happen, is it? |
| 2023-01-26 06:56:44 +0000 | qbt | (~qbt@user/edun) |
| 2023-01-26 08:59:46 +0000 | ft | (~ft@p4fc2a257.dip0.t-ipconnect.de) (Quit: leaving) |
| 2023-01-26 09:00:04 +0000 | nihilipster[m] | (~nihilipst@2001:470:69fc:105::720) (Quit: You have been kicked for being idle) |
| 2023-01-26 09:00:10 +0000 | unclechu | (~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle) |
| 2023-01-26 09:27:20 +0000 | jludwig | (~justin@li657-110.members.linode.com) (Ping timeout: 246 seconds) |
| 2023-01-26 09:30:18 +0000 | jludwig | (~justin@li657-110.members.linode.com) |
| 2023-01-26 09:49:16 +0000 | T_X | (~T_X@diktynna.open-mesh.org) (Read error: Connection reset by peer) |
| 2023-01-26 09:49:24 +0000 | T_X | (~T_X@diktynna.open-mesh.org) |
| 2023-01-26 10:28:06 +0000 | <geekosaur> | it might be an option for 1.1 since we're already looking at making a major change |
| 2023-01-26 10:28:21 +0000 | unclechu | (~unclechu@2001:470:69fc:105::354) |
| 2023-01-26 10:56:14 +0000 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 246 seconds) |
| 2023-01-26 10:56:45 +0000 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2023-01-26 11:28:00 +0000 | qbt | (~qbt@user/edun) (Ping timeout: 248 seconds) |
| 2023-01-26 13:36:16 +0000 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2023-01-26 13:42:39 +0000 | kalj | (~kalj@78-71-20-170-no193.tbcn.telia.com) |
| 2023-01-26 14:07:10 +0000 | fjMSX | (~hypni2p@89-179-32-81.broadband.corbina.ru) |
| 2023-01-26 14:37:15 +0000 | kalj | (~kalj@78-71-20-170-no193.tbcn.telia.com) (Quit: Client closed) |
| 2023-01-26 16:00:04 +0000 | AngryBromide[m] | (~angrybrom@2001:470:69fc:105::1:cfb3) (Quit: You have been kicked for being idle) |
| 2023-01-26 16:00:09 +0000 | unclechu | (~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle) |
| 2023-01-26 16:28:37 +0000 | Jadesheit[m] | Jadeitits[m] |
| 2023-01-26 18:03:49 +0000 | ft | (~ft@p4fc2a257.dip0.t-ipconnect.de) |
| 2023-01-26 18:09:00 +0000 | tremon | (~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl) |
| 2023-01-26 18:57:11 +0000 | Digit | (~user@user/digit) (Ping timeout: 256 seconds) |
| 2023-01-26 20:28:07 +0000 | thyriaen | (~thyriaen@2a01:aea0:dd4:4fa4:6245:cbff:fe9f:48b1) |
| 2023-01-26 20:29:00 +0000 | <thyriaen> | I found a strange bug |
| 2023-01-26 20:29:11 +0000 | <thyriaen> | I am using XmonaD on 2 screens |
| 2023-01-26 20:29:14 +0000 | unclechu | (~unclechu@2001:470:69fc:105::354) |
| 2023-01-26 20:29:30 +0000 | <thyriaen> | when i type xrandr --output monitor-2 --off |
| 2023-01-26 20:30:07 +0000 | <thyriaen> | xmonad does something really strange - it only puts screens on the first 2/3 of the screen and leaves the bottom third empty |
| 2023-01-26 20:30:58 +0000 | <thyriaen> | could be because my second screen is in vertical position but i am not sure -- any ideas ? ( restarting xmonad fixes it ) but it would be nice if i could toggle my 2nd screen on and off |
| 2023-01-26 20:32:01 +0000 | <geekosaur> | that's odd. rescreening should work fine, absent video driver bugs (restarting xmonad wouldn't help in that case, unless you also mean restarting the X server) |
| 2023-01-26 20:33:02 +0000 | <geekosaur> | I mean, I see that if I hotplug a monitor, but I also see it if it's sitting at the login screen (tested with both lightdm and gdm, also with gnome instead of xmonad) |
| 2023-01-26 20:37:36 +0000 | <geekosaur> | does mod-n help, by any chance? it should force a rescreen |
| 2023-01-26 21:04:27 +0000 | mc47 | (~mc47@xmonad/TheMC47) |
| 2023-01-26 22:13:03 +0000 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2023-01-26 23:10:22 +0000 | thyriaen | (~thyriaen@2a01:aea0:dd4:4fa4:6245:cbff:fe9f:48b1) (Remote host closed the connection) |
| 2023-01-26 23:29:25 +0000 | tremon | (~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl) (Quit: getting boxed in) |
| 2023-01-26 23:47:17 +0000 | scrungus | (~scrungus@bras-base-aurron9127w-grc-54-70-24-71-72.dsl.bell.ca) |
| 2023-01-26 23:49:52 +0000 | <scrungus> | Hi, I'm guessing you guys get a lot of questions from newbies but I'm having a weird issue that I just can't seem to figure out. |
| 2023-01-26 23:49:52 +0000 | <scrungus> | I have three monitors and by default xmonad behaves fine (but my monitors are out of order) but after I use xrandr to put my monitors in the right order, the workspace that's on my center monitor is only put into focus when my mouse is on another monitor. It's either the right or left one depending on what I set as my primary monitor. |
| 2023-01-26 23:50:25 +0000 | <scrungus> | I'm not sure if this is specifically an xmonad issue but I haven't found anyone who's described the same thing online. |
| 2023-01-26 23:51:53 +0000 | <geekosaur> | if you haven't changed the default bindings then only the primary monitor should ever have focus |
| 2023-01-26 23:53:24 +0000 | <geekosaur> | https://wiki.haskell.org/Xmonad/Frequently_asked_questions#Replacing_greedyView_with_view |
| 2023-01-26 23:55:55 +0000 | <scrungus> | I've read that, I don't think it's related to my issue. I can switch to the workspace I want but I just can't use my mouse in it because if my mouse moves to the workspace it focuses on a workspace on a different monitor |
| 2023-01-26 23:56:20 +0000 | <scrungus> | So I can use applications that require a mouse on a workspace that's on the monitor that's behaving strangely |
| 2023-01-26 23:56:28 +0000 | <geekosaur> | that… seems wrong. do you have a config? |
| 2023-01-26 23:57:52 +0000 | <geekosaur> | @where paste |
| 2023-01-26 23:57:52 +0000 | <lambdabot> | Help us help you: please paste full code, input and/or output at e.g. https://paste.tomsmeding.com |
| 2023-01-26 23:57:58 +0000 | <scrungus> | I was just following the quickstart guide on the website. I setup the bar but I didn't change anything related to the bahaviour of workspaces I don't think |
| 2023-01-26 23:57:59 +0000 | <scrungus> | Okay |