2023/02/21

2023-02-21 00:24:58 +0100 <HB[m]> Hey guys, just thought I'd spread the word, if anyone into self hosting your own services, check out #self-hosting:matrix.org
2023-02-21 00:34:33 +0100 <liskin> Solid: actually Matrix tells me you already are a mod (unless geekosaur made that change meanwhile)
2023-02-21 00:35:24 +0100 <geekosaur> I didn't change anything aside from switching from the #xmonad:libera.chat to #xmonad:matrix.org
2023-02-21 00:35:32 +0100 <HB[m]> <liskin> "the world is indeed getting..." <- I study all the time. I don't even know there is a world otuside 😄
2023-02-21 00:36:39 +0100 <HB[m]> Mostly I rear my head to update the Ubuntu KDE patches for Xmonad 😄
2023-02-21 00:37:03 +0100 <HB[m]> If I'm not around for long periods of time, you can rest assured Xmonad is doing what it's supposed to do, so all is 100% hunky dory
2023-02-21 00:46:08 +0100wuqs(~user@191.177.51.98)
2023-02-21 01:23:09 +0100mncheck(~mncheck@193.224.205.254) (Ping timeout: 268 seconds)
2023-02-21 02:07:03 +0100catman(~catman@user/catman)
2023-02-21 02:08:12 +0100wuqs(~user@191.177.51.98) (Remote host closed the connection)
2023-02-21 02:21:50 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 255 seconds)
2023-02-21 02:47:55 +0100catman(~catman@user/catman) (Quit: WeeChat 3.8)
2023-02-21 02:56:27 +0100catman(~catman@user/catman)
2023-02-21 03:11:49 +0100catman(~catman@user/catman) (Ping timeout: 246 seconds)
2023-02-21 03:40:00 +0100telser(~quassel@user/telser) (Ping timeout: 248 seconds)
2023-02-21 03:40:43 +0100telser(~quassel@user/telser)
2023-02-21 04:02:34 +0100banc(banc@gateway/vpn/protonvpn/banc) (Ping timeout: 246 seconds)
2023-02-21 04:22:31 +0100banc(banc@gateway/vpn/protonvpn/banc)
2023-02-21 04:47:12 +0100td_(~td@i5387093A.versanet.de) (Ping timeout: 248 seconds)
2023-02-21 04:49:18 +0100td_(~td@i5387093F.versanet.de)
2023-02-21 04:51:47 +0100zetabite(~horzion@ProtonDB/horzion) (Remote host closed the connection)
2023-02-21 05:00:00 +0100telser(~quassel@user/telser) (Ping timeout: 248 seconds)
2023-02-21 05:00:22 +0100telser(~quassel@user/telser)
2023-02-21 05:35:01 +0100stackdroid18(14094@de1.hashbang.sh) (Quit: hasta la vista... tchau!)
2023-02-21 05:40:55 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 246 seconds)
2023-02-21 05:41:46 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-02-21 06:02:00 +0100abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 255 seconds)
2023-02-21 06:08:51 +0100abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net)
2023-02-21 08:19:09 +0100zawaken(~zawaken@user/zawaken) (Ping timeout: 255 seconds)
2023-02-21 08:24:14 +0100zawaken(~zawaken@user/zawaken)
2023-02-21 08:55:55 +0100mncheckm(~mncheck@193.224.205.254)
2023-02-21 09:41:24 +0100cfricke(~cfricke@user/cfricke)
2023-02-21 09:51:03 +0100qbt(~qbt@user/edun)
2023-02-21 10:00:25 +0100unclechu(~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle)
2023-02-21 10:00:25 +0100liskin[m](~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
2023-02-21 10:14:15 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2023-02-21 10:47:55 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 260 seconds)
2023-02-21 10:47:58 +0100 <Solid[m]> liskin: ah, I was (i) just in #xmonad:libera.chat, and (ii) I do have moderator in #xmonad:matrix.org, but that does seem to be enough to delete messages
2023-02-21 10:48:09 +0100Solid[m](~slot-matr@2001:470:69fc:105::1:a84) ()
2023-02-21 10:48:26 +0100Solid[m](~slot-matr@2001:470:69fc:105::1:a84)
2023-02-21 10:49:32 +0100 <Solid> geekosaur: there is a code-review package for Emacs, in case you ever want to come back :)
2023-02-21 10:49:45 +0100liskin[m](~liskinmat@2001:470:69fc:105::768)
2023-02-21 10:50:00 +0100unclechu(~unclechu@2001:470:69fc:105::354)
2023-02-21 10:55:34 +0100ft(~ft@p3e9bc443.dip0.t-ipconnect.de) (Quit: leaving)
2023-02-21 11:03:16 +0100 <hellwolf[m]> I am getting myself warming up to trying xmonad... quick question, I have couple of chat programs(telegram, slack,etc.). I usually stack them up in a desktop environment (one behind other). What's the best workflow in xmonad for that instead?
2023-02-21 11:03:58 +0100 <Solid> hellwolf[m]: as in, on their own workspace, or just in general?
2023-02-21 11:04:39 +0100 <hellwolf[m]> My hesitation of imaging tiling them up is they might look too cramped to each other.
2023-02-21 11:04:39 +0100 <hellwolf[m]> And I usually put a firefox window (with emails, several other communication software tabs, etc.) on the right side.
2023-02-21 11:04:43 +0100 <hellwolf[m]> in one single workspace
2023-02-21 11:05:10 +0100 <hellwolf[m]> I have like tons of rt-communication software, be its own software or a firefox tab
2023-02-21 11:05:24 +0100 <hellwolf[m]> I am open to trying out a entire new workflow if it gives with me
2023-02-21 11:06:35 +0100cfricke(~cfricke@user/cfricke) (Ping timeout: 248 seconds)
2023-02-21 11:12:53 +0100 <Solid> I might be misunderstanding you, but to me it sounds like Full should totally suffice?
2023-02-21 12:14:50 +0100MrElendig(~Urist@archlinux/op/MrElendig) (Quit: pumping up some spy baloons)
2023-02-21 12:16:03 +0100MrElendig(~Urist@archlinux/op/MrElendig)
2023-02-21 12:33:50 +0100 <hellwolf[m]> I am new to xmonad (well, not started yet!), what is "Full"?
2023-02-21 12:35:17 +0100 <[Leary]> It's one of the default layouts. It just shows one window at a time, using all the screen space it's given.
2023-02-21 12:39:11 +0100 <hellwolf[m]> I found some sort of tab to cycle through them intuitive too. Or is there any more xmonad-way of doing it?
2023-02-21 12:39:21 +0100 <hellwolf[m]> * I found some sort of tab to cycle through them intuitive too, is it possible? Or is there any more xmonad-way of doing it?
2023-02-21 12:40:06 +0100 <[Leary]> Yes, there's a `tabbed` layout too.
2023-02-21 12:48:44 +0100 <hellwolf[m]> found it, sweet
2023-02-21 13:10:15 +0100nrv(~nrv@user/nrv)
2023-02-21 13:20:16 +0100wuqs(~user@191.177.51.98)
2023-02-21 13:22:20 +0100 <wuqs> there is any other way to disable a shortcut instead of '("shortCut", spawn "")'?
2023-02-21 13:24:31 +0100 <[Leary]> That doesn't actually remove it, since xmonad still steals the keypresses. Try `removeKeysP`.
2023-02-21 13:24:59 +0100 <wuqs> oh yes, lol
2023-02-21 13:25:08 +0100 <wuqs> i have this one commented
2023-02-21 13:25:22 +0100zawaken(~zawaken@user/zawaken) (Ping timeout: 246 seconds)
2023-02-21 13:30:45 +0100nrv(~nrv@user/nrv) (Quit: Ping timeout (120 seconds))
2023-02-21 13:31:07 +0100wuqs(~user@191.177.51.98) (Remote host closed the connection)
2023-02-21 13:32:30 +0100cfricke(~cfricke@user/cfricke)
2023-02-21 13:33:39 +0100zawaken(~zawaken@user/zawaken)
2023-02-21 13:39:39 +0100wuqs(~user@191.177.51.98)
2023-02-21 13:39:47 +0100 <wuqs> hmmm
2023-02-21 13:40:18 +0100 <wuqs> "<XF86PowerOff>", "<XF86PowerDown>" on removeKeysP` apparently does not work
2023-02-21 13:42:42 +0100 <wuqs> or maybe my power button on my laptop actually works like a proper desktop switch
2023-02-21 13:51:13 +0100 <MrElendig> logind or similar might be triggering on them
2023-02-21 13:51:47 +0100 <MrElendig> see logind.conf(5) if you are using systemd
2023-02-21 13:54:26 +0100 <wuqs> MrElendig: [Login]
2023-02-21 13:54:38 +0100 <wuqs> #HandlePowerKey=poweroff
2023-02-21 13:54:49 +0100 <wuqs> should i uncomment it?
2023-02-21 13:55:01 +0100 <MrElendig> change it to whatever you want
2023-02-21 13:55:09 +0100 <MrElendig> poweroff is the default
2023-02-21 13:55:16 +0100 <wuqs> hmm
2023-02-21 13:55:23 +0100 <wuqs> but the #, is not about having it off?
2023-02-21 13:55:34 +0100 <MrElendig> its commented out since it is the default
2023-02-21 13:55:40 +0100 <wuqs> ah, it makes sense
2023-02-21 13:55:46 +0100 <MrElendig> just uncommenting it won't do anything
2023-02-21 13:55:55 +0100 <wuqs> there is any way to parse it to xmonad input?
2023-02-21 13:56:05 +0100 <MrElendig> that doesn't make any sense
2023-02-21 13:56:23 +0100 <wuqs> i would like to set it as default function when i press Shift+Power
2023-02-21 13:56:57 +0100 <MrElendig> HandlePowerKey=ignore and HandlePowerKeyLongPress=poweroff might be a solution then
2023-02-21 13:57:18 +0100 <MrElendig> though a lot of laptops will poweroff on long press as a hardware function anyway
2023-02-21 13:57:41 +0100 <wuqs> o.o
2023-02-21 13:57:44 +0100 <wuqs> thanks!
2023-02-21 14:00:56 +0100nrv(~nrv@user/nrv)
2023-02-21 14:14:48 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2023-02-21 14:17:17 +0100mc47[m](~mc47matri@2001:470:69fc:105::733)
2023-02-21 14:17:51 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 248 seconds)
2023-02-21 14:20:16 +0100 <mc47[m]> What are actually the problems/shortcomings of xmonad's floating layer?
2023-02-21 14:31:54 +0100nrv(~nrv@user/nrv) (Quit: Client closed)
2023-02-21 14:35:34 +0100c0c0(~coco@212.51.146.137)
2023-02-21 14:46:28 +0100c0c0(~coco@212.51.146.137) (Quit: WeeChat 3.7.1)
2023-02-21 14:52:28 +0100 <geekosaur> the biggest is that floats are part of the workspace Stack, so they rotate along with window focus in ways that are really hard to control. the second biggest is that you can't raise a tiled window over them, so they're always in the way
2023-02-21 15:31:46 +0100 <mc47[m]> Hmmm, I'm not sure how to avoid the first point
2023-02-21 15:32:31 +0100 <mc47[m]> I mean, I want to be able to focus and manipulate float windows with key bindings
2023-02-21 15:33:03 +0100 <mc47[m]> (In general, not in xmonad per se)
2023-02-21 15:34:10 +0100 <geekosaur> sure, but there has to be a better way than quasi-random floats flashing at you as you rotate through tiled windows
2023-02-21 15:34:39 +0100 <geekosaur> they're not a real layer, they just fail to act like one
2023-02-21 15:36:03 +0100catman(~catman@user/catman)
2023-02-21 15:46:28 +0100 <[Leary]> mc47[m], geekosaur: In my design, there's a `Layers m1 m2` combinator akin to `|||`, combining models `m1` and `m2` such that the focused one of the two displays above the other. Any `m` can be augmented with a floating layer using `Layers (Floating a) m`, so it can be pushed up to become workspace independent, pushed down to stick transients to their parents, etc. `Layers` would support transformations (messages) to toggle focus and management of win
2023-02-21 15:46:28 +0100 <[Leary]> dows between the two layers, etc. Each submodel has the responsibility to track its own focus, so you can rotate through one without disturbing the other.
2023-02-21 16:03:23 +0100 <mc47[m]> That actually sounds pretty neat
2023-02-21 16:30:34 +0100cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.8)
2023-02-21 16:53:30 +0100catman(~catman@user/catman) (Ping timeout: 255 seconds)
2023-02-21 17:00:05 +0100unclechu(~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle)
2023-02-21 17:00:05 +0100liskin[m](~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
2023-02-21 17:06:39 +0100banc(banc@gateway/vpn/protonvpn/banc) (Ping timeout: 255 seconds)
2023-02-21 17:07:34 +0100banc(banc@gateway/vpn/protonvpn/banc)
2023-02-21 17:22:55 +0100 <galactic_starfis> my tree idea has something similar
2023-02-21 17:23:31 +0100 <galactic_starfis> though it sounds like yours is probably better implemented within monadic space
2023-02-21 17:26:50 +0100 <galactic_starfis> anyway, what is the best way for me to bind a key that I'm unsure of the keysym/name of? xev calls it Menu/135 but I can't figure out the ezconfig string for it...
2023-02-21 17:26:58 +0100 <galactic_starfis> what's the best way for me to identify that?
2023-02-21 17:40:25 +0100 <geekosaur> mm, I think you have a problem with EZConfig. old style it's xK_Menu
2023-02-21 17:40:38 +0100liskin[m](~liskinmat@2001:470:69fc:105::768)
2023-02-21 17:40:51 +0100unclechu(~unclechu@2001:470:69fc:105::354)
2023-02-21 17:54:48 +0100banc(banc@gateway/vpn/protonvpn/banc) (Ping timeout: 255 seconds)
2023-02-21 17:55:39 +0100banc(banc@gateway/vpn/protonvpn/banc)
2023-02-21 17:58:28 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-02-21 18:01:46 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Client Quit)
2023-02-21 18:48:46 +0100werneta(~werneta@137.79.195.231)
2023-02-21 20:33:23 +0100wuqs(~user@191.177.51.98) (Quit: ERC (IRC client for Emacs 27.1))
2023-02-21 20:56:26 +0100ft(~ft@p3e9bc443.dip0.t-ipconnect.de)
2023-02-21 21:01:36 +0100qbt(~qbt@user/edun) (Ping timeout: 268 seconds)
2023-02-21 23:04:31 +0100 <galactic_starfis> [Leary]: how close is your solution to a minimum viable product using just core?
2023-02-21 23:08:50 +0100hightower2(~hightower@141-136-228-229.dsl.iskon.hr)
2023-02-21 23:15:15 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) ()
2023-02-21 23:21:15 +0100 <[Leary]> galactic_starfis: I'm not completely sure what you're asking? I have the underlying application framework, but I'm still feeling out the process of working in it by writing the basic models needed to replace the windowset.
2023-02-21 23:45:09 +0100catman(~catman@user/catman)