2023-03-29 00:16:04 +0200 | L29Ah | (~L29Ah@wikipedia/L29Ah) |
2023-03-29 01:02:38 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
2023-03-29 01:24:40 +0200 | catman | (~catman@user/catman) |
2023-03-29 01:27:28 +0200 | chomwitt | (~chomwitt@athedsl-346372.home.otenet.gr) (Ping timeout: 265 seconds) |
2023-03-29 02:17:15 +0200 | catman | (~catman@user/catman) (Ping timeout: 248 seconds) |
2023-03-29 03:50:02 +0200 | rekahsoft | (~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-142.dsl.bell.ca) |
2023-03-29 03:50:41 +0200 | rekahsoft | (~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-142.dsl.bell.ca) (Remote host closed the connection) |
2023-03-29 03:51:19 +0200 | rekahsoft | (~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-142.dsl.bell.ca) |
2023-03-29 04:12:29 +0200 | catman | (~catman@user/catman) |
2023-03-29 04:29:54 +0200 | td_ | (~td@i5387093D.versanet.de) (Ping timeout: 255 seconds) |
2023-03-29 04:31:41 +0200 | td_ | (~td@i53870923.versanet.de) |
2023-03-29 04:58:12 +0200 | catman | (~catman@user/catman) (Ping timeout: 265 seconds) |
2023-03-29 06:15:32 +0200 | rekahsoft | (~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-142.dsl.bell.ca) (Ping timeout: 265 seconds) |
2023-03-29 07:45:12 +0200 | chomwitt | (~chomwitt@2a02:587:7a0f:e00:1ac0:4dff:fedb:a3f1) |
2023-03-29 07:50:16 +0200 | thunderrd | (~thunderrd@183.182.114.86) (Ping timeout: 265 seconds) |
2023-03-29 08:11:44 +0200 | <Solid> | oh, right :) |
2023-03-29 08:17:13 +0200 | <Solid> | guess we can always rename the branch when its time |
2023-03-29 08:29:57 +0200 | ft | (~ft@p3e9bc443.dip0.t-ipconnect.de) (Quit: leaving) |
2023-03-29 08:31:34 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 255 seconds) |
2023-03-29 08:33:15 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
2023-03-29 08:41:21 +0200 | mncheck | (~mncheck@193.224.205.254) |
2023-03-29 09:41:09 +0200 | <liskin> | Solid: yeah you'll need to cherry-pick enough of the CI commits to make github show a green tick for the head commit in that branch |
2023-03-29 09:41:34 +0200 | <liskin> | I mean, getting the haskell-ci workflow green *should* be enough for the release, but… |
2023-03-29 09:43:31 +0200 | <liskin> | (If we wanted to be super robust we'd need a release branch naming scheme and change the packdeps and generatemanpage workflows to run on release branches as well but in this case we can run packdeps manually and generatemanpage isn't needed.) |
2023-03-29 10:06:37 +0200 | <xmonadtrack> | xmonad-contrib Tony Zorman * v0.17.1-143-gfb63987a: X.Prompt: Factor out how to accept the current selection (2 hours ago, 1 file, 11+ 7-) https://github.com/xmonad/xmonad-contrib/commit/fb63987ac89c |
2023-03-29 10:06:39 +0200 | <xmonadtrack> | xmonad-contrib Tony Zorman * v0.17.1-144-gf127f71c: X.Prompt: Alias C-m to RET in Emacs/Vim bindings (2 hours ago, 2 files, 9+ 0-) https://github.com/xmonad/xmonad-contrib/commit/f127f71c914a |
2023-03-29 10:17:17 +0200 | <wz1000> | can xmonad handle REL_WHEEL_HI_RES events? https://www.kernel.org/doc/html/latest/input/event-codes.html#ev-rel |
2023-03-29 10:17:40 +0200 | <wz1000> | It doesn't seem so after adding tracing to the event hook |
2023-03-29 10:17:48 +0200 | shinjipf | (~shinjipf@159.65.131.14) (Quit: Shinji leaves) |
2023-03-29 10:19:59 +0200 | <wz1000> | I'm trying to fix a bug where if I have a device that advertises these events, and also have regular mouse wheel scroll events bound in xmonad, the hi res versions are not grabbed by xmonad and instead passed through to the underlying window (so the xmonad action is triggered but firefox also scrolls) |
2023-03-29 10:20:29 +0200 | <wz1000> | I guess that xmonad doesn't use xinput2 or evdev so doesn't know about these events |
2023-03-29 10:31:40 +0200 | <geekosaur> | correct |
2023-03-29 10:38:48 +0200 | <geekosaur> | you could conceivably mask for those events in startupHook but you'd have to modify the X11 library to recognize them the same way liskin had to modify it to recognize XRandR events. conceivably we could crash without that, since if we received an XI2 event the X11 lib wouldn't know what to do with it |
2023-03-29 10:42:19 +0200 | <geekosaur> | and it might even use more memory than is reserved for a received event which would corrupt the heap |
2023-03-29 10:43:25 +0200 | <geekosaur> | (I don't really like how X11 lib deals with events, but that ship sailed in xmonad 0.1) |
2023-03-29 10:44:16 +0200 | L29Ah | (~L29Ah@wikipedia/L29Ah) (Ping timeout: 252 seconds) |
2023-03-29 10:44:17 +0200 | <geekosaur> | or even whenever the original X11 bindings were written because it's that that expect an `alloca`d buffer for `nextEvent` |
2023-03-29 10:49:29 +0200 | shinjipf | (~shinjipf@137.184.4.49) |
2023-03-29 10:50:10 +0200 | shinjipf | (~shinjipf@137.184.4.49) (Client Quit) |
2023-03-29 10:50:38 +0200 | shinjipf | (~shinjipf@137.184.4.49) |
2023-03-29 11:00:06 +0200 | deip[m] | (~deipmatri@2001:470:69fc:105::2:679e) (Quit: You have been kicked for being idle) |
2023-03-29 11:00:37 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
2023-03-29 11:22:10 +0200 | real-fht[m] | (~real-fhtm@2001:470:69fc:105::2:d597) |
2023-03-29 11:27:15 +0200 | <real-fht[m]> | is it possible to combine different actions in a single manageHook match? |
2023-03-29 11:27:22 +0200 | <real-fht[m]> | (for example, run doShift and doFloat) |
2023-03-29 11:42:05 +0200 | <geekosaur> | use <+> or >> |
2023-03-29 11:42:22 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) |
2023-03-29 11:42:42 +0200 | <geekosaur> | or <> which is the new spelling for <+> |
2023-03-29 11:43:15 +0200 | <geekosaur> | some things need to happen in a particular order (https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs#L281-L282) |
2023-03-29 11:44:31 +0200 | <geekosaur> | https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs#L162-L163 is an example within a manageHook |
2023-03-29 12:39:00 +0200 | Ou42 | (~Ou4242a@2600:1700:e930:41b0:65bd:94a:d3f4:d966) |
2023-03-29 12:41:12 +0200 | <Ou42> | Hello! ( XY prob(s) will abound... ) I think what I want is to be able to change to a dark theme and increase the font size in xmessage, is this possible? and/or can it be replaced w/ something that has those features? |
2023-03-29 12:46:51 +0200 | <Ou42> | OK I just now found this: <https://gist.github.com/SilverSoldier/739433e99b291f2f818bc556b00780a3> but how to use it w/ xmonad? |
2023-03-29 12:50:10 +0200 | <geekosaur> | I use https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmessage (warning: perl) which accepts xmessage options and translates to zenity, which will use your gtk theme |
2023-03-29 12:52:17 +0200 | <Ou42> | geekosaur: TYVM! That said, I'm only familiar w/ perl in name only. ( I'm running xmonad ATM so I'm a bit slow flipping back / forth ) |
2023-03-29 12:52:47 +0200 | <Ou42> | I'm basically in "Couch OS" ATM -- laptop connected to TV |
2023-03-29 12:52:50 +0200 | <Solid> | Ou42: you can, in principle specify any executable via $XMONAD_XMESSAGE (see https://github.com/xmonad/xmonad/blob/master/src/XMonad/Core.hs#L457 ) |
2023-03-29 12:53:07 +0200 | <Solid> | you'd just need to take care of either doing something with, or ignoring the xmessage-specific arguments that we give it |
2023-03-29 12:54:00 +0200 | <Ou42> | Solid: there it is! I think! the link I found -- right after joining the chan of course! -- states that the fg/bg color args aren't in the man page. |
2023-03-29 12:54:09 +0200 | <Ou42> | ... so that might be the easiest way. |
2023-03-29 12:55:10 +0200 | <geekosaur> | a lot of standard (for old-style X programs) options are in X(7) instead of every program's manpage |
2023-03-29 12:55:20 +0200 | <geekosaur> | (which kinda sucks) |
2023-03-29 12:57:52 +0200 | <Ou42> | one moment |
2023-03-29 13:00:08 +0200 | <Ou42> | OK, I'm learning... maybe?! so that would be "man 7 X" ? |
2023-03-29 13:00:18 +0200 | <geekosaur> | yes |
2023-03-29 13:00:24 +0200 | <Ou42> | I didn't find mention of xmessage, but did find -fg |
2023-03-29 13:00:36 +0200 | <Ou42> | cool beans. |
2023-03-29 13:00:48 +0200 | <geekosaur> | look for OPTIONS |
2023-03-29 13:01:18 +0200 | <geekosaur> | it won't mention individual programs; it lists the options that all old-style X11 programs take |
2023-03-29 13:02:07 +0200 | <geekosaur> | (so it doesn't include things like -fn because not all programs use fonts) |
2023-03-29 13:03:52 +0200 | <Ou42> | interesting |
2023-03-29 13:04:12 +0200 | <Ou42> | Now I realize I hsould have followed the xmonad tutorial more closely and installed the screen cap feature. ;o) |
2023-03-29 13:05:09 +0200 | <geekosaur> | if you want to go the .Xresources route (why do they even mention .Xdefaults? that was X10 and SunOS 3/4) you can specify a font the way they show in that paste, making sure you install the adobe server-side fonts so the fontspec works (most linuxes don't install them by default these days |
2023-03-29 13:05:49 +0200 | <geekosaur> | you can also specify -fg/-bg as `Xmessage*foreground` and `Xmessage*background` in the .Xresources file |
2023-03-29 13:07:04 +0200 | <Ou42> | you're beating me to my Q's. |
2023-03-29 13:07:06 +0200 | <Ou42> | ha! |
2023-03-29 13:07:49 +0200 | <Ou42> | I was gonna go the environ var path, but I'll try that first |
2023-03-29 13:07:54 +0200 | <geekosaur> | it's xfonts-scalable on debian/ubuntu/mint, I don't know for other distros |
2023-03-29 13:09:03 +0200 | <Ou42> | before I go too far down this rabbit hole, is this the right problem? Or is there a more naive/idomatic way of switching to a dark theme while using xmonad? |
2023-03-29 13:09:39 +0200 | <Ou42> | ... like for instance, do y'all just close xmessage and open the log in a term instead? |
2023-03-29 13:09:40 +0200 | <geekosaur> | the default programs used by xmonad don't have a concept of themes, really |
2023-03-29 13:10:04 +0200 | L29Ah | (~L29Ah@wikipedia/L29Ah) |
2023-03-29 13:10:17 +0200 | <geekosaur> | that's why I have a wrapper for xmessage that runs zenity, because gtk programs have themes |
2023-03-29 13:11:28 +0200 | <Solid> | Ou42: I've never thought about this, but my xmessage has had a dark background ever since I can remember |
2023-03-29 13:11:48 +0200 | <Solid> | and I don't know why :) |
2023-03-29 13:12:12 +0200 | <Ou42> | oh c'mon, aren't you curious? |
2023-03-29 13:12:33 +0200 | <Ou42> | maybe you asked this same Q years ago and you are using geekosaur's perl script?! :oD |
2023-03-29 13:13:00 +0200 | <Ou42> | I'm not bash-ing any languages here. |
2023-03-29 13:13:07 +0200 | <Solid> | hah, no I'm definitely not |
2023-03-29 13:14:20 +0200 | <Solid> | Mh, I still have `*.background: #32302f` in my Xresources back from when I was still using urxvt |
2023-03-29 13:14:29 +0200 | <Solid> | so I guess that'd be it? |
2023-03-29 13:14:31 +0200 | <Ou42> | I'm slow and the theme change is annoying, but I'll learn. this is my 2nd attempt at using xmonad. I have a little haskell experience. Not a guru by any stretch, but thought I'd be OK ... but jumped too far ahead trying to get DistroTubes setup. |
2023-03-29 13:14:39 +0200 | <Ou42> | Now I'm going thru the tutorial as I should have. |
2023-03-29 13:14:46 +0200 | <Ou42> | w/ a very tiny xmonad.hs |
2023-03-29 13:14:54 +0200 | <Solid> | going through the tutorial is always a good idea :) |
2023-03-29 13:15:00 +0200 | <geekosaur> | Solid: yes |
2023-03-29 13:15:22 +0200 | <Solid> | maybe we should mention how to at least get rid of the white background there |
2023-03-29 13:26:04 +0200 | <Ou42> | progress! |
2023-03-29 13:26:14 +0200 | <Ou42> | TY Solid & geekosaur !! |
2023-03-29 13:27:20 +0200 | <Ou42> | OK, next Q and hold onto your seats ... per the tut one can create ( I'm not that familiar w/ the ||| operator ) a "list" of Layouts |
2023-03-29 13:28:25 +0200 | <Ou42> | AFAICT, this works fine if the Layouts are all non-decorated, but if I try to append `||| tabbed` it doesn't work, is this the correct interpretation? |
2023-03-29 13:29:36 +0200 | <Ou42> | <https://hackage.haskell.org/package/xmonad-contrib-0.16/docs/XMonad-Util-Themes.html> |
2023-03-29 13:35:26 +0200 | <geekosaur> | tabbed is a layout modifier that takes parameters; you can't use it by itself |
2023-03-29 13:35:50 +0200 | <geekosaur> | there is simpleTabbed which provides default parameters and a default underlying layout (Simplest) |
2023-03-29 13:36:49 +0200 | <geekosaur> | oh, no layout, just a shrinker and a formatter. https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs#L290 |
2023-03-29 13:43:34 +0200 | Ou42 | reading |
2023-03-29 13:49:18 +0200 | <geekosaur> | only that one line matters; the stuff following is unrelated and the Renamed is just to drop the "Simplest" when I display the layout in my status bar |
2023-03-29 13:50:33 +0200 | <geekosaur> | that said, I use a lot of xmonad features so you might be interested in going through my whole config to try to understand it 🙂 |
2023-03-29 14:00:53 +0200 | Ou42 | is (slowly) documenting this ... |
2023-03-29 14:10:12 +0200 | <Ou42> | geekosaur: It'll take me some time to sift thru your code, but much appreciated! |
2023-03-29 14:17:11 +0200 | <geekosaur> | I think all of us have our configs up, listed in the README. mine uses more stuff but is straightforward; liskin's has more experimental stuff in it |
2023-03-29 14:17:28 +0200 | <geekosaur> | (sorry I disappeared; let's just say I had to take a pepto bismol break) |
2023-03-29 14:18:15 +0200 | <Ou42> | I call it the "office" |
2023-03-29 14:19:25 +0200 | L29Ah | (~L29Ah@wikipedia/L29Ah) () |
2023-03-29 14:21:16 +0200 | <Ou42> | Well, I'm an eternal noob. I've made some progress w/ Haskell, but my eyes were bigger than my brain jumping too far ahead w/ xmonad. Now I (mostly) followed the tutorial off the xmonad.org ... |
2023-03-29 14:21:42 +0200 | <Ou42> | ... I just issued `xmonad --recompile` for the first time ... it worked! Lack of faith? |
2023-03-29 14:21:47 +0200 | <Ou42> | Now I'll break something and try it again. |
2023-03-29 14:21:49 +0200 | fnurglewitz | (uid263868@id-263868.lymington.irccloud.com) |
2023-03-29 14:21:50 +0200 | <Ou42> | brb |
2023-03-29 14:23:50 +0200 | <Ou42> | it still opens up an xmessage, but it does spit out the error msgs in the terminal too, so it's a win in my book. |
2023-03-29 14:24:29 +0200 | <Ou42> | ( re: xmessage: I did get the colors inverted, so it does look better. ) |
2023-03-29 14:25:18 +0200 | <geekosaur> | they should also be in xmonad.errors somewhere (~/.xmonad or ~/.local/share/xmonad/xmonad.errors) |
2023-03-29 14:25:45 +0200 | <geekosaur> | er, ~/.xmonad/xmonad.errors |
2023-03-29 14:26:15 +0200 | <Ou42> | thx! |
2023-03-29 14:26:43 +0200 | <Ou42> | I just remembered my next Q: I don't normally use `stack` and just tinker in ghci ... |
2023-03-29 14:27:35 +0200 | <Ou42> | part of my prev issue(s) were conflicting info online due to different xmonad versions and my stack setup not loading the correct ghc ver |
2023-03-29 14:27:50 +0200 | <Ou42> | but now that I'm starting "small" and building up no errors and things are building / working |
2023-03-29 14:28:23 +0200 | <Ou42> | but here's my Q: can I check the types so I can debug why I can't combine the layouts? |
2023-03-29 14:28:35 +0200 | <Ou42> | in ghci using `:t`? |
2023-03-29 14:28:55 +0200 | <geekosaur> | use `stack ghci` in your xmonad directory |
2023-03-29 14:29:09 +0200 | <Ou42> | ok one sec |
2023-03-29 14:29:24 +0200 | <geekosaur> | beware that layout types tend to be huge and complicated |
2023-03-29 14:31:00 +0200 | <geekosaur> | I've been using vscode to edit my config of late (this requires a full stack or cabal setup, not the quick and dirty one from INSTALL / TUTORIAL, or vscode won't find xmonad) and layout types are pretty horrifying |
2023-03-29 14:31:04 +0200 | <Ou42> | ugh. it tried to compile 319 things |
2023-03-29 14:31:13 +0200 | <Ou42> | lots of warnigns, then an error on ... |
2023-03-29 14:31:38 +0200 | <Ou42> | "[ 45 of 319] Compiling XMonad.Layout.MessageControl" |
2023-03-29 14:31:41 +0200 | <geekosaur> | hm, I don't think it should need to recompile |
2023-03-29 14:32:06 +0200 | <Ou42> | it did it automatically after issuing "stack ghci" |
2023-03-29 14:32:15 +0200 | <Ou42> | but like I said, I think I have my stack installation borked |
2023-03-29 14:32:24 +0200 | <Ou42> | that's for another day |
2023-03-29 14:32:34 +0200 | <Ou42> | I gotta catch some Z's before the sun comes up |
2023-03-29 14:32:49 +0200 | <Ou42> | Thanks again for the help! |
2023-03-29 14:36:15 +0200 | <Ou42> | ps - if I get to it, this might be my next foray: <https://www.reddit.com/r/xmonad/comments/hot295/xmonad_is_not_using_system_theme_settings/> |
2023-03-29 14:36:24 +0200 | <Ou42> | g'nite and thanks for all the ... monads? |
2023-03-29 14:37:01 +0200 | Ou42 | (~Ou4242a@2600:1700:e930:41b0:65bd:94a:d3f4:d966) (Quit: Leaving) |
2023-03-29 15:04:29 +0200 | haskl[error] | (~haskl@user/haskl) (Read error: Connection reset by peer) |
2023-03-29 15:07:28 +0200 | haskl | (~haskl@user/haskl) |
2023-03-29 15:19:57 +0200 | Ou42 | (~Ou4242a@2600:1700:e930:41b0:65bd:94a:d3f4:d966) |
2023-03-29 15:20:07 +0200 | <Ou42> | I couldn't let it go... |
2023-03-29 15:20:21 +0200 | <Ou42> | I found / fixed one of my errors/mistakes |
2023-03-29 15:20:27 +0200 | <Ou42> | but the other persists |
2023-03-29 15:20:39 +0200 | <geekosaur> | @where paste |
2023-03-29 15:20:39 +0200 | <lambdabot> | Help us help you: please paste full code, input and/or output at e.g. https://paste.tomsmeding.com |
2023-03-29 15:21:12 +0200 | <Ou42> | https://gist.github.com/Ou42/6355010c1829b7097b1fcf602b8c4beb |
2023-03-29 15:21:34 +0200 | <Ou42> | that's the hard to kill error |
2023-03-29 15:22:07 +0200 | <Ou42> | the mistake I fixed was "tabbed = tabbed ..." <== not allowed to use a func name as a binding? I s'pose |
2023-03-29 15:23:05 +0200 | <geekosaur> | oh, that's much worse. the `tabbed` on both sides of the `=` are the same, so it would try to find the least fixed point. which in practice means an infinite loop 🙂 |
2023-03-29 15:23:16 +0200 | <geekosaur> | so even if it had typechecked it would have failed |
2023-03-29 15:23:51 +0200 | <Ou42> | \o? |
2023-03-29 15:23:53 +0200 | <geekosaur> | in any case, yes, you can't reuse the name. which is why I stuck a `q` on the front of mine |
2023-03-29 15:24:05 +0200 | <Ou42> | grrr. \o// |
2023-03-29 15:24:38 +0200 | <geekosaur> | > let ones = 1:ones in ones |
2023-03-29 15:24:40 +0200 | <lambdabot> | [1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1... |
2023-03-29 15:24:58 +0200 | <geekosaur> | > let x = x in x |
2023-03-29 15:25:00 +0200 | <lambdabot> | *Exception: <<loop>> |
2023-03-29 15:25:01 +0200 | <Ou42> | but why can't the compiler infer the types when I have them "outside" that where clause? |
2023-03-29 15:26:27 +0200 | <Ou42> | my xmonad.hs is below the error output |
2023-03-29 15:28:50 +0200 | <geekosaur> | it can't infer types for layouts very well, especially in the case where they're not used |
2023-03-29 15:29:07 +0200 | <Ou42> | :lightbulb: |
2023-03-29 15:29:28 +0200 | <Ou42> | it needs to be used for it to infer the type! gotcha! |
2023-03-29 15:29:40 +0200 | <Ou42> | I think I can sleep on that. |
2023-03-29 15:29:47 +0200 | <geekosaur> | a layout has as its most general type `LayoutClass l => l Window`. typeclasses tend to break type inference |
2023-03-29 15:30:25 +0200 | <geekosaur> | (note that you can't give a layout that type; you need to give it a type compatible with that type, but specific to the layout |
2023-03-29 15:31:22 +0200 | <Ou42> | I grok maybe a 1/3 of what you're saying... so I'll still have to sleep on it. But I def grok the point about needing to have the thing used for the compiler to make the right assumptions. |
2023-03-29 15:32:09 +0200 | <geekosaur> | well, let's just say that it only has half the information it needs to infer a type. the other half it has to get from use providing that `LayoutClass` thing |
2023-03-29 15:33:36 +0200 | <Ou42> | I think I follow. |
2023-03-29 15:33:43 +0200 | <geekosaur> | I'm tempted to say this is because things are overparameterized |
2023-03-29 15:33:44 +0200 | <Ou42> | OK, *now* I'm gonna call it a night |
2023-03-29 15:34:21 +0200 | <Ou42> | geekosaur: tyvm |
2023-03-29 15:34:22 +0200 | <geekosaur> | we use type variables where we don't strictly need to, because that way we can provide alternative types to feed it through a proof checker that doesn't have access to X11 types |
2023-03-29 15:34:24 +0200 | <Ou42> | Solid: ty too |
2023-03-29 15:34:54 +0200 | <geekosaur> | but that means it breaks very badly when nothing provides those types to it |
2023-03-29 15:36:07 +0200 | <Ou42> | makes sense. |
2023-03-29 15:36:35 +0200 | <Ou42> | seriously appreciate this. |
2023-03-29 15:36:55 +0200 | <Ou42> | g'nite #xmonad! May we cross paths after a short nap |
2023-03-29 15:37:04 +0200 | <Ou42> | peace & 42 |
2023-03-29 15:37:18 +0200 | Ou42 | (~Ou4242a@2600:1700:e930:41b0:65bd:94a:d3f4:d966) (Quit: Leaving) |
2023-03-29 16:02:50 +0200 | L29Ah | (~L29Ah@wikipedia/L29Ah) |
2023-03-29 16:26:18 +0200 | redgloboli_ | (~redglobol@user/redgloboli) (Quit: ...enter the matrix...) |
2023-03-29 16:27:28 +0200 | redgloboli | (~redglobol@user/redgloboli) |
2023-03-29 16:28:47 +0200 | L29Ah | (~L29Ah@wikipedia/L29Ah) () |
2023-03-29 18:00:15 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
2023-03-29 18:28:44 +0200 | L29Ah | (~L29Ah@wikipedia/L29Ah) |
2023-03-29 18:50:05 +0200 | catman | (~catman@user/catman) |
2023-03-29 19:09:48 +0200 | catman | (~catman@user/catman) (Ping timeout: 264 seconds) |
2023-03-29 19:31:30 +0200 | ft | (~ft@p4fc2a88b.dip0.t-ipconnect.de) |
2023-03-29 21:29:37 +0200 | malook | (~Thunderbi@2a02:9b0:4029:41a8:3d46:a94b:9330:d637) |
2023-03-29 22:03:06 +0200 | malook | (~Thunderbi@2a02:9b0:4029:41a8:3d46:a94b:9330:d637) (Ping timeout: 252 seconds) |
2023-03-29 22:08:51 +0200 | malook | (~Thunderbi@46.52.72.170) |
2023-03-29 22:12:24 +0200 | malook | (~Thunderbi@46.52.72.170) (Remote host closed the connection) |
2023-03-29 22:12:52 +0200 | malook | (~Thunderbi@2a02:9b0:4029:41a8:e76d:c79c:d48f:d8b1) |
2023-03-29 22:26:45 +0200 | malook | (~Thunderbi@2a02:9b0:4029:41a8:e76d:c79c:d48f:d8b1) (Quit: malook) |
2023-03-29 22:40:15 +0200 | haskl | (~haskl@user/haskl) (Ping timeout: 255 seconds) |
2023-03-29 22:52:48 +0200 | haskl | (~haskl@user/haskl) |