2023/07/23

2023-07-23 00:50:07 +0200 <absta[m]> <geekosaur> "some display managers autostart..." <- Interesting, so far both lightdm and sddm seem to support it.
2023-07-23 00:50:55 +0200 <geekosaur> others might but you might have to edit a config file and restart them
2023-07-23 00:51:04 +0200 <geekosaur> some others might not
2023-07-23 00:51:49 +0200 <absta[m]> May I ask what other display managers are out there that can be used with xmonad?
2023-07-23 00:53:18 +0200T_X_T_X
2023-07-23 00:54:03 +0200 <geekosaur> gdm (probably autostarts it), wdm, lxdm — just looking quickly at `apt-cache search 'display manager'`; there may be others
2023-07-23 00:54:24 +0200 <geekosaur> display managers are completely divorced from sessions
2023-07-23 00:57:59 +0200 <geekosaur> well, no, since they can wrap the sessions in things like `dbus-launch` like we're talking about, but any display manager can start any session type (with some work; xdm/wdm won't run XDG sessions directly and the others need an XDG session wrapper to run ~/.xsession)
2023-07-23 01:05:12 +0200 <absta[m]> TIL about wdm. Maybe lxdm is lightweight enough to not start dbus session itself..
2023-07-23 01:07:11 +0200 <geekosaur> there used to be more but many have ceased to exist. KDE used to have its own kdm for example
2023-07-23 01:12:22 +0200 <geekosaur> I think MATE had mdm for a while too, then switched to lightdm
2023-07-23 01:19:05 +0200tremon(~tremon@83.80.159.219) (Quit: getting boxed in)
2023-07-23 01:34:46 +0200lain1001(~lain@76.108.135.43) (Ping timeout: 260 seconds)
2023-07-23 03:28:33 +0200 <absta[m]> Were LightDM and SDDM separate projects from MATE and KDE?
2023-07-23 03:29:04 +0200 <geekosaur> I don't know
2023-07-23 03:31:53 +0200 <geekosaur> wikipedia says they were both independent projects
2023-07-23 04:22:39 +0200td_(~td@i53870914.versanet.de) (Ping timeout: 244 seconds)
2023-07-23 04:24:41 +0200td_(~td@i53870909.versanet.de)
2023-07-23 05:38:42 +0200 <absta[m]> Woah
2023-07-23 10:57:21 +0200hightower2(~hightower@141-136-238-132.dsl.iskon.hr)
2023-07-23 11:04:51 +0200liskin[m](~liskinmat@2001:470:69fc:105::768) (Remote host closed the connection)
2023-07-23 11:08:58 +0200unclechu(~unclechu@2001:470:69fc:105::354) (Remote host closed the connection)
2023-07-23 12:47:13 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2023-07-23 12:47:32 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2023-07-23 17:19:06 +0200Guest85(~Guest19@178.234.118.203)
2023-07-23 17:20:33 +0200 <Guest85> hey! a bit specific question, sorry for that: someone ever used xmonad with pijulius picom fork?
2023-07-23 17:20:47 +0200liskin[m](~liskinmat@2001:470:69fc:105::768)
2023-07-23 17:21:02 +0200unclechu(~unclechu@2001:470:69fc:105::354)
2023-07-23 17:31:29 +0200Guest85(~Guest19@178.234.118.203) (Quit: Client closed)
2023-07-23 17:31:33 +0200 <Solid> No, but I don't imagine you'd have many problems either
2023-07-23 17:33:42 +0200Guest19(~Guest19@178.234.118.203)
2023-07-23 17:34:49 +0200Guest19(~Guest19@178.234.118.203) (Client Quit)
2023-07-23 17:46:19 +0200Guest19(~Guest19@178.234.118.203)
2023-07-23 17:47:27 +0200Guest19(~Guest19@178.234.118.203) (Client Quit)
2023-07-23 17:47:46 +0200Guest19(~Guest19@178.234.118.203)
2023-07-23 17:50:17 +0200Guest19(~Guest19@178.234.118.203) (Client Quit)
2023-07-23 17:52:41 +0200Guest19(~Guest19@178.234.118.203)
2023-07-23 17:56:46 +0200 <Guest19> yes, generally I don't. but workspace switch animation is not playing properly, only when I switch them fast. if I do it about 4 sec after, it plays open or unmap animation, and if I switch to empty workspace, that happens without any anim. again, im sorry for that kind of question, but it breaks my mind, I've tried a lot of ways to fix.
2023-07-23 18:58:44 +0200liskin[m](~liskinmat@2001:470:69fc:105::768) (Remote host closed the connection)
2023-07-23 18:58:44 +0200unclechu(~unclechu@2001:470:69fc:105::354) (Remote host closed the connection)
2023-07-23 21:05:51 +0200 <geekosaur[c]> I don't think xmonad would be involved there except by having EwmhDesktops configured and telling pijulius to use EWMH. I have a `compton.conf` which does it for compton/ older picom but I don't know how to adapt it
2023-07-23 21:06:07 +0200liskin[m](~liskinmat@2001:470:69fc:105::768)
2023-07-23 21:06:52 +0200unclechu(~unclechu@2001:470:69fc:105::354)
2023-07-23 21:08:27 +0200 <geekosaur[c]> https://github.com/geekosaur/xmonad.hs/blob/3a0adb542f8de902a33abbd10e2dad53d61d64da/compton.conf
2023-07-23 21:11:15 +0200 <Guest19> right, but other vm's "support" this feature properly (the ones I tried). thanks for the answer!
2023-07-23 21:12:22 +0200 <Guest19> all guided things (ewmh, managedocks) are involved. (but I miss some tho)
2023-07-23 21:12:31 +0200 <Guest19> might miss*
2023-07-23 21:22:06 +0200 <geekosaur> I can't make guarantees that the way we manage windows works with what it expects. We already have a conflict with how Gnome does it that breaks some screen sharing apps (we withdraw windows, some other WMs including Mutter draw them off-screen instead)
2023-07-23 21:25:57 +0200 <Guest19> I see. As I remember on BSD xmonad+tint2+this fork work perfectly. Unfortunately, configs are gone, but they not so different, because I tried a lot of them. I understand, the issuie is not hundred percent related to xmonad, so I'm seeking maybe someone had such experience. Sorry for possible offtop.
2023-07-23 21:26:52 +0200 <geekosaur> not worried about offtopic, just tossing out suggestions
2023-07-23 21:27:03 +0200 <geekosaur> this is the first I'm hearing of pijulius though :(
2023-07-23 21:30:23 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Quit: Leaving)
2023-07-23 21:30:49 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2023-07-23 21:33:19 +0200 <geekosaur> (sorry, just noticed I needed to redo my emojis plugin — upgraded my distro the other day, things are still shaking down…)
2023-07-23 21:33:38 +0200 <Guest19> haha ^_-
2023-07-23 21:34:51 +0200 <geekosaur> 🙂
2023-07-23 21:34:57 +0200 <geekosaur> yes, that's better 😛
2023-07-23 21:35:52 +0200 <Guest19> that is :)
2023-07-23 22:45:12 +0200Guest19(~Guest19@178.234.118.203) (Quit: Client closed)