2022/04/25

2022-04-25 00:01:24 +0200mvk(~mvk@2607:fea8:5ce3:8500::c90f) (Ping timeout: 240 seconds)
2022-04-25 00:35:34 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection)
2022-04-25 00:39:15 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-04-25 01:20:41 +0200mvk(~mvk@2607:fea8:5ce3:8500::c90f)
2022-04-25 01:42:49 +0200mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2022-04-25 01:51:07 +0200abhixec(~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Quit: brb)
2022-04-25 02:03:18 +0200stackdroid18(~stackdroi@user/stackdroid) (Quit: hasta la vista... tchau!)
2022-04-25 04:05:30 +0200banc(banc@gateway/vpn/airvpn/banc) (Ping timeout: 276 seconds)
2022-04-25 04:08:17 +0200 <abastro[m]> Strange, even default ubuntu installation is suffering from the mouse cursor size problem.
2022-04-25 04:08:36 +0200 <abastro[m]> Thought LightDM was default in ubuntu now..
2022-04-25 04:21:06 +0200Czernobog(~Czernobog@user/czernobog) (Ping timeout: 276 seconds)
2022-04-25 04:21:29 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 04:22:21 +0200banc(banc@gateway/vpn/airvpn/banc)
2022-04-25 04:27:43 +0200byorgey(~byorgey@155.138.238.211)
2022-04-25 04:38:39 +0200td_(~td@muedsl-82-207-238-135.citykom.de) (Ping timeout: 276 seconds)
2022-04-25 04:40:08 +0200td_(~td@94.134.91.109)
2022-04-25 04:49:43 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection)
2022-04-25 04:55:26 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-04-25 05:15:23 +0200 <abastro[m]> Is there a way to show different login UI for xscreensaver?
2022-04-25 05:15:46 +0200 <abastro[m]> gnome-screensaver doesn't seem to work well, and xscreensaver has this scary UI
2022-04-25 05:19:14 +0200 <abastro[m]> Apparently someone else thought similar and done this: https://github.com/unman/qscreensaver
2022-04-25 05:19:17 +0200 <abastro[m]> Hmm
2022-04-25 05:20:29 +0200 <abastro[m]> Actually nvm, I'd not use screensaver and instead use lightdm's one
2022-04-25 05:55:38 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 272 seconds)
2022-04-25 07:05:31 +0200benin(~benin@183.82.204.110)
2022-04-25 07:39:49 +0200tdammers(~tdammers@77.109.72.177.res.static.edpnet.net) (Ping timeout: 240 seconds)
2022-04-25 07:57:14 +0200mvk(~mvk@2607:fea8:5ce3:8500::c90f) (Ping timeout: 250 seconds)
2022-04-25 08:00:00 +0200 <Solid> just use startx :>
2022-04-25 08:36:58 +0200Guest59(~Guest59@70a4-ce62-67d4-784d-2080-841b-07d0-2001.dyn.estpak.ee)
2022-04-25 08:40:29 +0200 <M-elo-[m]> Out of curiosity, is there something similar/equivalent to AwesomeWM's UI library in xmonad? Even written in/for haskell would suffice?
2022-04-25 08:48:56 +0200thunderrd(~thunderrd@183.182.111.40) (Remote host closed the connection)
2022-04-25 09:04:10 +0200 <abastro[m]> Solid: How does it lock the screen when I close the lod?
2022-04-25 09:04:38 +0200 <abastro[m]> -(๐•‚eloฯ„)-: What kind of UI you mean?
2022-04-25 09:08:51 +0200Czernobog(~Czernobog@user/czernobog) (Read error: Connection reset by peer)
2022-04-25 09:08:58 +0200 <M-elo-[m]> abastro[m]: Came across two interesting AwesomeWM setups recently (https://github.com/ChocolateBread799/dotfiles & https://github.com/rxyhn/dotfiles) and if I understood the awesome right then they managed to achieve the their looks through awesome itself
2022-04-25 09:09:23 +0200 <M-elo-[m]> > <@abastro:matrix.org> -(๐•‚eloฯ„)-: What kind of UI you mean?
2022-04-25 09:09:23 +0200 <M-elo-[m]> * Came across two interesting AwesomeWM setups recently (https://github.com/ChocolateBread799/dotfiles & https://github.com/rxyhn/dotfiles) and if I understood their setups right then they managed to achieve the their looks with the help of native awesome features
2022-04-25 09:09:25 +0200 <lambdabot> <hint>:1:1: error: parse error on input โ€˜<@โ€™
2022-04-25 09:09:47 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 09:13:23 +0200 <abastro[m]> Oh, xmonad doesn't even provide the status bar.
2022-04-25 09:14:58 +0200 <abastro[m]> So I doubt it would provide any GUI functionalities.
2022-04-25 09:18:05 +0200 <Solid[m]> abastro[m]: that's just an acpi event, you can decide what to do with that yourself usually
2022-04-25 09:18:18 +0200 <Solid[m]> gilganix[m]: eww is supposed to be gtk widgets regardless of wm I think
2022-04-25 09:18:43 +0200 <M-elo-[m]> slot-[m]: Something native in haskell would be nice ngl
2022-04-25 09:18:55 +0200 <M-elo-[m]> abastro[m]: Yeah and imo that sucks :/
2022-04-25 09:19:06 +0200 <abastro[m]> One can also code in haskell with gtk widgets
2022-04-25 09:19:24 +0200 <M-elo-[m]> Isn't haskell old enough to have it's own gui toolkit though?
2022-04-25 09:19:27 +0200abastro(~abab9579@192.249.26.175)
2022-04-25 09:19:41 +0200 <M-elo-[m]> Strangely enough, no one bothered to make one (except monomer recently)
2022-04-25 09:19:50 +0200 <abastro[m]> slot-[m]: I know the event part, what I don't know is how to lock behind password
2022-04-25 09:19:58 +0200thunderrd(~thunderrd@183.182.111.40)
2022-04-25 09:20:02 +0200 <abastro[m]> Anyway I'm going to use DM's functionality for the lock.
2022-04-25 09:20:06 +0200Czernobog(~Czernobog@user/czernobog) (Ping timeout: 276 seconds)
2022-04-25 09:20:44 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 09:22:24 +0200Guest59(~Guest59@70a4-ce62-67d4-784d-2080-841b-07d0-2001.dyn.estpak.ee) (Quit: Client closed)
2022-04-25 09:36:05 +0200Czernobog(~Czernobog@user/czernobog) (Read error: Connection reset by peer)
2022-04-25 09:36:23 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 09:38:12 +0200dschrempf(~dominik@070-207.dynamic.dsl.fonira.net)
2022-04-25 09:39:01 +0200dschrempf(~dominik@070-207.dynamic.dsl.fonira.net) (Client Quit)
2022-04-25 09:43:17 +0200tv(~tv@user/tv) (Ping timeout: 256 seconds)
2022-04-25 09:52:04 +0200abastro(~abab9579@192.249.26.175) (Remote host closed the connection)
2022-04-25 10:01:23 +0200 <Solid[m]> > <@gilganix[m]:libera.chat> > <@slot-[m]:libera.chat> gilganix[m]: eww is supposed to be gtk widgets regardless of wm I think
2022-04-25 10:01:23 +0200 <Solid[m]> >
2022-04-25 10:01:23 +0200 <Solid[m]> > Something native in haskell would be nice ngl
2022-04-25 10:01:23 +0200 <Solid[m]> I don't think it would be particularly hard to rewrite eww in Haskell (`declarative-gtk` or something exist, although I've never used it)
2022-04-25 10:01:25 +0200 <lambdabot> <hint>:1:18: error: parse error on input โ€˜inโ€™
2022-04-25 10:01:25 +0200 <lambdabot> <hint>:1:1: error: parse error on input โ€˜<@โ€™
2022-04-25 10:01:26 +0200 <Solid[m]> Sounds like a fun project :)
2022-04-25 10:02:05 +0200 <M-elo-[m]> > <@slot-[m]:libera.chat> > <@gilganix[m]:libera.chat> > <@slot-[m]:libera.chat> gilganix[m]: eww is supposed to be gtk widgets regardless of wm I think... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/12c2cf22f6d3ad1281e70184aa8e4319bfdbโ€ฆ)
2022-04-25 10:02:07 +0200 <lambdabot> <hint>:1:1: error: parse error on input โ€˜<@โ€™
2022-04-25 10:02:18 +0200 <M-elo-[m]> what the hell is this lambdabot?
2022-04-25 10:02:26 +0200 <Solid[m]> <abastro[m]> "slot-[m]: I know the event part,..." <- You can execute an arbitrary script on an acpi event afaik
2022-04-25 10:02:34 +0200 <Solid[m]> It's a bot :)
2022-04-25 10:02:47 +0200 <Solid[m]> but it doesn't mash well with matrix citations currently
2022-04-25 10:03:06 +0200 <M-elo-[m]> I knew about the bot part but the second part I did not
2022-04-25 10:03:08 +0200 <M-elo-[m]> Makes sense
2022-04-25 10:03:30 +0200 <M-elo-[m]> I think taffybar could work for what I want, but that feels like cheating lol
2022-04-25 10:03:33 +0200 <Solid[m]> it uses > for executing code
2022-04-25 10:03:50 +0200 <Solid[m]> but taffybar is exactly the pure haskell solution you want :D
2022-04-25 10:04:28 +0200 <abastro[m]> slot-[m]: Yes I could, I meant the locking mechanism itself
2022-04-25 10:04:45 +0200 <M-elo-[m]> slot-[m]: It uses gtk though :P
2022-04-25 10:06:54 +0200 <M-elo-[m]> Alright, heading out ttyl fellas!
2022-04-25 10:12:46 +0200Czernobog(~Czernobog@user/czernobog) (Read error: Connection reset by peer)
2022-04-25 10:14:01 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 10:18:18 +0200tv(~tv@user/tv)
2022-04-25 10:27:08 +0200 <abastro[m]> Hm, lightdm with light-locker is a bit clunky. But it works I guess
2022-04-25 10:27:27 +0200 <abastro[m]> I wonder what is the error messages that comes time to time
2022-04-25 10:39:43 +0200abastro(~abab9579@192.249.26.175)
2022-04-25 10:48:32 +0200abastro(~abab9579@192.249.26.175) (Remote host closed the connection)
2022-04-25 10:55:40 +0200void(~vodage@118.201.231.83)
2022-04-25 10:56:25 +0200voidvodage
2022-04-25 11:12:02 +0200vodage(~vodage@118.201.231.83) (Quit: WeeChat 3.4.1)
2022-04-25 11:12:53 +0200dschrempf(~dominik@070-207.dynamic.dsl.fonira.net)
2022-04-25 11:20:59 +0200Czernobog(~Czernobog@user/czernobog) (Remote host closed the connection)
2022-04-25 11:22:52 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 11:24:45 +0200dschrempf(~dominik@070-207.dynamic.dsl.fonira.net) (Quit: WeeChat 3.4.1)
2022-04-25 11:37:39 +0200 <abastro[m]> Meh, python is so pervasive on the desktop apps
2022-04-25 11:39:31 +0200abastro(~abab9579@192.249.26.175)
2022-04-25 11:50:55 +0200 <davve> is that a bad thing?
2022-04-25 11:51:51 +0200 <abastro[m]> My personal distaste
2022-04-25 11:55:38 +0200abastro(~abab9579@192.249.26.175) (Remote host closed the connection)
2022-04-25 11:57:35 +0200 <abastro[m]> Oh, unity-greeter was enforcing small cursor. Eeh
2022-04-25 12:00:03 +0200abastro(~abab9579@192.249.26.175)
2022-04-25 12:03:03 +0200Czernobog(~Czernobog@user/czernobog) (Read error: Connection reset by peer)
2022-04-25 12:03:46 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 12:07:05 +0200Czernobog(~Czernobog@user/czernobog) (Read error: Connection reset by peer)
2022-04-25 12:07:57 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 12:18:06 +0200abastro(~abab9579@192.249.26.175) (Read error: Connection reset by peer)
2022-04-25 12:19:23 +0200abastro(~abab9579@192.249.26.175)
2022-04-25 12:48:10 +0200Czernobog(~Czernobog@user/czernobog) (Read error: Connection reset by peer)
2022-04-25 12:49:49 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 12:54:56 +0200Czernobog(~Czernobog@user/czernobog) (Quit: ZNC 1.8.2 - https://znc.in)
2022-04-25 12:56:57 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 13:24:42 +0200Czernobog(~Czernobog@user/czernobog) (Read error: Connection reset by peer)
2022-04-25 13:26:36 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 13:29:43 +0200Czernobog(~Czernobog@user/czernobog) (Read error: Connection reset by peer)
2022-04-25 13:30:55 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 13:35:59 +0200steve__(~steve@ool-182c2b80.dyn.optonline.net) (Ping timeout: 240 seconds)
2022-04-25 13:39:26 +0200Czernobog(~Czernobog@user/czernobog) (Read error: Connection reset by peer)
2022-04-25 13:41:46 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 13:56:12 +0200Czernobog(~Czernobog@user/czernobog) (Read error: Connection reset by peer)
2022-04-25 13:57:23 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 13:58:52 +0200tv(~tv@user/tv) (Ping timeout: 272 seconds)
2022-04-25 14:00:28 +0200Czernobog(~Czernobog@user/czernobog) (Read error: Connection reset by peer)
2022-04-25 14:01:25 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 14:02:49 +0200Czernobog(~Czernobog@user/czernobog) (Client Quit)
2022-04-25 14:12:04 +0200tv(~tv@user/tv)
2022-04-25 14:26:21 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 14:27:20 +0200Czernobog(~Czernobog@user/czernobog) (Read error: Connection reset by peer)
2022-04-25 14:27:58 +0200 <geekosaur> has anyone else looked at https://github.com/xmonad/xmonad-contrib/issues/709 yet?
2022-04-25 14:28:49 +0200 <geekosaur> summary: insertPosition requires (and documents) that StackSet actions happen in a specific order so it doesn't misfire; the docks combinator violates this
2022-04-25 14:39:51 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 15:01:31 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-04-25 16:23:54 +0200abastro(~abab9579@192.249.26.175) (Ping timeout: 276 seconds)
2022-04-25 16:54:35 +0200Czernobog(~Czernobog@user/czernobog) (Quit: ZNC 1.8.2 - https://znc.in)
2022-04-25 16:56:25 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 17:05:14 +0200tremon(~tremon@83-84-18-241.cable.dynamic.v4.ziggo.nl)
2022-04-25 17:08:37 +0200Czernobog(~Czernobog@user/czernobog) (Quit: ZNC 1.8.2 - https://znc.in)
2022-04-25 17:08:58 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 17:09:30 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 272 seconds)
2022-04-25 17:32:59 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 240 seconds)
2022-04-25 17:58:25 +0200mvk(~mvk@2607:fea8:5ce3:8500::aa1d)
2022-04-25 18:08:03 +0200 <liskin> geekosaur: I haven't looked at anything as I'm superbusy with other life stuff these days :-(
2022-04-25 18:08:19 +0200 <geekosaur> :(
2022-04-25 18:08:19 +0200 <liskin> but I'm keeping these things as unread in my inbox, if that helps :-)
2022-04-25 18:10:03 +0200 <geekosaur> kinda like I kept your XS PRs in my inbox for a ridiculously long time before I got around to poking at them? :)
2022-04-25 18:19:17 +0200 <liskin> possibly, not sure what your reasons were
2022-04-25 18:19:48 +0200 <liskin> anyway, I'm starting a job this week, so things are getting stable, but not any less busier, so I can't really promise anything
2022-04-25 18:25:10 +0200 <geekosaur> just that they came in at a bad time and then got buried
2022-04-25 18:57:12 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-04-25 19:16:28 +0200Czernobog(~Czernobog@user/czernobog) (Quit: ZNC 1.8.2 - https://znc.in)
2022-04-25 19:17:54 +0200Czernobog(~Czernobog@user/czernobog)
2022-04-25 19:23:01 +0200benin(~benin@183.82.204.110) (Quit: The Lounge - https://thelounge.chat)
2022-04-25 19:39:48 +0200mvk(~mvk@2607:fea8:5ce3:8500::aa1d) (Ping timeout: 240 seconds)
2022-04-25 20:23:37 +0200 <Solid> geekosaur: is it really the docks combinator itself that's causing this, or could it also manifest with just a different ordering of the relevant hooks?
2022-04-25 20:24:48 +0200 <Solid> I feel like the fix would be to make insertPosition properly commutative (if that's even possible...); there may be other hooks it's also incompatible with, given some weird ordering
2022-04-25 20:26:47 +0200 <geekosaur> the documentation for it makes it clear what ordering to use, and if you consider what it does you really do need to order it properly relative to things like doShift or doIgnore
2022-04-25 20:27:16 +0200 <geekosaur> it has code to deal with this, but that code is useless if the shift or ignore, etc. happens *after* the insertPosition
2022-04-25 20:28:07 +0200 <geekosaur> there is no way for it to retroactively clean up the Stack if you do something after it takes effect
2022-04-25 20:28:54 +0200 <Solid> oh I see
2022-04-25 20:29:35 +0200 <geekosaur> this may argue for it being a combinator so it can always insert itself leftmost (remember, composition associates to the right), but docks would still have to insert itself rightmost to not comflict
2022-04-25 20:30:17 +0200 <Solid> mh, I wonder if that would break anything
2022-04-25 20:31:19 +0200 <geekosaur> I doubt it since after doIgnore you can't do anything anyway and arguably doing something before docks is buggy behavior
2022-04-25 20:40:13 +0200 <Solid> sounds about right
2022-04-25 20:40:41 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 246 seconds)
2022-04-25 21:47:37 +0200 <geekosaur> inbox 4. been a while :)
2022-04-25 22:46:23 +0200steve__(~steve@ool-182c2b80.dyn.optonline.net)
2022-04-25 23:16:22 +0200stackdroid18(14094@user/stackdroid)
2022-04-25 23:25:00 +0200mvk(~mvk@2607:fea8:5ce3:8500::aa1d)
2022-04-25 23:38:59 +0200[Leary](~Leary]@122-58-90-96-vdsl.sparkbb.co.nz) (Remote host closed the connection)
2022-04-25 23:40:04 +0200[Leary](~Leary]@122-58-90-96-vdsl.sparkbb.co.nz)