2025/04/29

2025-04-29 00:06:02 +0200 <OftenFaded> Oh I see--I was locked in a 'this/that' perspective for a minute
2025-04-29 00:21:40 +0200rascasse(~rascasse@user/diep) (Remote host closed the connection)
2025-04-29 01:15:58 +0200Buliarous(~gypsydang@46.232.210.139) (Remote host closed the connection)
2025-04-29 01:16:25 +0200Buliarous(~gypsydang@46.232.210.139) Buliarous
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 02:56:33 +0200 <geekosaur> the core components are also packages
2025-04-29 02:56:58 +0200 <geekosaur> apps don't launch the core components automatically (usually)
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: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 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 03:20:12 +0200 <geekosaur> occasionally they are, but usually that means the main app and plugins
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: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: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:48:49 +0200OftenFaded(~OftenFade@user/tisktisk) (Quit: Client closed)
2025-04-29 04:20:14 +0200td_(~td@i53870908.versanet.de) (Ping timeout: 252 seconds)
2025-04-29 04:21:59 +0200td_(~td@i53870912.versanet.de)
2025-04-29 04:42:48 +0200terrorjack(~terrorjac@2a01:4f8:c17:9d11::) (Quit: The Lounge - https://thelounge.chat)
2025-04-29 04:45:21 +0200terrorjack(~terrorjac@2a01:4f8:c17:9d11::) terrorjack
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 06:04:39 +0200OftenFaded(~OftenFade@user/tisktisk) OftenFaded
2025-04-29 06:17:33 +0200Digitteknohippie(~user@user/digit) Digit
2025-04-29 06:18:40 +0200Digit(~user@user/digit) (Ping timeout: 260 seconds)
2025-04-29 06:27:25 +0200OftenFaded(~OftenFade@user/tisktisk) (Quit: Client closed)
2025-04-29 06:53:19 +0200DigitteknohippieDigit
2025-04-29 07:23:22 +0200werneta(~werneta@syn-071-083-160-242.res.spectrum.com) (Ping timeout: 276 seconds)
2025-04-29 07:57:37 +0200ChubaDuba(~ChubaDuba@46.147.118.125) ChubaDuba
2025-04-29 10:09:31 +0200ChubaDuba(~ChubaDuba@46.147.118.125) (Quit: WeeChat 4.6.0)
2025-04-29 10:21:50 +0200ft(~ft@p4fc2a6e6.dip0.t-ipconnect.de) (Quit: leaving)
2025-04-29 12:16:34 +0200MrElendig(~Urist@archlinux/op/MrElendig) (Quit: Brb, going to the moon)
2025-04-29 12:18:50 +0200MrElendig(~Urist@archlinux/op/MrElendig) MrElendig
2025-04-29 12:56:45 +0200Digitteknohippie(~user@user/digit) Digit
2025-04-29 12:57:45 +0200ChubaDuba(~ChubaDuba@46.147.118.125) ChubaDuba
2025-04-29 12:58:15 +0200Digit(~user@user/digit) (Ping timeout: 260 seconds)
2025-04-29 13:09:59 +0200DigitteknohippieDigit
2025-04-29 14:30:47 +0200ChubaDuba(~ChubaDuba@46.147.118.125) (Quit: WeeChat 4.6.0)
2025-04-29 15:13:14 +0200gauge(~gauge@user/gauge) (Read error: Connection reset by peer)
2025-04-29 15:20:00 +0200gauge(~gauge@user/gauge) gauge
2025-04-29 16:13:12 +0200Leary(~Leary@user/Leary/x-0910699) (Ping timeout: 276 seconds)
2025-04-29 16:14:42 +0200Leary(~Leary@user/Leary/x-0910699) Leary
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 19:32:01 +0200haskellbridge(~hackager@syn-024-093-192-219.res.spectrum.com) (Ping timeout: 276 seconds)
2025-04-29 19:33:19 +0200haskellbridge(~hackager@syn-024-093-192-219.res.spectrum.com) hackager
2025-04-29 19:36:15 +0200ft(~ft@p4fc2a6e6.dip0.t-ipconnect.de) ft
2025-04-29 20:47:06 +0200OftenFaded(~OftenFade@user/tisktisk) OftenFaded
2025-04-29 21:00:05 +0200L29Ah(~L29Ah@wikipedia/L29Ah) (Ping timeout: 244 seconds)
2025-04-29 21:02:48 +0200Digit(~user@user/digit) (Ping timeout: 252 seconds)
2025-04-29 21:11:44 +0200m5zs7k(aquares@web10.mydevil.net) (Ping timeout: 268 seconds)
2025-04-29 21:14:08 +0200m5zs7k(aquares@web10.mydevil.net) m5zs7k
2025-04-29 21:17:47 +0200L29Ah(~L29Ah@wikipedia/L29Ah) L29Ah
2025-04-29 21:54:39 +0200Digit(~user@69.47.7.51.dyn.plus.net)
2025-04-29 22:19:39 +0200Buliarous(~gypsydang@46.232.210.139) (Remote host closed the connection)
2025-04-29 22:20:09 +0200Buliarous(~gypsydang@46.232.210.139) Buliarous
2025-04-29 22:21:09 +0200Buliarous(~gypsydang@46.232.210.139) (Remote host closed the connection)
2025-04-29 22:21:36 +0200Buliarous(~gypsydang@46.232.210.139) Buliarous
2025-04-29 22:21:56 +0200ghormoon(~ghormoon@ghorland.net) (Ping timeout: 244 seconds)
2025-04-29 22:31:10 +0200OftenFaded(~OftenFade@user/tisktisk) (Quit: Client closed)
2025-04-29 22:47:05 +0200OftenFaded(~OftenFade@user/tisktisk) OftenFaded
2025-04-29 22:47:12 +0200ghormoon(~ghormoon@ghorland.net) ghormoon
2025-04-29 22:51:56 +0200 <OftenFaded> when arranging xmonad keybinds, are there any mappings that should be avoided or any default binds that are best left unchanged?
2025-04-29 22:53:36 +0200 <OftenFaded> or what question should I be asking here? Maybe best practice is to leave all default binds and only add minimally what is helpful?
2025-04-29 22:57:59 +0200 <vrs> mod-shift-space, mod-t and mod-q are pretty important
2025-04-29 22:58:14 +0200 <vrs> especially when experimenting
2025-04-29 23:01:54 +0200 <geekosaur> I have all my added bindings with ctrl added, fwiw
2025-04-29 23:04:57 +0200 <OftenFaded> geekosaur so you keep the defaults as is, and bind all additions to a ctrl + xyz scheme? How do you not run into issues/conflicts with all the apps that have default ctrl keybindings?
2025-04-29 23:05:29 +0200 <geekosaur> no, I add ctrl. so my bindings are mod+ctrl+…
2025-04-29 23:07:01 +0200 <OftenFaded> Ohhh, I see because you can basically hit both with one finger
2025-04-29 23:07:09 +0200 <OftenFaded> I may adopt something similar then
2025-04-29 23:07:37 +0200 <geekosaur> well, not quite because I'm ancient so I always swap caps lock and ctrl 🙂
2025-04-29 23:13:12 +0200 <OftenFaded> damn, thats even more genius--please keep the wisdom rolling
2025-04-29 23:13:57 +0200 <OftenFaded> wait, this just seems logical, what about this comes from being old?
2025-04-29 23:14:02 +0200 <geekosaur> (rockin the 80s 🙂 )
2025-04-29 23:14:41 +0200 <OftenFaded> most are in agreement about all the best art was made in the 80s
2025-04-29 23:32:45 +0200 <fizzie> A number of "Unix" keyboards (at least the Sun Type <some-number> ones I've seen) have caps lock and control swapped compared to the "PC" layout, I imagine that's the "old" part.
2025-04-29 23:50:27 +0200 <geekosaur> yes, that was how 80s engineering workstations and terminals worked. ISO went with the other layout, PCs followed
2025-04-29 23:54:56 +0200 <geekosaur> (because that weas how typewriters were laid out, noting that caps lock was actually shift lock and that nobody imagined typewriters would be obsolete like 5 years later)