IRCBrowse

2021/10/22

2021-10-22 00:08:27 +0200eqw_(~eqw@31.134.178.99) (Remote host closed the connection)
2021-10-22 00:16:21 +0200eqw(~eqw@31.134.178.99)
2021-10-22 00:17:27 +0200seschwar(~seschwar@user/seschwar) (Quit: :wq)
2021-10-22 00:20:04 +0200 <eqw> Hello. My xmobar is now behind any windows and thus invisible and almost useless. This problem didn't exist until today. Restart of X doesn't help. What else can I do?
2021-10-22 00:20:45 +0200 <geekosaur> sounds like you lost avoidStruts somewhere in your layoutHook
2021-10-22 00:21:23 +0200mestre(~mestre@191.177.175.57)
2021-10-22 00:22:08 +0200 <geekosaur> since that's what forces windows to resize around the status bar
2021-10-22 00:22:23 +0200 <eqw> but I didn't touch my ~/.xmonad/xmobar.hs since 2017
2021-10-22 00:23:28 +0200 <eqw> and neither I touched ~/.xmonad/xmonad.hs since 2020
2021-10-22 00:24:02 +0200 <geekosaur> conceivably you took an update that changed things, although it'd have had to be really delayed for it to be one of the xmonad changes that affected this
2021-10-22 00:24:46 +0200 <geekosaur> might have been an xmobar update, I think they changed the interaction between override_redirect and lowerOnStart?
2021-10-22 00:25:10 +0200 <geekosaur> sadly liskin's the one who knows xmobar but I think he gave up and went to bed
2021-10-22 00:30:14 +0200 <liskin> I wanted to, but haven't managed to go yet :-)
2021-10-22 00:30:33 +0200 <eqw> so neither xmonad nor xmobar store on disk any info between runs?
2021-10-22 00:30:55 +0200 <liskin> eqw: if you haven't changed config, what did you change? did you upgrade anything?
2021-10-22 00:31:01 +0200 <liskin> or perhaps downgrade? :-)
2021-10-22 00:31:30 +0200 <eqw> liskin: nothing, i believe
2021-10-22 00:32:04 +0200 <liskin> xmonad stores state, but restarting X clears that, so it's as if it didn't
2021-10-22 00:32:42 +0200 <geekosaur> xmonad and xmobar only store their configs. there's some information xmonad passes between running instances during mod-q but if that's sticking around it's a bug
2021-10-22 00:32:54 +0200 <geekosaur> that said you might see if mod-shift-space changes anything
2021-10-22 00:33:05 +0200 <geekosaur> (this will reset layouts)
2021-10-22 00:34:15 +0200 <liskin> I don't think there were changes in xmobar around override_redirect/lowerOnStart lately, it's been that way for ages
2021-10-22 00:34:24 +0200 <eqw> the screen is blinking when i press mod-shift-space. I mean, I see xmobar for a part of second.
2021-10-22 00:34:56 +0200 <geekosaur> yes, it forces a refresh. but this sounds like the layout is broken, then
2021-10-22 00:35:30 +0200 <liskin> and xmonad's handling of this was touched lately, but not in a way that would need config changes, or break it; more the other way around, we made it more tolerant of misconfigurations and fixed bugs
2021-10-22 00:36:01 +0200 <liskin> so the only scenario I can think of that would explain this is eqm upgrading from xmonad 0.11 to xmonad 0.13/0.15 or something :-)
2021-10-22 00:36:21 +0200 <liskin> *eqw I mean
2021-10-22 00:38:04 +0200 <liskin> (and if that's what happened, the solution is to either use "docks" instead of "docksEventHook", or to upgrade to the current git master, which makes "docksEventHook" alone work again)
2021-10-22 00:38:25 +0200 <geekosaur> might be worth seeing your config to see if there are bugs in it (or bugs in xmonad that it uncovers)
2021-10-22 00:38:27 +0200 <eqw> I upgraded my ubuntu from 16.04 to 20.04, but it took place about year ago
2021-10-22 00:38:32 +0200 <geekosaur> @where paste
2021-10-22 00:39:01 +0200 <liskin> eqw: an update of ubuntu doesn't force xmonad to recompile, though
2021-10-22 00:39:12 +0200 <liskin> so it's possible you were running an old binary
2021-10-22 00:39:20 +0200 <liskin> and then something forced it to rebuild today
2021-10-22 00:40:11 +0200dschrempf(~dominik@070-207.dynamic.dsl.fonira.net)
2021-10-22 00:40:39 +0200ArgoLargo[m](~argolargo@2001:470:69fc:105::1:16b1)
2021-10-22 00:40:58 +0200 <eqw> when the problem appeared I removed the binaries in ~/.xmonad as the had mtime 2021-10-21
2021-10-22 00:41:18 +0200 <eqw> https://termbin.com/0ust is my xmonad.hs
2021-10-22 00:41:22 +0200 <liskin> and ubuntu 16.04 was released before xmonad 0.13, so this seems close to the explanation I had in mind
2021-10-22 00:41:27 +0200dschrempf(~dominik@070-207.dynamic.dsl.fonira.net) (Client Quit)
2021-10-22 00:41:35 +0200 <liskin> 2021-10-21 is today, so that indeed suggests it recompiled today for some reason
2021-10-22 00:42:18 +0200 <liskin> oh, right, you have neither docksEventHook nor docksStartupHook there
2021-10-22 00:42:43 +0200 <liskin> that's indeed a config that should be broken since 0.12-ish
2021-10-22 00:43:08 +0200 <liskin> https://xmonad.github.io/xmonad-docs/xmonad-contrib-0.16.999/XMonad-Hooks-ManageDocks.html
2021-10-22 00:43:15 +0200 <liskin> main = xmonad $ … . docks . … $ def{…}
2021-10-22 00:43:37 +0200 <liskin> in your case just main = xmonad $ docks $ def
2021-10-22 00:45:21 +0200 <eqw> that helped, thank you!
2021-10-22 00:45:28 +0200 <liskin> good
2021-10-22 00:45:35 +0200 <liskin> and good night, this time for real :-)
2021-10-22 00:49:38 +0200mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2021-10-22 00:50:30 +0200 <Arcanus[m]> <liskin> "and then something forced it..." <- I just had a major update for xmonad today, it also looks like my config may be broken, still waiting on updates to finish, but I expect to not have a working machine here soon
2021-10-22 00:56:34 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2021-10-22 00:58:21 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2021-10-22 01:05:58 +0200alternateved(~user@staticline-31-183-146-132.toya.net.pl) (Ping timeout: 260 seconds)
2021-10-22 01:10:09 +0200eqw(~eqw@31.134.178.99) (Remote host closed the connection)
2021-10-22 02:31:11 +0200mestre(~mestre@191.177.175.57) (Quit: Lost terminal)
2021-10-22 03:40:57 +0200mvk(~mvk@2607:fea8:5cc1:300::4b63)
2021-10-22 03:59:54 +0200guydb89(~guy@98.40.140.117)
2021-10-22 04:04:40 +0200banc(banc@gateway/vpn/airvpn/banc) (Ping timeout: 260 seconds)
2021-10-22 04:24:19 +0200banc(banc@gateway/vpn/airvpn/banc)
2021-10-22 04:26:50 +0200td_(~td@94.134.91.188) (Ping timeout: 260 seconds)
2021-10-22 04:27:03 +0200td_(~td@94.134.91.188)
2021-10-22 04:40:38 +0200td_(~td@94.134.91.188) (Ping timeout: 260 seconds)
2021-10-22 04:42:24 +0200td_(~td@94.134.91.189)
2021-10-22 05:18:54 +0200guydb89(~guy@98.40.140.117) (Ping timeout: 260 seconds)
2021-10-22 05:33:41 +0200L29Ah(~L29Ah@wikipedia/L29Ah)
2021-10-22 05:33:54 +0200 <L29Ah> i see there's https://hackage.haskell.org/package/xmonad-0.15/docs/XMonad-ManageHook.html#v:-61--63- for exact matching of window properties
2021-10-22 05:34:30 +0200 <L29Ah> how should i match a prefix of a window property?
2021-10-22 05:52:24 +0200 <fizzie> You can look at the definition of =?, namely: q =? x = fmap (== x) q
2021-10-22 05:52:26 +0200 <fizzie> And then do the same thing except with isPrefixOf.
2021-10-22 05:54:42 +0200 <fizzie> IOW, fmap ("foo" `isPrefixOf`) should work for converting a Query String to a Query Bool.
2021-10-22 05:55:19 +0200 <L29Ah> thanks
2021-10-22 06:00:22 +0200 <fizzie> There's also https://hackage.haskell.org/package/xmonad-contrib-0.16/docs/XMonad-Hooks-ManageHelpers.html#v:isI… which isn't exactly "prefix" but "contains" instead.
2021-10-22 07:00:59 +0200mvk(~mvk@2607:fea8:5cc1:300::4b63) (Ping timeout: 264 seconds)
2021-10-22 07:20:00 +0200 <Solid> people have asked for a prefix thing quite often lately
2021-10-22 07:20:09 +0200 <Solid> I guess we should provide that
2021-10-22 07:21:02 +0200 <Solid> it would even fit nicely into the language is we called it `(^?)` or something (which would also give us `(~?)` for and `isInfixOf` variant
2021-10-22 07:31:01 +0200qbt(~qbt@user/edun)
2021-10-22 08:02:11 +0200catman(~catman@user/catman) (Ping timeout: 264 seconds)
2021-10-22 08:14:05 +0200benin(~benin@183.82.207.116)
2021-10-22 08:33:12 +0200dschrempf(~dominik@070-207.dynamic.dsl.fonira.net)
2021-10-22 08:44:47 +0200dschrempf(~dominik@070-207.dynamic.dsl.fonira.net) (Ping timeout: 264 seconds)
2021-10-22 09:04:58 +0200 <mc47[m]> Solid I just needed that lately too
2021-10-22 09:05:31 +0200 <mc47[m]> Might be worth it to explain how to create custom predicates (e.g. tell them about fmap)
2021-10-22 09:27:28 +0200mc47(~mc47@xmonad/TheMC47)
2021-10-22 09:28:14 +0200 <mc47> geekosaur: my medium concern is about changing WSPP from WSPP' (WorkspaceId -> String) to WSPP' (PP -> WorkspaceId -> String) so fallbackPrinters can be useful
2021-10-22 09:28:40 +0200 <mc47> the small concern is about exposing -?>
2021-10-22 09:37:58 +0200JasonFischmann[m(~sogensmat@2001:470:69fc:105::1:20a1)
2021-10-22 09:39:07 +0200 <JasonFischmann[m> is there any way of getting xmonad working with gnome 40 like dwm-gnome and awesome-gnome on the arch user repository ?
2021-10-22 09:39:24 +0200 <JasonFischmann[m> theres a way to do it with gnome 3 but it no longer works
2021-10-22 09:43:22 +0200cfricke(~cfricke@user/cfricke)
2021-10-22 09:49:47 +0200qbt(~qbt@user/edun) (Quit: Leaving.)
2021-10-22 09:53:24 +0200qbt(~qbt@user/edun)
2021-10-22 10:05:29 +0200qbt(~qbt@user/edun) (Quit: Leaving.)
2021-10-22 10:08:34 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2021-10-22 10:14:04 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2021-10-22 10:16:29 +0200dschrempf(~dominik@070-207.dynamic.dsl.fonira.net)
2021-10-22 10:16:55 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Read error: Connection reset by peer)
2021-10-22 10:17:54 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2021-10-22 10:22:28 +0200qbt(~qbt@user/edun)
2021-10-22 10:23:32 +0200 <FOSSHuman[m]> <Arcanus[m]> "I just had a major update for..." <- This will help you update your config: https://github.com/xmonad/xmonad-contrib/blob/master/CHANGES.md
2021-10-22 10:34:37 +0200alternateved(~user@staticline-31-183-146-132.toya.net.pl)
2021-10-22 10:47:10 +0200dschrempf(~dominik@070-207.dynamic.dsl.fonira.net) (Ping timeout: 260 seconds)
2021-10-22 11:10:33 +0200 <liskin> JasonFischmann[m: no idea but I'd think that if it worked with gnome 38 it should work with 40 and if it doesn't it's a bug in either gnome or xmonad or the glue between them
2021-10-22 11:10:55 +0200 <liskin> so the best course of action is to try to diagnose what's wrong with the thing that worked before
2021-10-22 11:11:32 +0200 <liskin> Arcanus[m]: what major update, what broke in your config?
2021-10-22 11:12:54 +0200 <liskin> mc47: hm, this PP -> thing is worring me. it's like having two nested readers :-/
2021-10-22 11:13:08 +0200 <liskin> mc47: but it may be good in practice, it just feels wrong :-)
2021-10-22 11:13:15 +0200 <mc47> It does feel wrong
2021-10-22 11:14:17 +0200 <mc47> We could just leave it as is and change post-release if we see fit
2021-10-22 11:14:33 +0200 <mc47> it would be a breaking change though
2021-10-22 11:19:57 +0200 <liskin> I guess I'll need to checkout the code again and play with it
2021-10-22 11:20:11 +0200 <liskin> (which means, not now, hopefully today)
2021-10-22 11:22:20 +0200 <liskin> or if you have time to play with it now, what would it look like if PP was added to WS?
2021-10-22 11:22:47 +0200 <liskin> (I say 9f6f7b183ad47f931344 just now, it looks okay actually, just still feels wrong)
2021-10-22 11:22:51 +0200 <liskin> *saw
2021-10-22 11:29:16 +0200 <mc47> The important thing is not to delay the release because of this ;) I doubt that many people would actually use it, so it would be okay to break later
2021-10-22 13:07:57 +0200 <Arcanus[m]> <liskin> "Arcanus: what major update, what..." <- ``` (6/8) Recompiling Xmonad now because of Haskell updates ...... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/3ec43c528720cd108cacc63581b1e8c96ffd…)
2021-10-22 13:09:25 +0200 <Arcanus[m]> this is what happened when I tried to start xmonad after the update. xmonad still runs, and the changes don't seem to actually affect anything major in my actual config, but this happens every time I try to recompile so I guess I have some cleaning up to do
2021-10-22 13:13:40 +0200 <Solid> Arcanus[m]: they don't seem to affect anything because xmonad simply uses the old binary of the compilation fails
2021-10-22 13:14:44 +0200 <Solid> something tells me that you're using Arch, perhaps try running `sudo ghc-pkg recache` to sync ghc's cache
2021-10-22 13:17:47 +0200 <Arcanus[m]> Solid: hahaha, I forgot to mention, I run arch btw
2021-10-22 13:21:44 +0200 <Solid> dynamically linking Haskell is the worst thing any distro has ever done
2021-10-22 13:21:59 +0200 <Solid> and then it happens to the distro whose users seems to have a larger overlap with xmonad users than normal
2021-10-22 13:22:02 +0200 <Solid> sigh
2021-10-22 13:22:51 +0200 <evilop> can look at it the other way too, not having sane dynamic linking support is the worst thing ghc have done :p
2021-10-22 13:22:59 +0200 <Arcanus[m]> <Solid> "something tells me that you're..." <- ran the command, then recompiled this is the error I'm getting now:
2021-10-22 13:22:59 +0200 <Arcanus[m]> ```error detected while loading xmonad configuration file /home/user/.xmonad/xmonad.hs
2021-10-22 13:22:59 +0200 <Arcanus[m]> collect2: fatal error: Id terminated with signal 7 [Bus error], core dumped compilation terminated. 'cc' failed in phase 'Linker'. Exit code: 1)
2021-10-22 13:22:59 +0200 <Arcanus[m]> Please check the file for errors.```
2021-10-22 13:23:51 +0200 <Solid> evilop: dynamic linking is the devil, so agree to disagree there :>
2021-10-22 13:24:35 +0200 <Solid> (but that desire should not be an excuse for Arch to flip the middle finger to all Haskell users...)
2021-10-22 13:24:41 +0200 <Arcanus[m]> and....now I can't close any windows...I will have to log out
2021-10-22 13:25:22 +0200 <Arcanus[m]> Solid: which distro works best with xmonad?
2021-10-22 13:26:28 +0200 <Solid> by default; any distro but Arch (and possibly its derivatives :)) But even on Arch you can install stack-static (I think it's called that) and install xmonad via stack
2021-10-22 13:26:53 +0200 <Solid> which is imo the easiest "reliable" setup one can have
2021-10-22 13:27:26 +0200 <Solid> (see https://github.com/xmonad/xmonad/blob/master/INSTALL.md#build-xmonad )
2021-10-22 13:27:32 +0200 <alternateved> So stack-static would be better option than installing stack with the sh script from stack page?
2021-10-22 13:27:50 +0200 <evilop> sidenote, I've have had more issues with xmonad on ubuntu than on arch
2021-10-22 13:27:50 +0200 <alternateved> Better for Arch-based distributions, I mean.
2021-10-22 13:28:18 +0200 <evilop> when not wanting to use the ancient version packaged for it
2021-10-22 13:28:46 +0200 <Solid> alternateved: I haven't used Arch in some time, so I can't say for sure
2021-10-22 13:28:58 +0200 <Solid> (and no idea what that script does)
2021-10-22 13:29:25 +0200 <evilop> (also ubuntu shipping ghc7 named as ghc6 was just hillarious)
2021-10-22 13:29:59 +0200 <Solid> lol
2021-10-22 13:30:03 +0200 <alternateved> Yeah, me neither. But I advised someone lately to use stack to manage xmonad and it seems that after a while stack disappeared from PATH
2021-10-22 13:30:15 +0200 <alternateved> At least that is how I understand that guy's issue.
2021-10-22 13:30:58 +0200 <evilop> that sounds like the user changing some user config regarding his shell
2021-10-22 13:31:46 +0200 <alternateved> Maybe, I cannot be sure what that user was doing on his computer.
2021-10-22 13:32:20 +0200 <alternateved> I only know that he had poor experience with Arch xmonad-git package and then he had poor experience with the stack
2021-10-22 13:32:33 +0200 <alternateved> This is the script if anyone is curious https://get.haskellstack.org/
2021-10-22 13:33:56 +0200 <Arcanus[m]> alternateved: I shall check it out post haste
2021-10-22 13:33:56 +0200 <Arcanus[m]> does this mean I need to re isntall and re-write my xmonad config?
2021-10-22 13:35:10 +0200 <alternateved> I'll leave that answer to someone more competent.
2021-10-22 13:35:39 +0200 <alternateved> But I have to say, when I was using Arch, stack was the only viable option for me.
2021-10-22 13:36:27 +0200 <alternateved> Using anything from Arch or Arch User Repositories quickly led to some breakage
2021-10-22 13:37:33 +0200 <alternateved> But I also wanted to use xmonad compiled from source (since I saw the TUTORIAL.md page), which does some things better
2021-10-22 13:37:58 +0200 <Arcanus[m]> that's so weird, I've been using it for a while, well, since I switched to arch and haven't had any problems with it until now
2021-10-22 13:37:58 +0200 <Arcanus[m]> besides being unable to figure out how to properly configure my xmobar
2021-10-22 14:03:11 +0200 <Solid> Arcanus[m]: you don't have to write your config, no
2021-10-22 14:03:20 +0200 <Solid> s/write/rewrite/
2021-10-22 15:28:35 +0200cfricke(~cfricke@user/cfricke) (Ping timeout: 264 seconds)
2021-10-22 16:30:10 +0200qbt(~qbt@user/edun) (Ping timeout: 260 seconds)
2021-10-22 16:37:50 +0200 <Solid> liskin: ewmhFullscreen does not work without ewmh, right?
2021-10-22 16:40:38 +0200 <alternateved> It seems it does work.
2021-10-22 16:40:46 +0200qbt(~qbt@user/edun)
2021-10-22 16:41:31 +0200 <liskin> Solid: it might, but it's not guaranteed; contents of the _NET_SUPPORTED property is undefined without ewmh, and ewmhFullscreen just adds to it
2021-10-22 16:42:09 +0200 <liskin> if someone replaces a fully EWMH-compliant WM with xmonad with ewmhFullscreen without ewmh, hillarity will ensue
2021-10-22 16:42:38 +0200 <liskin> (quite possibly a difficult to detect hillarity)
2021-10-22 16:43:57 +0200 <liskin> after #625, however, using just ewmhFullscreen will be valid (not that I'm going to test that usecase, but I will consider bug reports about it serious)
2021-10-22 16:51:04 +0200 <Solid> liskin: I was mainly thinking about the fact that we know get a deprecation warning in X.L.Fullscreen (and since we show deprecation warnings to users during recompilation this may be undesirable for people who compile contrib alongside their config file)
2021-10-22 16:51:23 +0200^[(~user@user//x-8473491) (Ping timeout: 264 seconds)
2021-10-22 16:52:43 +0200 <liskin> Solid: I see
2021-10-22 16:53:01 +0200 <liskin> I did spend considerable time thinking and writing code to get rid of that particular warning
2021-10-22 16:53:14 +0200 <liskin> and then I threw it all away and decided it's not worth it
2021-10-22 16:54:14 +0200 <liskin> but you do have a good point that people using the StackGhc recompile method will get warned about this, I did not consider that
2021-10-22 16:54:46 +0200 <liskin> so I suggest that we silence deprecations in X.L.Fullscreen until #625 is done
2021-10-22 17:03:05 +0200^[(~user@user//x-8473491)
2021-10-22 17:04:44 +0200 <liskin> actually not, xmonad --recompile invokes stack build --silent
2021-10-22 17:05:24 +0200 <liskin> so this only affects people with custom build scripts, hm
2021-10-22 17:39:25 +0200^[(~user@user//x-8473491) (Ping timeout: 252 seconds)
2021-10-22 18:11:58 +0200^[(~user@user//x-8473491)
2021-10-22 18:17:53 +0200CosmosAtlas(~CosmosAtl@bras-base-ktnron060cw-grc-02-76-69-147-188.dsl.bell.ca) (Quit: WeeChat 3.3)
2021-10-22 18:19:21 +0200wonko(~wjc@62.115.229.50)
2021-10-22 18:20:11 +0200^[(~user@user//x-8473491) (Ping timeout: 264 seconds)
2021-10-22 18:25:04 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2021-10-22 18:26:44 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2021-10-22 18:28:50 +0200^[(~user@user//x-8473491)
2021-10-22 18:34:18 +0200^[(~user@user//x-8473491) (Ping timeout: 258 seconds)
2021-10-22 18:47:04 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2021-10-22 18:48:49 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2021-10-22 19:36:05 +0200piele_piele
2021-10-22 19:46:53 +0200qbt(~qbt@user/edun) (Quit: Leaving.)
2021-10-22 19:57:16 +0200catman(~catman@user/catman)
2021-10-22 20:15:43 +0200Solidfeels like we need to standardise how we write xmonad
2021-10-22 20:15:51 +0200 <Solid> as in, the actual name of the thing
2021-10-22 20:16:02 +0200 <Solid> is it "xmonad" or "XMonad"? :)
2021-10-22 20:17:10 +0200 <liskin> oh, right, it's inconsistent right on the xmonad homepage :-)
2021-10-22 20:17:59 +0200 <liskin> we could interpret "xmonad" as the core repo/package and "XMonad" as the whole
2021-10-22 20:20:37 +0200 <Solid> Yeah it's all over the place everywhere
2021-10-22 20:20:52 +0200 <Solid> I have a feeling it's because Xmonad (say, when the name is at the start of a sentence) looks so bad
2021-10-22 20:21:08 +0200 <Solid> (also the namespace, of course)
2021-10-22 20:21:37 +0200 <geekosaur> there's alkso xmoinad the executable vs. the package or the whole
2021-10-22 20:21:50 +0200 <geekosaur> *also xmonad
2021-10-22 20:21:56 +0200 <geekosaur> I kan tipe gud
2021-10-22 20:22:05 +0200 <Solid> :D
2021-10-22 20:22:45 +0200 <Solid> using xmonad only for the core repo/package/executable sounds like a good idea, but also like a nightmare to enforce
2021-10-22 20:30:08 +0200humky(~humky@user/humky)
2021-10-22 20:38:47 +0200 <liskin> well what's the worst that could happen
2021-10-22 20:39:08 +0200 <liskin> someone will need to clean it up again in 5 years time :-)
2021-10-22 20:40:04 +0200 <geekosaur> I have to imagineother projects have this problem
2021-10-22 20:40:24 +0200 <geekosaur> it sometimes helps to have a conventions document, but then you have to hope people read it
2021-10-22 20:45:36 +0200mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2021-10-22 20:49:41 +0200 <alternateved> I am not sure if you would achieve anything with that matter. Check how it works with other window managers.
2021-10-22 20:50:27 +0200 <alternateved> Ways how people are naming them are also all over the place
2021-10-22 20:56:31 +0200^[(~user@user//x-8473491)
2021-10-22 20:59:21 +0200electr0n(~electr0n@about/security/founder/electr0n)
2021-10-22 21:04:20 +0200^[(~user@user//x-8473491) (Ping timeout: 260 seconds)
2021-10-22 21:14:43 +0200benin3(~benin@183.82.207.116)
2021-10-22 21:17:10 +0200benin(~benin@183.82.207.116) (Ping timeout: 260 seconds)
2021-10-22 21:17:10 +0200benin3benin
2021-10-22 21:43:59 +0200seschwar(~seschwar@user/seschwar)
2021-10-22 22:05:50 +0200^[(~user@user//x-8473491)
2021-10-22 22:14:36 +0200^[(~user@user//x-8473491) (Quit: ^[)
2021-10-22 22:39:38 +0200mestre(~mestre@191.177.175.57)
2021-10-22 23:13:34 +0200benin(~benin@183.82.207.116) (Quit: The Lounge - https://thelounge.chat)
2021-10-22 23:31:26 +0200ectospasm(~ectospasm@user/ectospasm) (*.net *.split)
2021-10-22 23:31:26 +0200srk(~sorki@user/srk) (*.net *.split)
2021-10-22 23:31:26 +0200steve__(~steve@ool-182c2aa4.dyn.optonline.net) (*.net *.split)
2021-10-22 23:31:26 +0200Forkk(~forkk@li926-228.members.linode.com) (*.net *.split)
2021-10-22 23:31:26 +0200jsoo(~znc@irc.refl.club) (*.net *.split)
2021-10-22 23:31:26 +0200tv(~tv@user/tv) (*.net *.split)
2021-10-22 23:31:26 +0200lambdabot(~lambdabot@haskell/bot/lambdabot) (*.net *.split)
2021-10-22 23:31:26 +0200slep(~slep@cpc150002-brnt4-2-0-cust437.4-2.cable.virginm.net) (*.net *.split)
2021-10-22 23:31:26 +0200rieper(~riepernet@sxbeta1.geo.uni-leipzig.de) (*.net *.split)
2021-10-22 23:31:27 +0200deebo(~globe@stonebay32.com) (*.net *.split)
2021-10-22 23:31:27 +0200zawaken(~zawaken@user/zawaken) (*.net *.split)
2021-10-22 23:31:33 +0200slep(~slep@cpc150002-brnt4-2-0-cust437.4-2.cable.virginm.net)
2021-10-22 23:31:38 +0200deebo(~globe@stonebay32.com)
2021-10-22 23:31:47 +0200steve__(~steve@ool-182c2aa4.dyn.optonline.net)
2021-10-22 23:32:16 +0200ectospasm(~ectospasm@23-227-173-50.static.hvvc.us)
2021-10-22 23:32:16 +0200rieper(~riepernet@sxbeta1.geo.uni-leipzig.de)
2021-10-22 23:32:16 +0200lambdabot(~lambdabot@haskell/bot/lambdabot)
2021-10-22 23:33:10 +0200ectospasmGuest2999
2021-10-22 23:33:11 +0200srk(~sorki@user/srk)
2021-10-22 23:33:15 +0200zawaken(~zawaken@user/zawaken)
2021-10-22 23:33:36 +0200Forkk(~forkk@li926-228.members.linode.com)
2021-10-22 23:33:37 +0200tv(~tv@user/tv)
2021-10-22 23:34:29 +0200 <mestre> e ai
2021-10-22 23:34:36 +0200 <mestre> ops, wrong chan.
2021-10-22 23:34:38 +0200jsoo(~znc@irc.refl.club)