2025/01/13

2025-01-13 00:27:25 +0100catman(~catman@user/catman) (Quit: WeeChat 4.5.1)
2025-01-13 00:29:10 +0100catman(~catman@user/catman) catman
2025-01-13 03:52:16 +0100rekahsoft(~rekahsoft@70.51.99.237) (Quit: connecting on another system)
2025-01-13 03:52:50 +0100rekahsoft(~rekahsoft@70.51.99.237) rekahsoft
2025-01-13 05:05:24 +0100rekahsoft(~rekahsoft@70.51.99.237) (Ping timeout: 245 seconds)
2025-01-13 07:02:01 +0100ft(~ft@p4fc2a354.dip0.t-ipconnect.de) (Quit: leaving)
2025-01-13 09:14:24 +0100ChubaDuba(~ChubaDuba@79.136.181.108) ChubaDuba
2025-01-13 14:14:10 +0100mc47(~yecinem@host-212-114-138-22.customer.m-online.net)
2025-01-13 14:14:39 +0100mc47(~yecinem@host-212-114-138-22.customer.m-online.net) (Changing host)
2025-01-13 14:14:39 +0100mc47(~yecinem@xmonad/TheMC47) mc47
2025-01-13 14:15:57 +0100 <mc47> hey guys! I (finally) can focus again on xmonad, if there is anything where you need assistance or support, just reach out
2025-01-13 14:16:07 +0100 <mc47> (maybe also just to my email, I don't check IRC often)
2025-01-13 14:26:07 +0100 <geekosaur> I think the biggest fire at the moment is that practically everything that's based on `LayoutModifier` is broken wrt `Hide` and `ReleaseResources`, but I'm already poking at that
2025-01-13 14:27:05 +0100 <geekosaur> https://github.com/xmonad/xmonad-contrib/issues/136
2025-01-13 14:36:06 +0100 <liskin> I was meaning to look into it because that seems extremely unlikely
2025-01-13 14:37:45 +0100 <geekosaur> the default implementation of `handleMess` doesn't pass on `Hide` or `ReleaseResources`, it calls `doUnhook` and eats the messages. https://github.com/xmonad/xmonad-contrib/blob/master/XMonad/Layout/LayoutModifier.hs#L146
2025-01-13 14:38:01 +0100 <liskin> https://github.com/xmonad/xmonad-contrib/blob/master/XMonad/Layout/LayoutModifier.hs#L263 - the lower layout always gets to handle the message, unless it was modified and turned into something else, which few modifiers do
2025-01-13 14:38:39 +0100 <liskin> mc47: what changed in your life that you can get back to xmonad, btw?
2025-01-13 14:41:00 +0100 <liskin> (in my case it's the other way around - I don't think I'll be able to do much xmonad stuff until I stop having a full time job, but once that happens, I probably won't afford to stay in London, because xmonad absolutely doesn't have enough donations to make that viable, even if I worked full time on it)
2025-01-13 14:42:53 +0100 <mc47> liskin: I was honestly overwhelmed with life a bit for the past year. It was the first year working full-time, so I kinda needed to find my rhythm. Now I feel more comfortable looking at a screen and coding after work :)
2025-01-13 14:43:34 +0100 <mc47> I'll try to take a look geekosaur
2025-01-13 14:45:42 +0100 <liskin> mc47: oh, that's awesome then :-)
2025-01-13 14:46:15 +0100 <liskin> I've never managed that with a full-time job.
2025-01-13 14:47:49 +0100 <mc47> Honestly, it helps that the weather is kinda shit now so I'm not tempted to go outside :D and pre-cooking for the week helps with the free time
2025-01-13 14:48:10 +0100T_X(~T_X@diktynna.open-mesh.org) (Read error: Connection reset by peer)
2025-01-13 14:48:20 +0100T_X(~T_X@diktynna.open-mesh.org) T_X
2025-01-13 15:25:47 +0100ChubaDuba(~ChubaDuba@79.136.181.108) (Quit: WeeChat 4.5.1)
2025-01-13 17:56:35 +0100Guest7(~Guest13@c-98-38-94-42.hsd1.co.comcast.net)
2025-01-13 17:57:40 +0100Guest7(~Guest13@c-98-38-94-42.hsd1.co.comcast.net) (Client Quit)
2025-01-13 17:57:58 +0100Guest31(~Guest31@c-98-38-94-42.hsd1.co.comcast.net)
2025-01-13 17:58:30 +0100 <Guest31> does anyone know how I can get tap-to-click working on my touchpad? I'm running xmonad on fedora under GDM and tap-to-click works in gnome but not xmonad
2025-01-13 18:01:40 +0100 <geekosaur> it's an xinput setting, I couldn't tell you which one because touchpads aren't very consistent
2025-01-13 18:02:27 +0100 <L29Ah> Guest31: it's irrelevant to xmonad; also you can use synclient(1) perhaps
2025-01-13 18:02:53 +0100 <Guest31> if it's irrelevant to xmonad why does it work without doing anything under gnome?
2025-01-13 18:05:09 +0100 <L29Ah> ask gnome
2025-01-13 18:05:43 +0100 <L29Ah> xmonad is a window manager, it doesn't configure input devices, unlike gnome that tries to do everything apparently
2025-01-13 18:07:30 +0100 <geekosaur> as does mate. that's why they're desktop managers, not just window managers
2025-01-13 18:07:39 +0100 <L29Ah> https://hackage.haskell.org/package/xmonad-contrib-0.18.1/docs/XMonad-Config-Gnome.html apparently one can use xmonad with gnome
2025-01-13 18:08:37 +0100 <geekosaur> you used to be able to with gnome 2, or if you have gnome-flashback whoich is gnome 2 with a gnome 3-ish theme
2025-01-13 18:08:46 +0100 <geekosaur> gnome 3 itself cannot
2025-01-13 18:10:39 +0100 <geekosaur> https://www.baeldung.com/linux/enable-disable-touchpad-scrolling-tapping-command-line
2025-01-13 18:10:58 +0100 <Guest31> I'm not sure what that gnomeConfig does...I didn't need to use it at all, I just installed xmonad with dnf and it showed up as an option in GDM
2025-01-13 18:11:15 +0100 <geekosaur> I'm not seeing the relevant options on my local touchpad but it's not yours and may not support tap to click
2025-01-13 18:11:41 +0100 <Guest31> looks like it maybe just sets terminal, which I don't want anyway. I just want the gnome mouse settings to get applied, I wonder if there's some gnome command I can run to do that
2025-01-13 18:11:47 +0100 <geekosaur> it switches the default terminal and hooks mod-shift-q to the gnome logout dialog, pretty much
2025-01-13 18:13:31 +0100 <geekosaur> you can run the gnome settings manager but expect it to kill xmonad and start gnome 3
2025-01-13 18:13:37 +0100 <geekosaur> it's all tied together
2025-01-13 18:14:06 +0100ft(~ft@p4fc2a354.dip0.t-ipconnect.de) ft
2025-01-13 18:17:50 +0100ash3en(~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) ash3en
2025-01-13 18:30:10 +0100Guest31(~Guest31@c-98-38-94-42.hsd1.co.comcast.net) (Ping timeout: 240 seconds)
2025-01-13 18:35:03 +0100 <mc47> For what it's worth: https://wiki.archlinux.org/title/Touchpad_Synaptics. They probably just need a driver installed and a configuration file under /etc/X11/xorg.conf.d/
2025-01-13 18:39:53 +0100mc47(~yecinem@xmonad/TheMC47) (Ping timeout: 265 seconds)
2025-01-13 19:01:59 +0100ash3en(~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Quit: ash3en)
2025-01-13 19:16:05 +0100hightower2(~hightower@213.186.15.36) (Remote host closed the connection)
2025-01-13 19:20:16 +0100Guest31(~Guest31@c-98-38-94-42.hsd1.co.comcast.net)
2025-01-13 19:27:43 +0100mc47(~yecinem@xmonad/TheMC47) mc47
2025-01-13 19:32:16 +0100mc47(~yecinem@xmonad/TheMC47) (Remote host closed the connection)
2025-01-13 20:28:20 +0100catman(~catman@user/catman) (Quit: WeeChat 4.5.1)
2025-01-13 20:36:42 +0100ircbrowse_tom(~ircbrowse@user/tomsmeding/bot/ircbrowse-tom) ircbrowse_tom
2025-01-13 20:36:46 +0100Server+cnt
2025-01-13 20:53:22 +0100catman(~catman@user/catman) catman
2025-01-13 21:01:41 +0100catman(~catman@user/catman) (Quit: WeeChat 4.5.1)
2025-01-13 21:06:31 +0100catman(~catman@user/catman) catman
2025-01-13 21:14:28 +0100Guest31(~Guest31@c-98-38-94-42.hsd1.co.comcast.net) (Quit: Client closed)
2025-01-13 21:27:40 +0100catman(~catman@user/catman) (Quit: WeeChat 4.5.1)
2025-01-13 22:33:47 +0100Guest31(~Guest31@c-98-38-94-42.hsd1.co.comcast.net)
2025-01-13 23:00:37 +0100Guest31(~Guest31@c-98-38-94-42.hsd1.co.comcast.net) (Quit: Client closed)
2025-01-13 23:13:18 +0100Forkk(~forkk@li926-228.members.linode.com) (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.)
2025-01-13 23:15:22 +0100Forkk13(~forkk@li926-228.members.linode.com) Forkk
2025-01-13 23:36:02 +0100hightower2(~hightower@213.186.15.36) hightower2