2025/04/29

Newest at the top

2025-04-29 19:36:15 +0200ft(~ft@p4fc2a6e6.dip0.t-ipconnect.de) ft
2025-04-29 19:33:19 +0200haskellbridge(~hackager@syn-024-093-192-219.res.spectrum.com) hackager
2025-04-29 19:32:01 +0200haskellbridge(~hackager@syn-024-093-192-219.res.spectrum.com) (Ping timeout: 276 seconds)
2025-04-29 17:19:10 +0200 <geekosaur> the reasons have differed over the years. originally it was an issue with the "cashew" that we had to patch around, then it was issues with how they manage their panels that they need to be patched around since they don't care about compatibility with other wms
2025-04-29 16:14:42 +0200Leary(~Leary@user/Leary/x-0910699) Leary
2025-04-29 16:13:12 +0200Leary(~Leary@user/Leary/x-0910699) (Ping timeout: 276 seconds)
2025-04-29 15:20:00 +0200gauge(~gauge@user/gauge) gauge
2025-04-29 15:13:14 +0200gauge(~gauge@user/gauge) (Read error: Connection reset by peer)
2025-04-29 14:30:47 +0200ChubaDuba(~ChubaDuba@46.147.118.125) (Quit: WeeChat 4.6.0)
2025-04-29 13:09:59 +0200DigitteknohippieDigit
2025-04-29 12:58:15 +0200Digit(~user@user/digit) (Ping timeout: 260 seconds)
2025-04-29 12:57:45 +0200ChubaDuba(~ChubaDuba@46.147.118.125) ChubaDuba
2025-04-29 12:56:45 +0200Digitteknohippie(~user@user/digit) Digit
2025-04-29 12:18:50 +0200MrElendig(~Urist@archlinux/op/MrElendig) MrElendig
2025-04-29 12:16:34 +0200MrElendig(~Urist@archlinux/op/MrElendig) (Quit: Brb, going to the moon)
2025-04-29 10:21:50 +0200ft(~ft@p4fc2a6e6.dip0.t-ipconnect.de) (Quit: leaving)
2025-04-29 10:09:31 +0200ChubaDuba(~ChubaDuba@46.147.118.125) (Quit: WeeChat 4.6.0)
2025-04-29 07:57:37 +0200ChubaDuba(~ChubaDuba@46.147.118.125) ChubaDuba
2025-04-29 07:23:22 +0200werneta(~werneta@syn-071-083-160-242.res.spectrum.com) (Ping timeout: 276 seconds)
2025-04-29 06:53:19 +0200DigitteknohippieDigit
2025-04-29 06:27:25 +0200OftenFaded(~OftenFade@user/tisktisk) (Quit: Client closed)
2025-04-29 06:18:40 +0200Digit(~user@user/digit) (Ping timeout: 260 seconds)
2025-04-29 06:17:33 +0200Digitteknohippie(~user@user/digit) Digit
2025-04-29 06:04:39 +0200OftenFaded(~OftenFade@user/tisktisk) OftenFaded
2025-04-29 05:41:15 +0200 <Digit> huh. did not know it's been hard to use a different wm with kde4+. shows how long it's been since i did.
2025-04-29 04:45:21 +0200terrorjack(~terrorjac@2a01:4f8:c17:9d11::) terrorjack
2025-04-29 04:42:48 +0200terrorjack(~terrorjac@2a01:4f8:c17:9d11::) (Quit: The Lounge - https://thelounge.chat)
2025-04-29 04:21:59 +0200td_(~td@i53870912.versanet.de)
2025-04-29 04:20:14 +0200td_(~td@i53870908.versanet.de) (Ping timeout: 252 seconds)
2025-04-29 03:48:49 +0200OftenFaded(~OftenFade@user/tisktisk) (Quit: Client closed)
2025-04-29 03:38:01 +0200 <OftenFaded> I guess an intuitive convention is all that's needed ultimately--I didn't even consider that
2025-04-29 03:35:55 +0200 <geekosaur> for years I just used a convention (actually I still use it to some extent: terminals on 1, editor on 2, mail on 3…)
2025-04-29 03:34:39 +0200 <OftenFaded> last stupid question(for today): How do you good folks navigate/monitor your workspaces without a bar?
2025-04-29 03:20:12 +0200 <geekosaur> occasionally they are, but usually that means the main app and plugins
2025-04-29 03:09:52 +0200 <OftenFaded> This makes sense. I thought apps were to be moreso considered as collections of packages I guess
2025-04-29 02:59:24 +0200 <geekosaur> in this context, "package" is generally a distribution thing that is unrelated to how desktop environment components relate to each other
2025-04-29 02:58:11 +0200 <geekosaur> in particular, most apps will allow any component to provide the services they need, so they can be run under other desktop managers. this is not usually true of core components (except in lxde)
2025-04-29 02:56:58 +0200 <geekosaur> apps don't launch the core components automatically (usually)
2025-04-29 02:56:33 +0200 <geekosaur> the core components are also packages
2025-04-29 02:54:55 +0200 <OftenFaded> you clarified packages as apps, but I thought the wizards preferred the term packages in this context?
2025-04-29 01:16:25 +0200Buliarous(~gypsydang@46.232.210.139) Buliarous
2025-04-29 01:15:58 +0200Buliarous(~gypsydang@46.232.210.139) (Remote host closed the connection)
2025-04-29 00:21:40 +0200rascasse(~rascasse@user/diep) (Remote host closed the connection)
2025-04-29 00:06:02 +0200 <OftenFaded> Oh I see--I was locked in a 'this/that' perspective for a minute
2025-04-28 23:53:15 +0200 <geekosaur> someone would need to write an adapter in JS
2025-04-28 23:52:08 +0200 <geekosaur> but gnome breaks even worse there: it's not possible, the wm has to be a plugin to their DE
2025-04-28 23:51:48 +0200 <geekosaur> "packages" (apps) are fine. it's trying to use it as window manager for the DE that breaks
2025-04-28 23:48:37 +0200 <OftenFaded> so a stable xmonad would stick to gnome/gtk packages instead?
2025-04-28 23:31:45 +0200 <geekosaur> (I mean using xmonad as wm for kde, which was easy in kde2/3 and got harder in kde4+. currently you need to patch and rebuild part of kde, the patch is in our issue tracker)
2025-04-28 23:29:49 +0200rascasse(~rascasse@user/diep) diep