2025/04/29

Newest at the top

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
2025-04-28 23:26:34 +0200 <Digit> xmonad offers so much shiny potential, (and i've explored some, with prior more elaborate configs, even in kde), and yet still manages to be easy to settle down into something simple and practical.
2025-04-28 23:24:29 +0200 <geekosaur> I liked it but I was running on a tiny netbook (600MHz, 2GB!) and it just got too heavy
2025-04-28 23:23:42 +0200 <OftenFaded> geekosaur what made you switch away from kde, if you don't mind me asking?
2025-04-28 23:19:15 +0200 <geekosaur> my basic config has lasted around that long as well, although the github repo doesn't show it. last major change was when I switched away from kde sometime in the late 2000s
2025-04-28 23:16:16 +0200 <Digit> i've basically not changed my xmonad config in over a dozen years. updated, re-wrote once for upgrade, but no change. that's fair sign of having unbroken my workflow from rice squirrelling. :)
2025-04-28 23:12:21 +0200 <OftenFaded> hoping xmonad dethrones i3 for me in this endeavour
2025-04-28 23:11:36 +0200 <OftenFaded> ricing is no longer the focus (don't have the creativity for it). I need to stick with tools that break least often and are most effortlessly repairable when I inevitably do break them.
2025-04-28 23:08:12 +0200m5zs7k(aquares@web10.mydevil.net) m5zs7k
2025-04-28 23:06:48 +0200 <geekosaur> "human fuzzer"
2025-04-28 23:05:38 +0200m5zs7k(aquares@web10.mydevil.net) (Ping timeout: 252 seconds)
2025-04-28 23:00:26 +0200 <Digit> well, you probably dont need one of those to pick a good term for ricing in xmonad, but it helps. sfe ;)
2025-04-28 22:50:15 +0200 <OftenFaded> I can break any and everything without trying too--I may have a neverb4-diagnosed condition
2025-04-28 22:49:55 +0200 <Digit> blunders teach. sometimes they're the right mistakes to make.
2025-04-28 22:49:17 +0200 <Digit> been a st user long time, xterm(/yeahconsole) mostly before that, ... stability never bit me, and so never entered my mind.
2025-04-28 22:49:12 +0200 <OftenFaded> Sorry for asking endless questions. I'm a hobbyist who's blundered my way forward for way too long--trying to do more avoidance of the blunders before they arise you could say
2025-04-28 22:48:22 +0200 <OftenFaded> stability wasn't scored because one shouldn't consider the stability of terms? I guess they are one of the more naturally stable tools in software world
2025-04-28 22:47:08 +0200 <Digit> OftenFaded: urxvt's a fair choice. (I say after re-consulting my spreadsheet to work out my terminal preference: http://ks392457.kimsufi.com/stuff/scrots/2025-04-09-121424_1920x1080_scrot.png ) ... tho alacrity does score 2nd highest overall there. but then i didnt score for stability at all apparently.
2025-04-28 22:41:49 +0200 <L29Ah> OftenFaded: https://github.com/l29ah/misc/blob/master/suck/terminal-emulators#L26 maybe
2025-04-28 22:40:54 +0200 <OftenFaded> wait, should I really be using urxvt in an xmonad env? Is it more stable than alacritty?
2025-04-28 22:39:20 +0200 <Digit> temps, i got in my monitors tmux session. power, i'm always plugged in. if i needed it, sure, i might look into putting that in a bar... maybe tint2. n_n
2025-04-28 22:38:49 +0200 <L29Ah> congrats on increasing your screen estate savings
2025-04-28 22:38:26 +0200 <OftenFaded> well fug, I don't know how yall did that, but I no longer desire the bar life
2025-04-28 22:37:29 +0200 <Digit> got clock on my tmux, got clock on my prompt, got timestamps in irc, got a a gui analog clock in view on my other computer that spends most time on my sound therapy workspace, got clocks on my monitors tab in htop and tmux and likely somewhere else... always somewhere i can see the time in an instant.
2025-04-28 22:37:20 +0200 <geekosaur> (with nothing running, that is)
2025-04-28 22:37:10 +0200 <geekosaur> judging by how fast pids increase on my system, it'd be in the noise
2025-04-28 22:37:05 +0200 <L29Ah> but good enough for a laptop
2025-04-28 22:36:46 +0200 <L29Ah> i must admit though a shell script calling `date` isn't the most energy efficient way to produce the date
2025-04-28 22:36:28 +0200 <geekosaur> xmobar has had a lot of bugs, actually. "all haskell" falls apart when you have to make FFI calls to do anything useful, as you must with any GUI
2025-04-28 22:36:05 +0200 <L29Ah> OftenFaded: urxvt.
2025-04-28 22:36:00 +0200 <OftenFaded> my thoughts exactly lol