| 2021-12-17 01:06:10 +0100 | seschwar | (~seschwar@user/seschwar) (Quit: :wq) |
| 2021-12-17 01:29:53 +0100 | curiousgay | (~curiousga@77-120-141-90.kha.volia.net) (Quit: Leaving) |
| 2021-12-17 02:21:18 +0100 | obimod | (~obimod@gateway/vpn/pia/obimod) |
| 2021-12-17 02:30:00 +0100 | ormaaj | (~ormaaj@user/ormaaj) (Quit: Reconnecting) |
| 2021-12-17 02:30:44 +0100 | ormaaj | (~ormaaj@user/ormaaj) |
| 2021-12-17 03:20:34 +0100 | steve__ | (~steve@ool-182c2b80.dyn.optonline.net) (Ping timeout: 268 seconds) |
| 2021-12-17 03:50:37 +0100 | pl | (sid98063@id-98063.helmsley.irccloud.com) (Ping timeout: 240 seconds) |
| 2021-12-17 03:51:05 +0100 | pl | (sid98063@id-98063.helmsley.irccloud.com) |
| 2021-12-17 04:03:27 +0100 | banc | (banc@gateway/vpn/airvpn/banc) (Ping timeout: 256 seconds) |
| 2021-12-17 04:09:36 +0100 | abhixec | (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) |
| 2021-12-17 04:11:33 +0100 | <abhixec> | anyone know why some programs(Google chrome, visual studio code,atom) all hang/are unresponsive in xmonad. |
| 2021-12-17 04:16:42 +0100 | <kaizoku> | i haven't had that trouble with chrome, though I don't use it very often |
| 2021-12-17 04:16:53 +0100 | <kaizoku> | when you say hang, do they display anything prior to freezing? |
| 2021-12-17 04:18:58 +0100 | <abhixec> | it loads a screen but every action that I perform on chrome either loads or happens once I move to another window |
| 2021-12-17 04:19:35 +0100 | <abhixec> | for example when I do ctl+t to open a new tab it does nothing but when I move to different workspace or a window a new tab appears |
| 2021-12-17 04:23:17 +0100 | td_ | (~td@muedsl-82-207-238-051.citykom.de) (Ping timeout: 240 seconds) |
| 2021-12-17 04:23:52 +0100 | banc | (banc@gateway/vpn/airvpn/banc) |
| 2021-12-17 04:24:18 +0100 | <kaizoku> | hmm, this actually sounds familiar.. I remember running into something like this ages ago, but my old brain isn't remembering the details |
| 2021-12-17 04:24:37 +0100 | <kaizoku> | sounds like it's still running but not re-drawing the window |
| 2021-12-17 04:25:14 +0100 | td_ | (~td@94.134.91.242) |
| 2021-12-17 04:25:36 +0100 | <abhixec> | I remember geekosaur mentioning it could be something to do with the compositor but I don't have one I am just running x+xmonad :) |
| 2021-12-17 04:25:50 +0100 | <abhixec> | I also tried picom to see if that helped but still the same |
| 2021-12-17 04:26:48 +0100 | <kaizoku> | I have xcompmgr starting in my xinitrc but it's been in there so long idk if it even does anything anymore |
| 2021-12-17 04:27:19 +0100 | <abhixec> | kaizoku: ah! let me try running it |
| 2021-12-17 04:27:41 +0100 | <kaizoku> | I have it running `xcompmgr -n` |
| 2021-12-17 04:27:52 +0100 | <kaizoku> | oh i guess that's the default mode |
| 2021-12-17 04:31:22 +0100 | <abhixec> | ok that didn't quite resolve the issue! |
| 2021-12-17 04:31:45 +0100 | <kaizoku> | oh it looks like picom is a fork of a fork of xcompmgr actually |
| 2021-12-17 04:32:27 +0100 | <kaizoku> | sorry i'm not especially useful here ;) |
| 2021-12-17 04:33:09 +0100 | <kaizoku> | i'm woefully understudied on how X actually works |
| 2021-12-17 04:33:45 +0100 | <abhixec> | I noticed a weird thing, this seems to happen only when I am plugged to external monitor |
| 2021-12-17 04:41:57 +0100 | catman | (~catman@user/catman) |
| 2021-12-17 04:43:29 +0100 | <abhixec> | kaizoku: so I think I figured out what the issue was, google chrome has a use hardware acceleration when available option disabling that option somehow seems to have fixed this issue |
| 2021-12-17 05:12:54 +0100 | catman | (~catman@user/catman) (Quit: WeeChat 3.4-rc1) |
| 2021-12-17 05:38:06 +0100 | catman | (~catman@user/catman) |
| 2021-12-17 05:48:38 +0100 | abhixec | (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Quit: Reconnecting) |
| 2021-12-17 05:48:53 +0100 | abhixec | (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) |
| 2021-12-17 05:51:13 +0100 | ormaaj | ormaaj2 |
| 2021-12-17 06:35:59 +0100 | abhixec | (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Quit: leaving) |
| 2021-12-17 07:19:17 +0100 | benin | (~benin@183.82.204.250) (Ping timeout: 240 seconds) |
| 2021-12-17 07:31:43 +0100 | ebray187 | (~ebray187@2800:150:129:17c4:224:1dff:fed5:599e) (Quit: Konversation terminated!) |
| 2021-12-17 07:33:54 +0100 | steve__ | (~steve@ool-182c2b80.dyn.optonline.net) |
| 2021-12-17 07:36:21 +0100 | benin | (~benin@183.82.27.121) |
| 2021-12-17 08:24:53 +0100 | electr0n | (~electr0n@about/security/founder/electr0n) (Quit: WeeChat 3.3) |
| 2021-12-17 08:31:12 +0100 | cfricke | (~cfricke@user/cfricke) |
| 2021-12-17 08:37:02 +0100 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) |
| 2021-12-17 09:34:44 +0100 | gruntsplatter | (~sogens@pa49-182-100-68.pa.qld.optusnet.com.au) |
| 2021-12-17 09:35:29 +0100 | gruntsplatter2 | (~sogens@gateway/vpn/pia/sogens) |
| 2021-12-17 09:36:44 +0100 | gruntsplatter2 | (~sogens@gateway/vpn/pia/sogens) (Client Quit) |
| 2021-12-17 09:37:07 +0100 | gruntsplatter2 | (~sogens@gateway/vpn/pia/sogens) |
| 2021-12-17 09:37:13 +0100 | cfricke | (~cfricke@user/cfricke) (Quit: WeeChat 3.3) |
| 2021-12-17 09:39:48 +0100 | gruntsplatter | (~sogens@pa49-182-100-68.pa.qld.optusnet.com.au) (Ping timeout: 268 seconds) |
| 2021-12-17 10:00:09 +0100 | CorinCWStra[m] | (~cwstramat@2001:470:69fc:105::1:3671) (Quit: You have been kicked for being idle) |
| 2021-12-17 10:17:43 +0100 | allbery_b | (~geekosaur@xmonad/geekosaur) |
| 2021-12-17 10:17:43 +0100 | geekosaur | (~geekosaur@xmonad/geekosaur) (Killed (NickServ (GHOST command used by allbery_b))) |
| 2021-12-17 10:17:46 +0100 | allbery_b | geekosaur |
| 2021-12-17 10:31:54 +0100 | cfricke | (~cfricke@user/cfricke) |
| 2021-12-17 10:50:17 +0100 | mvk | (~mvk@2607:fea8:5cdd:f000::745c) (Ping timeout: 240 seconds) |
| 2021-12-17 10:53:03 +0100 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) (Quit: WeeChat 3.3) |
| 2021-12-17 10:54:08 +0100 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) |
| 2021-12-17 11:31:22 +0100 | geekosaur | (~geekosaur@xmonad/geekosaur) (Remote host closed the connection) |
| 2021-12-17 11:40:51 +0100 | geekosaur | (~geekosaur@xmonad/geekosaur) |
| 2021-12-17 12:08:30 +0100 | <liskin> | noex: I've been doing those exercises from your video, and a few more from other videos, and I've seen some improvement, so thanks |
| 2021-12-17 12:08:48 +0100 | <liskin> | and I had an in-person appointment today and they recommended some additional exercises |
| 2021-12-17 12:09:11 +0100 | <liskin> | also, which I find quite funny, they told me to get a wrist support brace from Amazon :-) |
| 2021-12-17 12:10:14 +0100 | <liskin> | (in Czechia they'd send me to a specialized shop with these things in the hospital campus, but here things are different it seems) |
| 2021-12-17 12:13:24 +0100 | <geekosaur> | abhixec, I used to have weird stuff like that with hardware acceleration enabled, but haven't seen it in a while |
| 2021-12-17 12:39:30 +0100 | geekosaur | (~geekosaur@xmonad/geekosaur) (Quit: Leaving) |
| 2021-12-17 12:39:53 +0100 | geekosaur | (~geekosaur@xmonad/geekosaur) |
| 2021-12-17 12:45:17 +0100 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) (Ping timeout: 240 seconds) |
| 2021-12-17 14:18:28 +0100 | <Vermoot> | Huh |
| 2021-12-17 14:19:00 +0100 | <Vermoot> | News from the "sometimes xmobar shows on top of firefox fullscreen even with ewmhFullscreen and ewmh" |
| 2021-12-17 14:19:28 +0100 | <Vermoot> | If that happens, I can "solve it" by opening a new firefox window and closing it. Then when I go fullscreen again, everything is as expected. |
| 2021-12-17 14:27:47 +0100 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) |
| 2021-12-17 15:20:32 +0100 | banc | (banc@gateway/vpn/airvpn/banc) (Ping timeout: 240 seconds) |
| 2021-12-17 15:50:14 +0100 | ml| | (~ml|@user/ml/x-5298235) (Quit: WeeChat 3.0.1) |
| 2021-12-17 16:01:39 +0100 | seschwar | (~seschwar@user/seschwar) |
| 2021-12-17 16:37:28 +0100 | Arya[m] | (~gi-ytmatr@2001:470:69fc:105::d663) (Excess Flood) |
| 2021-12-17 16:37:42 +0100 | Arya[m] | (~gi-ytmatr@2001:470:69fc:105::d663) |
| 2021-12-17 17:08:55 +0100 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) (Quit: WeeChat 3.3) |
| 2021-12-17 17:13:40 +0100 | ebray187 | (~ebray187@2800:150:129:17c4:224:1dff:fed5:599e) |
| 2021-12-17 17:17:50 +0100 | <Solid> | my bet is on firefox doing something fucky wucky |
| 2021-12-17 17:27:31 +0100 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) |
| 2021-12-17 17:39:11 +0100 | Vermoot | (~vermoot@89-158-106-112.rev.numericable.fr) (Remote host closed the connection) |
| 2021-12-17 17:50:08 +0100 | cfricke | (~cfricke@user/cfricke) (Quit: WeeChat 3.3) |
| 2021-12-17 17:52:49 +0100 | jludwig | (~justin@user/jludwig) |
| 2021-12-17 18:11:13 +0100 | ml| | (~ml|@user/ml/x-5298235) |
| 2021-12-17 18:30:30 +0100 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) (Quit: WeeChat 3.3) |
| 2021-12-17 18:31:59 +0100 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 268 seconds) |
| 2021-12-17 18:32:15 +0100 | ml| | (~ml|@user/ml/x-5298235) (Quit: WeeChat 3.3) |
| 2021-12-17 18:33:44 +0100 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2021-12-17 18:45:42 +0100 | benin | (~benin@183.82.27.121) (Quit: The Lounge - https://thelounge.chat) |
| 2021-12-17 19:07:03 +0100 | ml| | (~ml|@user/ml/x-5298235) |
| 2021-12-17 20:09:07 +0100 | Vermoot | (~vermoot@89-158-106-112.rev.numericable.fr) |
| 2021-12-17 20:13:08 +0100 | electr0n | (~electr0n@about/security/founder/electr0n) |
| 2021-12-17 20:28:30 +0100 | abhixec | (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) |
| 2021-12-17 20:34:44 +0100 | abhixec[m] | (~abhixecma@2001:470:69fc:105::a2a) |
| 2021-12-17 20:35:51 +0100 | <abhixec> | geekosaur: even though I kind of managed to fix that issue on google chrome code and other electron based apps still hang/show blank context menus |
| 2021-12-17 20:38:00 +0100 | <geekosaur> | if toggling hardware acceleration fixed it in chrome, there's a decent chance it's a driver issue. can't really be an xmonad issue as client rendering is completely between the x server and the client; the window manager only controls window position / sizing, not drawing |
| 2021-12-17 20:38:16 +0100 | abhixec[m] | (~abhixecma@2001:470:69fc:105::a2a) () |
| 2021-12-17 20:38:58 +0100 | <abhixec> | geekosaur: thanks let me see if I dig something on this on archwiki |
| 2021-12-17 20:42:48 +0100 | <geekosaur> | (the only desktop component that is involved with drawing is the compositor, which is why my earlier suggestion. plus we've actually seen that one happen) |
| 2021-12-17 20:45:27 +0100 | <abhixec> | the strange thing is everything seems to work fine on laptop just when I connect to external monitor I see this issue |
| 2021-12-17 20:48:33 +0100 | <geekosaur> | that also suggests the driver, sadly |
| 2021-12-17 20:48:43 +0100 | <geekosaur> | because it's about the only thing that can see a difference |
| 2021-12-17 20:49:51 +0100 | <abhixec> | *facepalm* nvidia!!! |
| 2021-12-17 20:54:54 +0100 | abhixec | (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Quit: rebooting) |
| 2021-12-17 20:55:36 +0100 | twiclo | (~twiclo@2604:7b80:2000:1069:52fc:cedd:fbeb:10c) |
| 2021-12-17 20:56:50 +0100 | <twiclo> | Does anyone know of a way to select a workspace when you mouse over it? If you have an empty desktop you have to click it before you can spawn things to i twith dmenu |
| 2021-12-17 21:01:01 +0100 | abhixec | (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) |
| 2021-12-17 21:01:02 +0100 | twiclo | (~twiclo@2604:7b80:2000:1069:52fc:cedd:fbeb:10c) (Ping timeout: 240 seconds) |
| 2021-12-17 21:03:28 +0100 | <FOSSHuman[m]> | <twiclo> "Does anyone know of a way to..." <- I use XMobar which doesn't have a feature to do this I dont think |
| 2021-12-17 21:04:02 +0100 | <FOSSHuman[m]> | I think some other bars like Taffybar might? be able to do this though |
| 2021-12-17 21:04:27 +0100 | <FOSSHuman[m]> | * like Taffybar (might?, * might?) be |
| 2021-12-17 21:05:00 +0100 | <geekosaur> | bars generally can't do this (mouseover, not click) |
| 2021-12-17 21:05:13 +0100 | <FOSSHuman[m]> | <twiclo> "Does anyone know of a way to..." <- Or you can just spawn something with dmenu and then shift it to the workspace or use a manageHook |
| 2021-12-17 21:05:15 +0100 | <geekosaur> | xmonad might be able to do it with a handleEventHook |
| 2021-12-17 21:06:16 +0100 | <geekosaur> | with some shortcomings, for example desktop windows are pretty much impossible to handle that way |
| 2021-12-17 21:06:36 +0100 | <kwer[m]> | This came up recently in the xmonad subreddit: https://www.reddit.com/r/xmonad/comments/qi1tlm/focus_empty_workspace_on_cursor_hover/ |
| 2021-12-17 21:07:32 +0100 | <FOSSHuman[m]> | kwer[m]: "Yeah, I also experience this occassionally (not always, seems to depend on the speed of pointer movement). This is definitely not a configuration issue, but a bug in xmonad core." |
| 2021-12-17 21:07:35 +0100 | <FOSSHuman[m]> | is what Liskin said |
| 2021-12-17 21:08:12 +0100 | <FOSSHuman[m]> | Actually, I was wondering why this was happening too when I had two monitors running |
| 2021-12-17 21:11:16 +0100 | <FOSSHuman[m]> | @kwer: thanks for posting that link btw, I rarely check XMonad Reddit |
| 2021-12-17 21:11:17 +0100 | <lambdabot> | Unknown command, try @list |
| 2021-12-17 21:11:44 +0100 | <geekosaur> | oh, now I see where xmobar came into it. that wouldn't be xmonad core but something about the X server compressing out extra motions it thinks aren't necessary :( |
| 2021-12-17 21:12:17 +0100 | <geekosaur> | would need the xmobar to be an InputOnly window to change that, I think? |
| 2021-12-17 21:14:59 +0100 | <kwer[m]> | FOSSHuman[m]: It's a shameless plug 😉 |
| 2021-12-17 21:15:40 +0100 | <geekosaur> | kwer[m], how would you feel about packaging up your little setup and submitting it to -contrib? |
| 2021-12-17 21:17:52 +0100 | <FOSSHuman[m]> | I thought X.A.UpdateFocus could fix this behaviour, but according to @geekosaur it is more internal |
| 2021-12-17 21:18:09 +0100 | <FOSSHuman[m]> | I guess it was just bcs of the name |
| 2021-12-17 21:19:04 +0100 | <FOSSHuman[m]> | It does say |
| 2021-12-17 21:19:20 +0100 | <FOSSHuman[m]> | * does say "Updates the focus on mouse move in unfocused windows." so its unrelated anyway I guess |
| 2021-12-17 21:20:41 +0100 | <kwer[m]> | geekosaur: Haha yeah, some other people suggested that as well. I'm not sure about the desktop focus because it does listen to all pointer movements. I was considering limiting it but it seems that the Haskell interface to Xlib doesn't report the time for pointer motion events |
| 2021-12-17 21:21:57 +0100 | <kwer[m]> | FOSSHuman[m]: Hmm, I guess it only listens to window entry events? Here, the issue is that you're in the root window the whole time |
| 2021-12-17 21:33:55 +0100 | <FOSSHuman[m]> | `alt + w/e/r` with X.A.UpdatePointer works pretty decently, it just moves to pointer to the other screen when pressing that keybind. Even though physically moving the mouse to the other screen sometimes doesn't switch XMonad to that workspace that the other screen is using (if no windows are present on the other screen)... |
| 2021-12-17 21:36:13 +0100 | <FOSSHuman[m]> | s/that/either/, s/keybind/of them keybinds/ |
| 2021-12-17 21:37:26 +0100 | <FOSSHuman[m]> | But clicking on the desktop on the other screen does move XMonad to the workspace that the other screen is using |
| 2021-12-17 21:38:16 +0100 | <FOSSHuman[m]> | * the desktop when no windows are present on the |
| 2021-12-17 21:48:02 +0100 | curiousgay | (~curiousga@77-120-141-90.kha.volia.net) |
| 2021-12-17 21:50:23 +0100 | <kwer[m]> | Actually, what you said earlier, FOSS Human , might be better than listening to all pointer motion events. In the end, if the workspace is empty, what's the point of shifting the focus? One could just check where the pointer is whenever a new window is added and move it there. Would that be possible or would it force the wrongly focussed workspace to get rearranged before the window is moved? |
| 2021-12-17 21:51:18 +0100 | <geekosaur> | sounds like it'd be difficult or at least annoying if the manageHook shifts the window elsewhere |
| 2021-12-17 21:51:45 +0100 | <geekosaur> | obvious answer to that would be the logHook, except changing workspace or window focus would rerun it |
| 2021-12-17 21:55:17 +0100 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) |
| 2021-12-17 21:55:48 +0100 | <kwer[m]> | But couldn't you handle MapRequestEvents in your custom logHook (which I think is run before the default one) and shift the focus if necessary? |
| 2021-12-17 21:58:45 +0100 | <geekosaur> | the default is empty, and if the user does chain to it they could do so anywhere |
| 2021-12-17 21:59:30 +0100 | <geekosaur> | if you're looking for events that's handleEventHook, but MapRequest would end up being done before the window was managed (and therefore before the manageHook) |
| 2021-12-17 22:39:17 +0100 | obimod | (~obimod@gateway/vpn/pia/obimod) (Ping timeout: 240 seconds) |
| 2021-12-17 22:39:37 +0100 | obimod | (~obimod@gateway/vpn/pia/obimod) |
| 2021-12-17 22:55:37 +0100 | mohab | (~mohab@45.245.18.151) |
| 2021-12-17 22:58:30 +0100 | banc | (banc@gateway/vpn/airvpn/banc) |
| 2021-12-17 23:46:33 +0100 | benin | (~benin@183.82.27.121) |
| 2021-12-17 23:56:22 +0100 | mohab | (~mohab@45.245.18.151) (Quit: WeeChat 3.3) |