Logs: liberachat/#xmonad
| 2022-04-19 12:59:02 | <Ether[m]> | Isee |
| 2022-04-19 12:59:08 | <Ether[m]> | I see* |
| 2022-04-19 12:59:27 | <abastro[m]> | geekosaur: Thanks! Hmm, this is quite hard to debug. |
| 2022-04-19 12:59:32 | <geekosaur> | dunst has to do it itself, and has support to do so (I was actually trying to dig that out from the dunst website but liskin beat me to it) |
| 2022-04-19 12:59:45 | <abastro[m]> | Maybe at this point I'd try gdb and wish luck? |
| 2022-04-19 13:00:17 | <geekosaur> | gdb will probably notbe too much help, as the necessary information has been lost by that point |
| 2022-04-19 13:00:57 | <geekosaur> | you probably want to ask the folks in #ghc for help, in particular there are some gdb scripts that come with the ghc source code that can be useful for examining heap structures |
| 2022-04-19 13:01:53 | <Ether[m]> | Dunst claims otherwise; |
| 2022-04-19 13:01:53 | <Ether[m]> | https://github.com/dunst-project/dunst/issues/678 |
| 2022-04-19 13:04:36 | <abastro> | Oh, I see thank you! geekosaur |
| 2022-04-19 13:04:47 | <abastro> | #ghc on libera, right? |
| 2022-04-19 13:13:37 | <geekosaur> | yes |
| 2022-04-19 13:14:30 | <geekosaur> | Ether[m], that bug confirms that dunst is raising itself. xmonad will not like that *if* it is managing the window; you have to `doIgnore` it for that to work |
| 2022-04-19 13:21:09 | <liskin> | it's quite likely an overrideredirect window, so it should work out of the box |
| 2022-04-19 13:22:05 | <liskin> | Ether[m]: do you have https://github.com/xmonad/xmonad/pull/275 or are you running an older version of xmonad? |
| 2022-04-19 13:22:31 | <liskin> | still wouldn't explain the "Dunst hides when i spawn" bit but the "resize or move windows.." part is fixed by #275 |
| 2022-04-19 13:47:49 | × | abastro quits (~abab9579@220.75.216.63) (Remote host closed the connection) |
| 2022-04-19 13:57:14 | <Ether[m]> | <liskin> "Ether: do you have https://..." <- Unfortunately, i am 01.5 |
| 2022-04-19 13:57:27 | <Ether[m]> | 0.15* |
| 2022-04-19 13:58:42 | <geekosaur> | I think at some point you'll have to upgrade |
| 2022-04-19 13:58:42 | <Ether[m]> | <geekosaur> "Ether, that bug confirms that..." <- Yes |
| 2022-04-19 13:58:51 | <Ether[m]> | Yes |
| 2022-04-19 13:59:15 | <Ether[m]> | But the binary is still not in the repos |
| 2022-04-19 13:59:17 | <Ether[m]> | Is 0.17 stable? |
| 2022-04-19 13:59:33 | <Ether[m]> | Why is there no binary package? |
| 2022-04-19 13:59:50 | <geekosaur> | we don't ship binary packages, that's up to your distribution |
| 2022-04-19 14:00:34 | <Ether[m]> | geekosaur: The thing is, even something bleeding edge like arch doesn't have it. So i am scared its unstable |
| 2022-04-19 14:01:28 | <geekosaur> | arch is just not upgrading its haskell packages, because even arch users are telling other arch users to use ghcup and stack instead of the packaged versions |
| 2022-04-19 14:01:35 | <geekosaur> | becuase arch mis-packages haskell stuff |
| 2022-04-19 14:02:14 | <Ether[m]> | I see, but is 0.17 considered stable? |
| 2022-04-19 14:02:46 | <lyiriyah[m]> | Ether[m]: Arch's Haskell packages are broken. I use Stack instead. |
| 2022-04-19 14:04:57 | <Ether[m]> | There is a lack of documentation for installing xmonad 0.17 |
| 2022-04-19 14:06:08 | <Ether[m]> | https://xmonad.org/INSTALL.html |
| 2022-04-19 14:06:57 | <Ether[m]> | It doesn't go through how the process could be made minimal. |
| 2022-04-19 14:07:14 | <lyiriyah[m]> | ? |
| 2022-04-19 14:07:16 | <Ether[m]> | Its basically cloning the repo and installing it |
| 2022-04-19 14:07:35 | <lyiriyah[m]> | Yes |
| 2022-04-19 14:07:47 | <lyiriyah[m]> | With Stack you are building from source |
| 2022-04-19 14:08:20 | <lyiriyah[m]> | Make sure to install using ghcup and not pacman |
| 2022-04-19 14:11:59 | <geekosaur> | it would be nice if arch at least provided static library packages for what they do package, but they only do that for ghc-bundled libraries |
| 2022-04-19 14:12:24 | <geekosaur> | which means youget weird errors when trying to use the packaged libraries unless you know to patch everything to use -dynamic |
| 2022-04-19 14:16:16 | <geekosaur> | yeh, even the arch wiki page for xmonad warns about the things that go wrong because of only shipping shared libraries |
| 2022-04-19 14:16:35 | <geekosaur> | which means what arch packages *is* unstable |
| 2022-04-19 14:16:59 | <geekosaur> | but it's all their fault; if they did things the way they're intended to be done, there would be no problem |
| 2022-04-19 14:18:50 | <geekosaur> | we've also had problems with the AUR packaging of xmonad-git in the past, because they sometimes ignore the version bounds we put on things and then they get weird bugs |
| 2022-04-19 14:25:38 | <abastro[m]> | Ignoring version bounds???? |
| 2022-04-19 14:27:21 | <geekosaur> | yeh. we released a new X11 binding with a version outside the bounds for xmonad and xmonad-contrib because one binding was able to throw an exsception that code had to be ready to catch |
| 2022-04-19 14:27:51 | <geekosaur> | they patched the version bounds of xmonad-git and xmonad-contrib-git to accept it anyway, and xmonad-git started throwing exceptions |
| 2022-04-19 14:28:06 | <geekosaur> | it was pretty ugly |
| 2022-04-19 14:28:37 | <geekosaur> | this was several years ago. we try to force type changes now so things like that can't happen any more |
| 2022-04-19 14:29:34 | <abastro[m]> | Oh noo |
| 2022-04-19 14:29:39 | <abastro[m]> | Why is arch repo managed like this |
| 2022-04-19 14:30:16 | <geekosaur> | you would have to ask them |
| 2022-04-19 14:30:33 | <abastro[m]> | :P |
| 2022-04-19 14:30:36 | <geekosaur> | at this point we just tell people touse ghcup and ignore the arch repo for anything haskell related |
| 2022-04-19 14:30:38 | <Ether[m]> | Arch used to be awesome |
| 2022-04-19 14:30:45 | <Ether[m]> | Its getting worse.. |
| 2022-04-19 14:30:48 | <geekosaur> | it'sfine for anything else |
| 2022-04-19 14:31:15 | <Ether[m]> | geekosaur: Not really, systemd and all the broken packages |
| 2022-04-19 14:31:16 | <geekosaur> | keep in mindthat rolling release is a lot of work as more and more packages interact |
| 2022-04-19 14:31:36 | <geekosaur> | there'sa reason it's an uncommon way of managing distributions |
| 2022-04-19 14:31:44 | <Ether[m]> | Some of the core packages are broken too |
| 2022-04-19 14:32:58 | <abastro[m]> | Are many package managers like this? |
| 2022-04-19 14:33:12 | <abastro[m]> | I wonder how they somehow work in a sense.. |
| 2022-04-19 14:33:58 | <geekosaur> | I've managed a distribution, sort of (when I worked for C-MU we maintained a modified red hat, later suse, customized for our environment); it's quite a lot of work even doing that, much less managing the whole distribution. rolling release means it's constant instead of just during releases |
| 2022-04-19 14:35:11 | <Ether[m]> | Wow what a pain! |
| 2022-04-19 14:35:19 | <Ether[m]> | I pitty you.. |
| 2022-04-19 14:35:52 | → | abastro joins (~abab9579@220.75.216.63) |
| 2022-04-19 14:39:44 | <abastro> | geekosaur: Was there any post on the ghc irc btw? I turned off the computer for a while and #ghc does not provide logs |
| 2022-04-19 14:40:20 | <geekosaur> | not yet |
| 2022-04-19 14:40:29 | <geekosaur> | haven't really seen anyone around #ghc |
| 2022-04-19 14:40:43 | <geekosaur> | you may want to monitor it via matrix so you get logs |
| 2022-04-19 14:40:53 | <abastro> | Thank you! Yea I joined via matrix as well |
| 2022-04-19 14:41:11 | <abastro> | So ye I can check log myself from now on |
| 2022-04-19 14:43:32 | <geekosaur> | oh goodie, reboot in my near future |
| 2022-04-19 14:49:04 | × | geekosaur quits (~geekosaur@xmonad/geekosaur) (Quit: Leaving) |
| 2022-04-19 14:56:30 | → | geekosaur joins (~geekosaur@xmonad/geekosaur) |
| 2022-04-19 15:05:25 | <liskin> | Ether[m]: even xmonad from git is considered stable in terms of bugs, it's just the configuration API that can evolve dramatically during development cycles |
| 2022-04-19 15:12:43 | <geekosaur> | we are very careful to not commit things that will break someone's running xmonad |
| 2022-04-19 15:13:01 | <geekosaur> | after all, it's how you interact with the computer |
| 2022-04-19 15:20:34 | → | Natch joins (~natch@c-9e07225c.038-60-73746f7.bbcust.telenor.se) |
| 2022-04-19 15:20:47 | <abastro> | I cannot coerce over X.. :( |
| 2022-04-19 15:21:24 | <geekosaur> | ? |
| 2022-04-19 15:30:39 | → | abiss27 joins (~abiss27@user/abiss) |
| 2022-04-19 15:33:56 | → | stackdroid18 joins (14094@user/stackdroid) |
| 2022-04-19 15:36:53 | <abastro> | I am using ExtensibleState facility. |
| 2022-04-19 15:37:15 | <abastro> | (Realized it would be useful for persistent state) |
| 2022-04-19 15:37:58 | <geekosaur> | that'll break coercion, yep |
| 2022-04-19 15:38:07 | <geekosaur> | type level shenanigans often do |
| 2022-04-19 15:38:20 | <geekosaur> | even though XS is relatively simple as such go |
| 2022-04-19 15:38:33 | <abastro> | It's simply because the constructor is not exported, I think. |
| 2022-04-19 15:38:47 | <abastro> | (Or isn't it?) |
| 2022-04-19 15:39:03 | <abastro> | That, or just `coerce` being overly fragile |
| 2022-04-19 15:47:08 | × | abastro quits (~abab9579@220.75.216.63) (Remote host closed the connection) |
| 2022-04-19 15:49:54 | × | twiclo quits (~twiclo@mail.twil.cx) (Ping timeout: 276 seconds) |
| 2022-04-19 15:51:35 | → | twiclo joins (~twiclo@vpn.utahbroadband.com) |
| 2022-04-19 15:58:00 | <Ether[m]> | geekosaurii i tested the notification issue with x.hs and to my surprise it somehow manges to keep dunst on top |
| 2022-04-19 15:58:43 | <Ether[m]> | https://github.com/Ahanaf-Ether/xmonad/blob/stable/x.hs |
| 2022-04-19 15:59:09 | → | abastro joins (~abab9579@220.75.216.63) |
| 2022-04-19 16:05:51 | <abastro> | Hmm `XMonad.Config.Prime` irks me |
All times are in UTC.