Note: This channel on freenode is currently not being logged anymore. The logs are reproduced here for posterity.

2020-12-03 23:24:49 +0100sagax(~sagax_nb@213.138.71.146) (Remote host closed the connection)
2020-12-03 23:54:45 +0100novas0x2a(~blah@157-131-125-210.fiber.dynamic.sonic.net) (Ping timeout: 240 seconds)
2020-12-03 23:56:45 +0100cynapse(~chris@d24-141-165-72.home.cgocable.net)
2020-12-04 00:06:38 +0100ghormoon(~ghormoon@ghorland.net) (Ping timeout: 264 seconds)
2020-12-04 00:08:36 +0100ghormoon(~ghormoon@ghorland.net)
2020-12-04 00:09:27 +0100 <Irishluck83> i have been on xmonad for 5 years, doesn't seem that long
2020-12-04 00:17:46 +0100seschwar(~seschwar@unaffiliated/seschwar) (Quit: :wq)
2020-12-04 00:20:59 +0100novas0x2a(~blah@157-131-125-210.fiber.dynamic.sonic.net)
2020-12-04 00:23:52 +0100cynapse(~chris@d24-141-165-72.home.cgocable.net) (Quit: leaving)
2020-12-04 00:24:14 +0100cynapse(~chris@d24-141-165-72.home.cgocable.net)
2020-12-04 00:26:32 +0100ddellacosta(dd@gateway/vpn/mullvad/ddellacosta)
2020-12-04 00:47:52 +0100sfrique(~sfrique@189.122.177.88)
2020-12-04 00:48:14 +0100 <sfrique> Another question, is there any effort to make xmonad run on wayland?
2020-12-04 00:58:31 +0100 <dminuoso> Yes and no.
2020-12-04 00:58:42 +0100 <dminuoso> There is wayland, but xmonad has no plans on moving to wayland
2020-12-04 00:58:46 +0100 <dminuoso> Err there is *waymonad
2020-12-04 00:59:53 +0100 <dminuoso> And xmonad is very much incompatible with wayland at every level
2020-12-04 01:00:53 +0100 <dminuoso> Sadly waymonad is currently dead, but that's just a matter of someone picking up the stick
2020-12-04 01:04:42 +0100isgy(~jy@82.38.116.187)
2020-12-04 01:06:02 +0100 <sfrique> i see, i am asking because i'm currently on i3 for a few years now, was planing on changing to some other tiling with auto tiling, i started to play with xmonad and got quite a few things working, but for a future proof i don't see how i can go with xmonad if there is now wayland plan =/
2020-12-04 01:06:27 +0100 <sfrique> and that also apply to others tiling wm
2020-12-04 01:09:51 +0100isgy(~jy@82.38.116.187) (Quit: WeeChat 2.6)
2020-12-04 01:10:09 +0100isgy(~jy@82.38.116.187)
2020-12-04 01:11:44 +0100 <Irishluck83> i'm sure they will need to move to wayland when they have too
2020-12-04 01:14:49 +0100isgy(~jy@82.38.116.187) (Client Quit)
2020-12-04 01:15:05 +0100isgy(~jy@82.38.116.187)
2020-12-04 01:15:31 +0100isgy(~jy@82.38.116.187) (Client Quit)
2020-12-04 01:16:06 +0100 <xaltsc> Is waymonad going anywhere btw ? Looks like developement has stalled almost two years ago now..
2020-12-04 01:16:24 +0100isgy(~jy@82.38.116.187)
2020-12-04 01:18:00 +0100 <Liskni_si> it'd be a lot easier to maintain wayland xmonad if there was a generic wayland compositor with an interface to run window managers in a separate process
2020-12-04 01:18:45 +0100 <Liskni_si> (or at least that's my feeling about it; no real experience with wayland apart from looking at waymonad and seeing all the complicated stuff that someone else should maintain :-))
2020-12-04 01:23:04 +0100isgy(~jy@82.38.116.187) (Ping timeout: 260 seconds)
2020-12-04 02:04:42 +0100 <vrs> waymonad was someone's personal project, I was going to look into it but yeah
2020-12-04 02:26:05 +0100xaltsc(~xaltsc@unaffiliated/xaltsc) (Ping timeout: 240 seconds)
2020-12-04 02:54:56 +0100notis(~notis@185.51.134.222) (Ping timeout: 240 seconds)
2020-12-04 03:11:12 +0100materiyolo(~materiyol@112.204.171.225)
2020-12-04 03:11:57 +0100 <sfrique> thanks for the info!
2020-12-04 03:12:14 +0100 <Hash> I need some tips and tricks on how to use xmond more effectively
2020-12-04 03:12:16 +0100 <Hash> :)
2020-12-04 03:12:30 +0100 <Hash> If I don't even know what all one can do, how can I do it
2020-12-04 03:12:40 +0100 <sfrique> i just installed it, feel free to ask whatever you need
2020-12-04 03:12:59 +0100 <Irishluck83> its however you want to use it Hash
2020-12-04 03:13:23 +0100 <Hash> https://termbin.com/co36
2020-12-04 03:13:27 +0100 <Hash> Here is my current config
2020-12-04 03:14:05 +0100 <sfrique> One thing i wanted to test but never got the chance, is to define the layout based on the screen it's on
2020-12-04 03:14:40 +0100 <Hash> , focusFollowsMouse = True
2020-12-04 03:14:46 +0100 <Hash> The best setting in the world.
2020-12-04 03:15:43 +0100 <Hash> , ("M-`", runOrRaisePrompt def)
2020-12-04 03:15:45 +0100 <Hash> And that
2020-12-04 03:17:28 +0100 <Hash> https://wiki.haskell.org/Xmonad/General_xmonad.hs_config_tips#Managing_Windows_aka_Manage_Hooks
2020-12-04 03:17:30 +0100 <Hash> Been reading this
2020-12-04 03:17:31 +0100 <Hash> Learning more
2020-12-04 03:46:37 +0100PacBilly(~PacBilly@2600:6c58:6400:11fc:b167:f9ce:862e:3091)
2020-12-04 03:47:10 +0100materiyolo(~materiyol@112.204.171.225) (Quit: WeeChat 2.9)
2020-12-04 04:08:38 +0100PacBilly(~PacBilly@2600:6c58:6400:11fc:b167:f9ce:862e:3091) (Quit: Textual IRC Client: www.textualapp.com)
2020-12-04 04:18:38 +0100davemq(~davemq@2600:1700:b1c0:2580:cff1:7c10:c5a4:57e0) (Ping timeout: 264 seconds)
2020-12-04 04:22:38 +0100davemq(~davemq@99-179-0-50.lightspeed.austtx.sbcglobal.net)
2020-12-04 04:35:37 +0100theDon(~td@muedsl-82-207-238-021.citykom.de) (Ping timeout: 264 seconds)
2020-12-04 04:37:08 +0100theDon(~td@94.134.91.27)
2020-12-04 04:50:25 +0100 <Hash> https://github.com/zaxtax/xmonad-sessions
2020-12-04 04:50:28 +0100 <Hash> Anyone ever ued this?
2020-12-04 04:53:34 +0100sfrique(~sfrique@189.122.177.88) (Ping timeout: 260 seconds)
2020-12-04 05:45:57 +0100abhixec(~abhixec@c-67-169-141-95.hsd1.ca.comcast.net)
2020-12-04 05:54:48 +0100sagax(~sagax_nb@213.138.71.146)
2020-12-04 06:01:13 +0100ericsagn1(~ericsagne@2405:6580:0:5100:5edc:6c03:7218:210e) (Ping timeout: 272 seconds)
2020-12-04 06:17:29 +0100Nahra(~Nahra@unaffiliated/nahra)
2020-12-04 06:27:56 +0100ddellacosta(dd@gateway/vpn/mullvad/ddellacosta) (Ping timeout: 272 seconds)
2020-12-04 07:14:23 +0100palo1(~weechat@c-base/crew/palo)
2020-12-04 07:17:10 +0100palo(~weechat@c-base/crew/palo) (Ping timeout: 246 seconds)
2020-12-04 07:17:10 +0100palo1palo
2020-12-04 07:38:51 +0100materiyolo(~materiyol@112.204.171.225)
2020-12-04 07:45:08 +0100materiyolo(~materiyol@112.204.171.225) (Quit: WeeChat 2.9)
2020-12-04 08:14:21 +0100ericsagnes(~ericsagne@2405:6580:0:5100:43fe:8354:1780:830b)
2020-12-04 08:17:47 +0100growpotkin(~growpotki@130-45-30-154.dyn.grandenetworks.net) (Quit: ZNC 1.8.2 - https://znc.in)
2020-12-04 08:33:01 +0100 <dminuoso> Mmm, I recently updated my entire system. Ever since, it seems that sometimes when when firefox is open the entire screen flickers shortly at unpredictable times
2020-12-04 08:33:17 +0100 <dminuoso> The flickering looks almost as if for a split second another window is being drawn, perhaps partially ontop of the scren
2020-12-04 08:33:28 +0100 <dminuoso> It's rare enough to majorly impact me, but it happens a few times a day
2020-12-04 08:33:40 +0100 <dminuoso> What might be going on?
2020-12-04 08:34:11 +0100 <dminuoso> My journald has nothing of interest during the time period
2020-12-04 08:36:11 +0100 <dminuoso> Mmm, even the region ontop of the status bar is affected.
2020-12-04 08:36:40 +0100 <dminuoso> How can firefox have control over this? I thought it's xmonads job to control the window layouting
2020-12-04 08:37:57 +0100 <dminuoso> It seems to be indirectly correlated to me hovering over links, at random times. The flickering exhibits shortly after
2020-12-04 08:38:45 +0100 <dminuoso> Ohh... I think it might happen when Slack is right behind Firefox...
2020-12-04 08:39:38 +0100 <dminuoso> Perhaps Slack is trying to grab?
2020-12-04 08:40:35 +0100 <dminuoso> Well, it's good that after 2 weeks I finally have something to go on.
2020-12-04 08:48:06 +0100xaltsc(~xaltsc@unaffiliated/xaltsc)
2020-12-04 08:50:37 +0100jchia(~jchia@58.32.35.67) (Ping timeout: 246 seconds)
2020-12-04 09:04:19 +0100jchia(~jchia@58.32.35.91)
2020-12-04 09:09:08 +0100cynapse(~chris@d24-141-165-72.home.cgocable.net) (Remote host closed the connection)
2020-12-04 09:12:37 +0100malook(~Thunderbi@5.108.42.152)
2020-12-04 09:23:07 +0100malook(~Thunderbi@5.108.42.152) ()
2020-12-04 09:30:15 +0100 <coldpress> dminuoso: try setting layers.acceleration.disabled to true
2020-12-04 09:32:37 +0100cfricke(~cfricke@unaffiliated/cfricke)
2020-12-04 09:42:13 +0100 <dminuoso> coldpress: Can you explain why that would help?
2020-12-04 09:43:46 +0100 <dminuoso> Im not convinced this is a firefox bug. It seems to trigger when some particular UI element is right behind firefox and my mouse hovers over it.
2020-12-04 09:43:54 +0100 <dminuoso> That is, a particular slack UI element
2020-12-04 09:43:56 +0100mc47(~yecinem@89.246.239.190)
2020-12-04 09:44:02 +0100 <dminuoso> (Not slack in firefox, but the slack native client)
2020-12-04 09:46:16 +0100notis(~notis@185.51.134.222)
2020-12-04 09:48:40 +0100wonko7(~wonko7@2a01:e35:2ffb:7040:55f1:c3a3:cdbe:bf52) (Quit: See You Space Cowboy..)