| 2022-12-30 01:32:20 +0100 | ectospasm | (~ectospasm@user/ectospasm) (Quit: WeeChat 3.7.1) |
| 2022-12-30 01:33:10 +0100 | ectospasm | (~ectospasm@user/ectospasm) |
| 2022-12-30 01:33:16 +0100 | ectospasm | (~ectospasm@user/ectospasm) (Client Quit) |
| 2022-12-30 01:33:54 +0100 | ectospasm | (~ectospasm@user/ectospasm) |
| 2022-12-30 01:34:29 +0100 | ectospasm | (~ectospasm@user/ectospasm) (Client Quit) |
| 2022-12-30 01:40:19 +0100 | ectospasm | (~ectospasm@user/ectospasm) |
| 2022-12-30 01:40:50 +0100 | ectospasm | (~ectospasm@user/ectospasm) (Client Quit) |
| 2022-12-30 01:54:39 +0100 | xmonadtrack | (~xmonadtra@xmonad/geekosaur) (Remote host closed the connection) |
| 2022-12-30 01:56:19 +0100 | xmonadtrack | (~xmonadtra@069-135-003-034.biz.spectrum.com) |
| 2022-12-30 01:56:20 +0100 | xmonadtrack | (~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host) |
| 2022-12-30 01:56:20 +0100 | xmonadtrack | (~xmonadtra@xmonad/geekosaur) |
| 2022-12-30 02:00:20 +0100 | ectospasm | (~ectospasm@user/ectospasm) |
| 2022-12-30 02:07:55 +0100 | ectospasm | (~ectospasm@user/ectospasm) (Quit: WeeChat 3.7.1) |
| 2022-12-30 02:08:48 +0100 | ectospasm | (~ectospasm@user/ectospasm) |
| 2022-12-30 03:00:40 +0100 | ft | (~ft@i59F5448E.versanet.de) (Ping timeout: 252 seconds) |
| 2022-12-30 03:02:39 +0100 | ft | (~ft@i59F54B83.versanet.de) |
| 2022-12-30 04:02:58 +0100 | banc | (banc@gateway/vpn/protonvpn/banc) (Ping timeout: 268 seconds) |
| 2022-12-30 04:18:23 +0100 | td_ | (~td@83.135.9.29) (Ping timeout: 268 seconds) |
| 2022-12-30 04:19:58 +0100 | td_ | (~td@83.135.9.0) |
| 2022-12-30 04:24:23 +0100 | banc | (banc@gateway/vpn/protonvpn/banc) |
| 2022-12-30 04:47:56 +0100 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Quit: leaving) |
| 2022-12-30 04:48:14 +0100 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2022-12-30 06:18:11 +0100 | [Leary] | (~Leary]@user/Leary/x-0910699) (Ping timeout: 264 seconds) |
| 2022-12-30 06:19:52 +0100 | [Leary] | (~Leary]@user/Leary/x-0910699) |
| 2022-12-30 07:53:16 +0100 | Maeda | (~Maeda@91-161-10-149.subs.proxad.net) (Ping timeout: 252 seconds) |
| 2022-12-30 08:40:05 +0100 | ft | (~ft@i59F54B83.versanet.de) (Quit: leaving) |
| 2022-12-30 08:41:44 +0100 | sogens | (~sogens@103.75.11.26) (Ping timeout: 260 seconds) |
| 2022-12-30 09:33:23 +0100 | ft | (~ft@dynamic-046-114-194-225.46.114.pool.telefonica.de) |
| 2022-12-30 09:52:31 +0100 | defjam | (~defjam@2a02:c7e:2807:b900:4c63:a033:8c58:6225) |
| 2022-12-30 10:00:08 +0100 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2022-12-30 10:04:08 +0100 | defjam | (~defjam@2a02:c7e:2807:b900:4c63:a033:8c58:6225) (Ping timeout: 246 seconds) |
| 2022-12-30 10:06:28 +0100 | mc47 | (~mc47@xmonad/TheMC47) |
| 2022-12-30 10:13:34 +0100 | <mc47> | HB[m] that's an interesting workflow. I rarely have more than two windows on any screen, but I use scratchpads and DynamicWorkspaceGroups _a lot_ |
| 2022-12-30 10:13:46 +0100 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) |
| 2022-12-30 10:17:08 +0100 | defjam | (~defjam@2a02:c7e:2807:b900:4c63:a033:8c58:6225) |
| 2022-12-30 10:21:35 +0100 | defjam | (~defjam@2a02:c7e:2807:b900:4c63:a033:8c58:6225) (Ping timeout: 246 seconds) |
| 2022-12-30 10:24:43 +0100 | <Solid> | that's the beauty of xmonad; it enables to many different types of workflows :) |
| 2022-12-30 10:25:26 +0100 | <Solid> | I remember how surprised liskin was at ZuriHac that our workflows are so different, yet we swear by the same piece of software :D |
| 2022-12-30 10:32:13 +0100 | defjam | (~defjam@2a02:c7e:2807:b900:4c63:a033:8c58:6225) |
| 2022-12-30 10:37:29 +0100 | <HB[m]> | 1920x1080 monitor just doesn't seem large enough to tile a browser with decent window size, terminal, other stuff, etc. etc. |
| 2022-12-30 10:37:29 +0100 | <HB[m]> | If I had a much larger monitor where I could have at least equivalent of 2x2 1920x1080 at least monitors (prefrebly high resolution) so 4 monitors total, prefrebly without bezel, then I would love to use tiling features. I have currently 2x 1920x1080, 24", which is ok but I dunno. Tiling makes windows smaller. 😄 |
| 2022-12-30 10:46:48 +0100 | ft | (~ft@dynamic-046-114-194-225.46.114.pool.telefonica.de) (Quit: leaving) |
| 2022-12-30 11:12:16 +0100 | ft | (~ft@dynamic-046-114-194-225.46.114.pool.telefonica.de) |
| 2022-12-30 11:19:22 +0100 | thyriaen | (~thyriaen@2a01:aea0:dd4:4bae:6245:cbff:fe9f:48b1) |
| 2022-12-30 11:26:03 +0100 | rundown | (~defjam@90.201.240.60) |
| 2022-12-30 11:26:06 +0100 | defjam | (~defjam@2a02:c7e:2807:b900:4c63:a033:8c58:6225) (Ping timeout: 265 seconds) |
| 2022-12-30 11:43:23 +0100 | rundown | (~defjam@90.201.240.60) (Ping timeout: 248 seconds) |
| 2022-12-30 11:44:57 +0100 | rundown | (~defjam@2a02:c7e:2807:b900:482c:53d7:4d7:47cd) |
| 2022-12-30 11:58:59 +0100 | xmonadtrack | (~xmonadtra@xmonad/geekosaur) (Ping timeout: 264 seconds) |
| 2022-12-30 11:59:28 +0100 | allbery_b | (~geekosaur@xmonad/geekosaur) |
| 2022-12-30 11:59:33 +0100 | geekosaur | (~geekosaur@xmonad/geekosaur) (Killed (NickServ (GHOST command used by allbery_b))) |
| 2022-12-30 12:01:28 +0100 | defjam | (~defjam@2a02:c7e:2807:b900:a917:ee8f:a35b:a8a3) |
| 2022-12-30 12:02:05 +0100 | rundown | (~defjam@2a02:c7e:2807:b900:482c:53d7:4d7:47cd) (Ping timeout: 252 seconds) |
| 2022-12-30 12:17:27 +0100 | liskin | uses 13x7 fixed bitmap fonts, makes tiling feasible on a single fhd screen :-) |
| 2022-12-30 12:18:03 +0100 | xmonadtrack | (~xmonadtra@069-135-003-034.biz.spectrum.com) |
| 2022-12-30 12:18:03 +0100 | xmonadtrack | (~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host) |
| 2022-12-30 12:18:03 +0100 | xmonadtrack | (~xmonadtra@xmonad/geekosaur) |
| 2022-12-30 13:03:28 +0100 | ft | (~ft@dynamic-046-114-194-225.46.114.pool.telefonica.de) (Quit: leaving) |
| 2022-12-30 13:13:26 +0100 | defjam | (~defjam@2a02:c7e:2807:b900:a917:ee8f:a35b:a8a3) (Quit: WeeChat 3.7.1) |
| 2022-12-30 14:14:06 +0100 | ft | (~ft@p4fc2a257.dip0.t-ipconnect.de) |
| 2022-12-30 14:24:22 +0100 | thyriaen | (~thyriaen@2a01:aea0:dd4:4bae:6245:cbff:fe9f:48b1) (Quit: Leaving) |
| 2022-12-30 15:14:57 +0100 | Maeda | (~Maeda@91-161-10-149.subs.proxad.net) |
| 2022-12-30 15:45:26 +0100 | allbery_b | geekosaur |
| 2022-12-30 16:18:43 +0100 | jabuxas | (~jabuxas@user/jabuxas) |
| 2022-12-30 16:23:14 +0100 | jab | (~jabuxas@user/jabuxas) |
| 2022-12-30 16:23:20 +0100 | jab | (~jabuxas@user/jabuxas) (Client Quit) |
| 2022-12-30 16:23:48 +0100 | jabuxas | (~jabuxas@user/jabuxas) (Quit: WeeChat 3.6) |
| 2022-12-30 16:34:33 +0100 | jabuxas | (~jabuxas@user/jabuxas) |
| 2022-12-30 16:34:46 +0100 | jabuxas | (~jabuxas@user/jabuxas) (Client Quit) |
| 2022-12-30 16:35:44 +0100 | jabuxas | (~jabuxas@user/jabuxas) |
| 2022-12-30 16:35:57 +0100 | jabuxas | (~jabuxas@user/jabuxas) (Client Quit) |
| 2022-12-30 16:39:41 +0100 | jabuxas | (~jabuxas@user/jabuxas) |
| 2022-12-30 16:45:24 +0100 | jabuxas | (~jabuxas@user/jabuxas) (Quit: WeeChat 2.8) |
| 2022-12-30 16:46:58 +0100 | jabuxas | (~jabuxas@user/jabuxas) |
| 2022-12-30 16:52:31 +0100 | <a[m]1> | Heya |
| 2022-12-30 16:52:37 +0100 | <a[m]1> | Is there an extension for snap tiling? |
| 2022-12-30 17:00:04 +0100 | Dominik[m] | (~dschrempf@2001:470:69fc:105::2:bbb6) (Quit: You have been kicked for being idle) |
| 2022-12-30 17:00:05 +0100 | damhiya[m] | (~damhiyama@2001:470:69fc:105::2:b1a3) (Quit: You have been kicked for being idle) |
| 2022-12-30 17:00:06 +0100 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2022-12-30 17:03:22 +0100 | <geekosaur> | I thinjk the closest we get is `TiledWindowDragging`. xmonad's "thing" is automatic tiling via the `layoutHook` |
| 2022-12-30 17:03:34 +0100 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) |
| 2022-12-30 17:03:49 +0100 | diep | (~diep@2a01:cb11:2d7:4a00:a13f:e40c:c4e8:736c) |
| 2022-12-30 17:06:21 +0100 | diep | (~diep@2a01:cb11:2d7:4a00:a13f:e40c:c4e8:736c) (Remote host closed the connection) |
| 2022-12-30 17:15:56 +0100 | jabuxas | (~jabuxas@user/jabuxas) (Quit: WeeChat 2.8) |
| 2022-12-30 17:18:09 +0100 | jabuxas | (~jabuxas@user/jabuxas) |
| 2022-12-30 18:12:40 +0100 | deip[m] | (~deipmatri@2001:470:69fc:105::2:679e) |
| 2022-12-30 18:59:57 +0100 | Guest19 | (~Guest19@2603-8000-6f00-2842-0000-0000-0000-1673.res6.spectrum.com) |
| 2022-12-30 19:00:43 +0100 | <Guest19> | Hi after a recent update to xmobar I cant seem to prevent my xmobar from overflowing when showing window titles, does anyone know what might be causing this or now to fix it? I have my dotfiles here: https://github.com/jrgiacone/.dotfiles |
| 2022-12-30 19:09:04 +0100 | Guest19 | (~Guest19@2603-8000-6f00-2842-0000-0000-0000-1673.res6.spectrum.com) (Quit: Client closed) |
| 2022-12-30 19:09:55 +0100 | Guest19 | (~Guest19@2603-8000-6f00-2842-0000-0000-0000-1673.res6.spectrum.com) |
| 2022-12-30 19:16:03 +0100 | Guest19 | (~Guest19@2603-8000-6f00-2842-0000-0000-0000-1673.res6.spectrum.com) (Ping timeout: 260 seconds) |
| 2022-12-30 19:26:33 +0100 | Guest19 | (~Guest19@2603-8000-6f00-2842-0000-0000-0000-1673.res6.spectrum.com) |
| 2022-12-30 19:27:15 +0100 | tremon | (~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl) |
| 2022-12-30 19:30:55 +0100 | Guest19 | (~Guest19@2603-8000-6f00-2842-0000-0000-0000-1673.res6.spectrum.com) (Client Quit) |
| 2022-12-30 19:34:13 +0100 | Guest19 | (~Guest19@172-112-225-143.res.spectrum.com) |
| 2022-12-30 19:54:05 +0100 | Guest19 | (~Guest19@172-112-225-143.res.spectrum.com) (Quit: Client closed) |
| 2022-12-30 20:06:33 +0100 | Guest19 | (~Guest19@172-112-225-143.res.spectrum.com) |
| 2022-12-30 20:07:19 +0100 | <Guest19> | please help when i have this for my xmobar the bar keeps growing when more windows are opening pushing modules off the screen: myXmobarPP :: X PP |
| 2022-12-30 20:07:19 +0100 | <Guest19> | myXmobarPP = clickablePP . filterOutWsPP [scratchpadWorkspaceTag] $ def |
| 2022-12-30 20:07:20 +0100 | <Guest19> | ▏ ▏ { ppSep = nordaurora5 " • " |
| 2022-12-30 20:07:20 +0100 | <Guest19> | ▏ ▏ , ppTitleSanitize = xmobarStrip |
| 2022-12-30 20:07:21 +0100 | <Guest19> | ▏ ▏ , ppCurrent = wrap " " "" . xmobarBorder "Top" "#88c0d0" 2 |
| 2022-12-30 20:07:21 +0100 | <Guest19> | ▏ ▏ , ppHidden = nordfrost4 . wrap " " "" |
| 2022-12-30 20:07:22 +0100 | <Guest19> | ▏ ▏ , ppHiddenNoWindows = nordfrost1 . wrap " " "" |
| 2022-12-30 20:07:22 +0100 | <Guest19> | ▏ ▏ , ppUrgent = red . wrap (yellow "!") (yellow "!") |
| 2022-12-30 20:07:23 +0100 | <Guest19> | ▏ ▏ , ppOrder = \[ws, l, _, wins] -> [ws, l, wins] |
| 2022-12-30 20:07:23 +0100 | <Guest19> | ▏ ▏ , ppExtras = [logTitles formatFocused formatUnfocused] |
| 2022-12-30 20:07:24 +0100 | <Guest19> | ▏ ▏ , ppVisible = wrap "[" "]" |
| 2022-12-30 20:07:24 +0100 | <Guest19> | ▏ ▏ } |
| 2022-12-30 20:07:25 +0100 | <Guest19> | ▏ where |
| 2022-12-30 20:07:25 +0100 | <Guest19> | ▏ ▏ formatFocused = wrap (lowWhite "[") (lowWhite "]") . nordsnow1 . ppWindow |
| 2022-12-30 20:07:26 +0100 | <Guest19> | ▏ ▏ formatUnfocused = wrap (lowWhite "[") (lowWhite "]") . nordfrost1 . ppWindow |
| 2022-12-30 20:07:26 +0100 | <Guest19> | ▏ ▏ |
| 2022-12-30 20:07:27 +0100 | <Guest19> | ▏ ▏ -- | Windows should have *some* title, which should not not exceed a |
| 2022-12-30 20:07:27 +0100 | <Guest19> | ▏ ▏ -- sane length. |
| 2022-12-30 20:09:19 +0100 | <geekosaur[m]> | doesn't look like anyone who knows xmobar is active at the moment. it being Friday before New Year's, possibly nobody will be around to help until Tuesday |
| 2022-12-30 20:10:02 +0100 | jrgiacone | (~jrgiacone@172-112-225-143.res.spectrum.com) |
| 2022-12-30 20:11:10 +0100 | <jrgiacone> | no worries I will wait till then I guess, i figured it has to do with xmonad.hs and not my xmobarrc, sorry for repeatedly sending messages I keep getting kicked from the online chat so I just installed irssi |
| 2022-12-30 20:11:21 +0100 | Guest19 | (~Guest19@172-112-225-143.res.spectrum.com) (Client Quit) |
| 2022-12-30 20:11:33 +0100 | twiclo | (~twiclo@vpn.utahbroadband.com) |
| 2022-12-30 20:11:48 +0100 | <twiclo> | Does anyone know what picom setting controls the opacity of the border of the selected window? |
| 2022-12-30 20:21:06 +0100 | <HB[m]> | Xmobarrc sample config, by Hash... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/8a49d4d71081ca2bbab7775559a0ea970e74…>) |
| 2022-12-30 20:21:40 +0100 | <HB[m]> | * Xmobarrc sample config, by Hash... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/045210fdd87a281e20616815610883a857d4…>) |
| 2022-12-30 20:25:57 +0100 | <HB[m]> | * Xmobarrc sample config, by Hash... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/2e36140bceb54dbcdb3b3313d4acb9270867…>) |
| 2022-12-30 20:28:43 +0100 | <HB[m]> | > XMonad.Hooks.StatusBar, XMonad.Hooks.StatusBar.PP (previously XMonad.Hooks.DynamicLog) and XMonad.Util.Run... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/7a7b513606c91e2c489dd0b92cda167e8af6…>) |
| 2022-12-30 20:28:45 +0100 | <lambdabot> | <hint>:1:23: error: parse error on input ‘,’ |
| 2022-12-30 20:28:53 +0100 | <HB[m]> | https://github.com/xmonad/xmonad-contrib/blob/master/CHANGES.md |
| 2022-12-30 20:29:35 +0100 | <HB[m]> | 0.17 introduced changes and dynamic log will be deprecated, so you are encouraged to switch to XMonad.Hooks.StatusBar, XMonad.Hooks.StatusBar.PP |
| 2022-12-30 20:30:55 +0100 | <HB[m]> | https://github.com/xmonad/xmonad-contrib/blob/master/CHANGES.md#new-modules-2 More information |
| 2022-12-30 20:35:08 +0100 | <geekosaur[m]> | twiclo, it doesn't look like picom supports the window borders xmonad uses, only frame window borders |
| 2022-12-30 20:35:56 +0100 | <HB[m]> | I just looked at your xmonad.hs and it seems you're using statusbarpp and also you're using two bars. Seems ... okay.. on a glance. |
| 2022-12-30 20:36:07 +0100 | <HB[m]> | s/on/at/ |
| 2022-12-30 20:36:12 +0100 | <geekosaur[m]> | if you're on xmonad 0.17.0, border opacity will be wrong as part of a workaround for a bug in WindowNavigation that was fixed in 0.17.1 |
| 2022-12-30 20:37:23 +0100 | <HB[m]> | geekosaur[m]: For me? |
| 2022-12-30 20:37:59 +0100 | <twiclo> | How do I update it? |
| 2022-12-30 20:39:22 +0100 | <twiclo> | I guess I gotta download the new release |
| 2022-12-30 20:40:05 +0100 | <HB[m]> | <Guest19> "please help when i have this for..." <- What do you mean it keeps growing? |
| 2022-12-30 20:41:47 +0100 | <HB[m]> | <a[m]1> "Is there an extension for snap..." <- https://xmonad.github.io/xmonad-docs/xmonad-contrib/XMonad-Actions-FloatSnap.html This maybe? So you can snap windows to other windows while dragging, would be floatsnap |
| 2022-12-30 20:42:19 +0100 | <geekosaur[m]> | but that's snap floating, not snap tiling |
| 2022-12-30 20:43:05 +0100 | <HB[m]> | I figured, it may serve that purpose, because you're tiling back/unfloating to other windows/edges etc. |
| 2022-12-30 20:43:24 +0100 | <HB[m]> | Or not? |
| 2022-12-30 20:43:46 +0100 | <geekosaur[m]> | TiledWindowDragging with an appropriate layout might do what they want |
| 2022-12-30 20:45:21 +0100 | <jrgiacone> | HB[m] what i mean is when there are multiple windows in the screen it is pushing all of the modules to the right off the screen even when running a single monitor |
| 2022-12-30 20:45:36 +0100 | <HB[m]> | Snapping doesn't make sense unless you're moving windows using amouse, and when you move the window to adjust it, drag it, that's makes it floated, and then snapped to other edges, then tiled again. |
| 2022-12-30 20:45:36 +0100 | <HB[m]> | That's my thinking on that. So if you're snapping, you're obviously already using a mouse drag. |
| 2022-12-30 20:45:57 +0100 | <jrgiacone> | I tried creating an issue here, but it could be my config, unsure: https://codeberg.org/xmobar/xmobar/issues/655#issuecomment-743436 |
| 2022-12-30 20:46:42 +0100 | <geekosaur[m]> | it drags tiled windows |
| 2022-12-30 20:46:43 +0100 | <geekosaur[m]> | HB, you should look at the module I pointed to |
| 2022-12-30 20:46:54 +0100 | <HB[m]> | I didn't see anything in your config that jumps out to me |
| 2022-12-30 20:46:58 +0100 | <geekosaur[m]> | which will necessarily snap |
| 2022-12-30 20:47:37 +0100 | <HB[m]> | Oh interesting |
| 2022-12-30 20:47:38 +0100 | <HB[m]> | Thanks |
| 2022-12-30 20:47:40 +0100 | <jrgiacone> | it was working until about a month ago after all my git pulls, I haven't been able to trace the last working instance, config hasnt changed in a few months |
| 2022-12-30 20:49:29 +0100 | <HB[m]> | geekosaur: what's difference in floatsnap and tiledwindowdragging? Does tiled window dragging not unfloat somethign while doing so? |
| 2022-12-30 20:50:25 +0100 | <HB[m]> | My understanding was that if something is tiled, it's in tile mode, and to move it around with a mouse, makes it in floated mode, which then you need to put the window back into tiled mode after the dragging/positioning is finished |
| 2022-12-30 20:51:01 +0100 | <HB[m]> | Maybe I don't fully yet understand how Xmonad works under the hodo |
| 2022-12-30 20:51:02 +0100 | <HB[m]> | s/hodo/hood/ |
| 2022-12-30 20:51:39 +0100 | <geekosaur[m]> | normally you are correct. but you can move tiled windows around via terminal in a number of ways and TiledWindowDragging extends that to the mouse |
| 2022-12-30 20:51:55 +0100 | <geekosaur[m]> | this repositions the tiles within the layout |
| 2022-12-30 20:51:55 +0100 | <HB[m]> | I see |
| 2022-12-30 20:52:53 +0100 | <geekosaur[m]> | s/terminal/keyboard/, s//`/, s//`/ |
| 2022-12-30 20:53:23 +0100 | <HB[m]> | * I see. Thank you |
| 2022-12-30 21:02:29 +0100 | <jrgiacone> | what client do yall use to chat on here? |
| 2022-12-30 21:02:53 +0100 | <_Ity[m]> | Element 😔 |
| 2022-12-30 21:03:36 +0100 | <geekosaur[m]> | nheko |
| 2022-12-30 21:03:44 +0100 | <geekosaur[m]> | via flatpak |
| 2022-12-30 21:04:02 +0100 | <geekosaur[m]> | (the one packaged for ubuntu dumps core when checking usernames at login) |
| 2022-12-30 21:04:39 +0100 | <geekosaur[m]> | I also use hexchat but I'm experimenting with running via nheko normally and saving hexchat for when I need to do ops things |
| 2022-12-30 22:44:08 +0100 | jrgiacone | (~jrgiacone@172-112-225-143.res.spectrum.com) (Quit: leaving) |
| 2022-12-30 23:54:12 +0100 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |