2025/05/04

2025-05-04 00:15:05 +0200gauge(~gauge@user/gauge) (Quit: Quitting)
2025-05-04 00:16:41 +0200gauge(~gauge@user/gauge) gauge
2025-05-04 00:22:19 +0200Buliarous(~gypsydang@46.232.210.139) (Remote host closed the connection)
2025-05-04 00:22:47 +0200Buliarous(~gypsydang@46.232.210.139) Buliarous
2025-05-04 01:15:43 +0200tremon(~tremon@83.80.159.219) (Quit: getting boxed in)
2025-05-04 02:07:01 +0200hiecaq(~hiecaq@user/hiecaq) hiecaq
2025-05-04 02:09:20 +0200 <Leary> geekosaur: They're "selective"---lazy in the effects of the second argument.
2025-05-04 02:20:31 +0200sajenim(~sajenim@user/sajenim) sajenim
2025-05-04 03:20:58 +0200hiecaq(~hiecaq@user/hiecaq) (Quit: ERC 5.6.0.30.1 (IRC client for GNU Emacs 30.0.92))
2025-05-04 04:13:09 +0200_qw(~eqw@user/eqw) (Ping timeout: 248 seconds)
2025-05-04 04:14:08 +0200_qw(~eqw@user/eqw) eqw
2025-05-04 04:15:49 +0200td_(~td@i53870919.versanet.de) (Ping timeout: 248 seconds)
2025-05-04 04:17:38 +0200td_(~td@i53870915.versanet.de)
2025-05-04 09:26:46 +0200 <dpn`> looks like kovid has added some doco on the issues with xmonad and the panel feature in kitty - doco here https://github.com/kovidgoyal/kitty/blob/master/docs/kittens/panel.rst - the comment is " - doesn't support the needed NET_WM protocols"
2025-05-04 09:32:03 +0200 <dpn`> i added logging around the atom creation and didn't find any errors - will ahve to dig a bit more
2025-05-04 10:37:18 +0200chomwitt-alt(~chomwitt@2a02:587:7a24:7f00:12c3:7bff:fe6d:d374)
2025-05-04 12:52:13 +0200hiecaq(~hiecaq@user/hiecaq) hiecaq
2025-05-04 14:42:42 +0200tremon(~tremon@83.80.159.219) tremon
2025-05-04 17:39:08 +0200hiecaq(~hiecaq@user/hiecaq) (Quit: ERC 5.6.0.30.1 (IRC client for GNU Emacs 30.0.92))
2025-05-04 17:45:40 +0200sajenim(~sajenim@user/sajenim) (Ping timeout: 252 seconds)
2025-05-04 17:50:52 +0200 <geekosaur> so he actually thinks that atoms owned by docks should be created by the window manager? that's GNOME-level BS
2025-05-04 17:51:10 +0200 <geekosaur> GNOME only does it because the wm is the pager is the compositor is the file manager is the everything
2025-05-04 17:52:12 +0200 <geekosaur> and if he's found a way to replace the panel someone over there will probably make it illegal, because you're not permitted to run non-GNOME components
2025-05-04 17:54:13 +0200 <vrs> note that this is the guy who wrote his own suid mount helper (with predictable results) and was one of last holdouts of the python3 migration saying "I'm perfectly capable of maintaining python2 myself"
2025-05-04 17:54:41 +0200 <vrs> (both in calibre)
2025-05-04 17:59:32 +0200 <geekosaur> yeh, I know only too well
2025-05-04 18:00:19 +0200 <geekosaur> the reality is still that docks are self-managing and own their settings and related atoms, we have no business mucking with them
2025-05-04 18:01:02 +0200 <geekosaur> that said, I suppose there could be an XMonad.KovidGoyalDecrees.Atoms contrib that creates his atoms for him
2025-05-04 19:01:53 +0200hightower2(~hightower@213.186.15.36) (Remote host closed the connection)
2025-05-04 21:08:16 +0200chomwitt-alt(~chomwitt@2a02:587:7a24:7f00:12c3:7bff:fe6d:d374) (Ping timeout: 276 seconds)