| 2022-04-19 00:44:19 +0200 | Polo | (~GiverOfDo@user/polo) (Quit: Textual IRC Client: www.textualapp.com) |
| 2022-04-19 01:19:33 +0200 | chomwitt | (~chomwitt@ppp-94-67-221-107.home.otenet.gr) (Ping timeout: 256 seconds) |
| 2022-04-19 01:34:26 +0200 | stackdroid18 | (14094@user/stackdroid) (Quit: hasta la vista... tchau!) |
| 2022-04-19 01:45:07 +0200 | twiclo | (~twiclo@204.14.20.66.static.utbb.net) (Ping timeout: 240 seconds) |
| 2022-04-19 01:47:16 +0200 | twiclo | (~twiclo@mail.twil.cx) |
| 2022-04-19 01:54:17 +0200 | mvk | (~mvk@2607:fea8:5ce3:8500::85f6) |
| 2022-04-19 01:57:36 +0200 | werneta | (~werneta@137.79.218.82) (Remote host closed the connection) |
| 2022-04-19 03:06:25 +0200 | abastro | (~abab9579@220.75.216.63) |
| 2022-04-19 03:14:15 +0200 | Sleroq | (~Sleroq@95-107-2-180.dsl.orel.ru) (Quit: Client closed) |
| 2022-04-19 03:21:42 +0200 | evanjs[m] | (~evanjsxma@2001:470:69fc:105::1:fc72) |
| 2022-04-19 03:43:02 +0200 | steve__ | (~steve@ool-182c2b80.dyn.optonline.net) |
| 2022-04-19 03:54:21 +0200 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2022-04-19 03:57:02 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2022-04-19 04:03:04 +0200 | banc | (banc@gateway/vpn/airvpn/banc) (Ping timeout: 248 seconds) |
| 2022-04-19 04:22:08 +0200 | banc | (banc@gateway/vpn/airvpn/banc) |
| 2022-04-19 04:23:40 +0200 | abastro | (~abab9579@220.75.216.63) (Remote host closed the connection) |
| 2022-04-19 04:24:14 +0200 | abastro | (~abab9579@220.75.216.63) |
| 2022-04-19 04:28:15 +0200 | abhixec | (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 256 seconds) |
| 2022-04-19 04:42:08 +0200 | mohab | (~mohab@156.223.10.66) |
| 2022-04-19 04:42:36 +0200 | mohab | (~mohab@156.223.10.66) (Client Quit) |
| 2022-04-19 04:44:12 +0200 | mohab | (~mohab@156.223.10.66) |
| 2022-04-19 04:46:32 +0200 | mohab | (~mohab@156.223.10.66) (Client Quit) |
| 2022-04-19 05:08:52 +0200 | mvk | (~mvk@2607:fea8:5ce3:8500::85f6) (Ping timeout: 250 seconds) |
| 2022-04-19 05:08:59 +0200 | abastro | (~abab9579@220.75.216.63) (Remote host closed the connection) |
| 2022-04-19 05:10:06 +0200 | abastro | (~abab9579@220.75.216.63) |
| 2022-04-19 05:10:29 +0200 | abastro | (~abab9579@220.75.216.63) (Remote host closed the connection) |
| 2022-04-19 05:12:01 +0200 | abastro | (~abab9579@220.75.216.63) |
| 2022-04-19 05:19:28 +0200 | abastro | (~abab9579@220.75.216.63) (Remote host closed the connection) |
| 2022-04-19 05:31:09 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 256 seconds) |
| 2022-04-19 05:44:29 +0200 | Polo | (~GiverOfDo@50-206-8-110-static.hfc.comcastbusiness.net) |
| 2022-04-19 05:44:33 +0200 | Polo | (~GiverOfDo@50-206-8-110-static.hfc.comcastbusiness.net) (Changing host) |
| 2022-04-19 05:44:33 +0200 | Polo | (~GiverOfDo@user/polo) |
| 2022-04-19 05:55:01 +0200 | Polo | (~GiverOfDo@user/polo) (Quit: Textual IRC Client: www.textualapp.com) |
| 2022-04-19 05:58:15 +0200 | Polo | (~GiverOfDo@50-206-8-110-static.hfc.comcastbusiness.net) |
| 2022-04-19 06:03:04 +0200 | Polo | (~GiverOfDo@50-206-8-110-static.hfc.comcastbusiness.net) (Read error: Connection reset by peer) |
| 2022-04-19 06:03:26 +0200 | Polo | (~GiverOfDo@50-206-8-110-static.hfc.comcastbusiness.net) |
| 2022-04-19 06:11:32 +0200 | benin | (~benin@183.82.204.110) |
| 2022-04-19 06:31:52 +0200 | Polo | (~GiverOfDo@50-206-8-110-static.hfc.comcastbusiness.net) (Quit: Textual IRC Client: www.textualapp.com) |
| 2022-04-19 06:46:27 +0200 | <abastro[m]> | geekosaur: Well I am seeing strange phenomenon |
| 2022-04-19 06:46:53 +0200 | <abastro[m]> | Nearly identical configuration yet one crashes, the other does not. |
| 2022-04-19 06:48:38 +0200 | <abastro[m]> | I'll try to see if it is due to the script running bunch of commands or the build file including a few more dependencies. |
| 2022-04-19 07:36:25 +0200 | abhixec | (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) |
| 2022-04-19 07:43:17 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) (Remote host closed the connection) |
| 2022-04-19 07:45:19 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) |
| 2022-04-19 08:10:35 +0200 | Polo | (~GiverOfDo@50-206-8-110-static.hfc.comcastbusiness.net) |
| 2022-04-19 08:11:56 +0200 | Polo | (~GiverOfDo@50-206-8-110-static.hfc.comcastbusiness.net) (Client Quit) |
| 2022-04-19 08:15:04 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Quit: Lost terminal) |
| 2022-04-19 08:23:34 +0200 | <Solid> | liskin: thanks for taking care of the cache stuff! |
| 2022-04-19 08:35:28 +0200 | cyr4x3 | (~cyr4x3@139.47.114.80) |
| 2022-04-19 08:37:14 +0200 | cyr4x3 | (~cyr4x3@139.47.114.80) (Client Quit) |
| 2022-04-19 09:32:18 +0200 | abastro | (~abab9579@220.75.216.63) |
| 2022-04-19 09:46:37 +0200 | chomwitt | (~chomwitt@2a02:587:dc1b:da00:1339:e02b:9822:2360) |
| 2022-04-19 10:29:56 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2022-04-19 11:00:15 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2022-04-19 11:23:12 +0200 | <Ether[m]> | Dunst hides when i spawn, resize or move windows.. |
| 2022-04-19 11:23:26 +0200 | <Ether[m]> | Is there a quick fix? |
| 2022-04-19 11:33:06 +0200 | amoe | (~amoe@visarend.solasistim.net) (Quit: leaving) |
| 2022-04-19 11:50:15 +0200 | abastro | (~abab9579@220.75.216.63) (Ping timeout: 256 seconds) |
| 2022-04-19 12:22:11 +0200 | Czernobog | (~Czernobog@user/czernobog) (Read error: Connection reset by peer) |
| 2022-04-19 12:24:08 +0200 | Czernobog | (~Czernobog@user/czernobog) |
| 2022-04-19 12:42:07 +0200 | theproffesor | (~theprofff@user/theproffesor) (Ping timeout: 246 seconds) |
| 2022-04-19 12:42:42 +0200 | theproffesor | (~theprofff@user/theproffesor) |
| 2022-04-19 13:21:03 +0200 | abastro | (~abab9579@220.75.216.63) |
| 2022-04-19 13:31:15 +0200 | Lears | (~Leary]@122-58-90-96-vdsl.sparkbb.co.nz) (Remote host closed the connection) |
| 2022-04-19 13:32:15 +0200 | [Leary] | (~Leary]@122-58-90-96-vdsl.sparkbb.co.nz) |
| 2022-04-19 13:46:54 +0200 | <geekosaur> | not familiar with dunst, sorry |
| 2022-04-19 13:47:08 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) |
| 2022-04-19 13:47:20 +0200 | <geekosaur> | we don't support stays-on-top, except in thelimited fashion that floats are generally above tiled windows |
| 2022-04-19 14:07:05 +0200 | <Ether[m]> | <geekosaur> "we don't support stays-on-top..." <- How do i float dunst? |
| 2022-04-19 14:07:15 +0200 | <Ether[m]> | Mange hook? |
| 2022-04-19 14:08:16 +0200 | <geekosaur> | manageHook, yes |
| 2022-04-19 14:08:43 +0200 | <geekosaur> | that said it's probably already being doIgnore-d so it behaves likea notification; which means nothing will keep it on top |
| 2022-04-19 14:15:06 +0200 | abastro | (~abab9579@220.75.216.63) (Quit: testing xmonad) |
| 2022-04-19 14:21:35 +0200 | benin | (~benin@183.82.204.110) (Quit: The Lounge - https://thelounge.chat) |
| 2022-04-19 14:23:46 +0200 | abastro | (~abab9579@220.75.216.63) |
| 2022-04-19 14:26:38 +0200 | <abastro> | geekosaur: Well I think I established that the crash is not related with xmonad path settings. |
| 2022-04-19 14:27:08 +0200 | <abastro> | I added containers, filepath, directory, X11, unix into the `build-depends` file |
| 2022-04-19 14:27:30 +0200 | <abastro> | Then it began crashing again when I abuse the window switching. |
| 2022-04-19 14:40:17 +0200 | <abastro> | Has any idea? Am I importing some potentially dangerous stuffs? |
| 2022-04-19 14:42:13 +0200 | <liskin> | Ether[m]: also Dunst makes some effort to raise itself when the stacking order changes, there are two closed issues in the xmonad repo about it |
| 2022-04-19 14:43:01 +0200 | <liskin> | Maybe one is still open as there still are some issues with other notification daemons but Dunst should just work :-/ |
| 2022-04-19 14:44:14 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-04-19 14:52:47 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) (Remote host closed the connection) |
| 2022-04-19 14:54:27 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) |
| 2022-04-19 14:55:03 +0200 | <geekosaur> | abastro, none of those should be dangerous and I would think someone would have heard about it by now if any of themprovoked problems with 9.2.2 as they're pretty widely used |
| 2022-04-19 14:55:30 +0200 | <abastro[m]> | Oh no :( |
| 2022-04-19 14:55:55 +0200 | <abastro[m]> | Hm, actually I guess I could have confused it for an actual problem. |
| 2022-04-19 14:56:14 +0200 | <Ether[m]> | <geekosaur> "that said it's probably already..." <- Is there like a work around? |
| 2022-04-19 14:56:23 +0200 | <abastro[m]> | By actual problem I mean, perhaps this one has different reason behind, i.e. |
| 2022-04-19 14:57:02 +0200 | <abastro[m]> | `user error (Error in function getWindowAttributes)` |
| 2022-04-19 14:57:19 +0200 | <abastro[m]> | (I only opened `gnome-terminal` btw) |
| 2022-04-19 14:57:37 +0200 | <geekosaur> | Ether[m], you might check your dunst confoiguration, as liskin said it should try to keep itself on top |
| 2022-04-19 14:58:28 +0200 | <Ether[m]> | But you said at the moment nothing does that |
| 2022-04-19 14:58:37 +0200 | <Ether[m]> | <geekosaur> "that said it's probably already..." <- . |
| 2022-04-19 14:58:40 +0200 | <geekosaur> | abastro[m], you'll usually get that when a window is closed. personally I'd like to know where we're not cleaning up properly after a DestroyWindow event (or perhaps trying to access the window inside that event), but it's harmless |
| 2022-04-19 14:58:54 +0200 | <geekosaur> | Ether[m], nothing in xmonad keeps it on top |
| 2022-04-19 14:59:02 +0200 | <Ether[m]> | Isee |
| 2022-04-19 14:59:08 +0200 | <Ether[m]> | I see* |
| 2022-04-19 14:59:27 +0200 | <abastro[m]> | geekosaur: Thanks! Hmm, this is quite hard to debug. |
| 2022-04-19 14:59:32 +0200 | <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 14:59:45 +0200 | <abastro[m]> | Maybe at this point I'd try gdb and wish luck? |
| 2022-04-19 15:00:17 +0200 | <geekosaur> | gdb will probably notbe too much help, as the necessary information has been lost by that point |
| 2022-04-19 15:00:57 +0200 | <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 15:01:53 +0200 | <Ether[m]> | Dunst claims otherwise; |
| 2022-04-19 15:01:53 +0200 | <Ether[m]> | https://github.com/dunst-project/dunst/issues/678 |
| 2022-04-19 15:04:36 +0200 | <abastro> | Oh, I see thank you! geekosaur |
| 2022-04-19 15:04:47 +0200 | <abastro> | #ghc on libera, right? |
| 2022-04-19 15:13:37 +0200 | <geekosaur> | yes |
| 2022-04-19 15:14:30 +0200 | <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 15:21:09 +0200 | <liskin> | it's quite likely an overrideredirect window, so it should work out of the box |
| 2022-04-19 15:22:05 +0200 | <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 15:22:31 +0200 | <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 15:47:49 +0200 | abastro | (~abab9579@220.75.216.63) (Remote host closed the connection) |
| 2022-04-19 15:57:14 +0200 | <Ether[m]> | <liskin> "Ether: do you have https://..." <- Unfortunately, i am 01.5 |
| 2022-04-19 15:57:27 +0200 | <Ether[m]> | 0.15* |
| 2022-04-19 15:58:42 +0200 | <geekosaur> | I think at some point you'll have to upgrade |
| 2022-04-19 15:58:42 +0200 | <Ether[m]> | <geekosaur> "Ether, that bug confirms that..." <- Yes |
| 2022-04-19 15:58:51 +0200 | <Ether[m]> | Yes |
| 2022-04-19 15:59:15 +0200 | <Ether[m]> | But the binary is still not in the repos |
| 2022-04-19 15:59:17 +0200 | <Ether[m]> | Is 0.17 stable? |
| 2022-04-19 15:59:33 +0200 | <Ether[m]> | Why is there no binary package? |
| 2022-04-19 15:59:50 +0200 | <geekosaur> | we don't ship binary packages, that's up to your distribution |
| 2022-04-19 16:00:34 +0200 | <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 16:01:28 +0200 | <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 16:01:35 +0200 | <geekosaur> | becuase arch mis-packages haskell stuff |
| 2022-04-19 16:02:14 +0200 | <Ether[m]> | I see, but is 0.17 considered stable? |
| 2022-04-19 16:02:46 +0200 | <lyiriyah[m]> | Ether[m]: Arch's Haskell packages are broken. I use Stack instead. |
| 2022-04-19 16:04:57 +0200 | <Ether[m]> | There is a lack of documentation for installing xmonad 0.17 |
| 2022-04-19 16:06:08 +0200 | <Ether[m]> | https://xmonad.org/INSTALL.html |
| 2022-04-19 16:06:57 +0200 | <Ether[m]> | It doesn't go through how the process could be made minimal. |
| 2022-04-19 16:07:14 +0200 | <lyiriyah[m]> | ? |
| 2022-04-19 16:07:16 +0200 | <Ether[m]> | Its basically cloning the repo and installing it |
| 2022-04-19 16:07:35 +0200 | <lyiriyah[m]> | Yes |
| 2022-04-19 16:07:47 +0200 | <lyiriyah[m]> | With Stack you are building from source |
| 2022-04-19 16:08:20 +0200 | <lyiriyah[m]> | Make sure to install using ghcup and not pacman |
| 2022-04-19 16:11:59 +0200 | <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 16:12:24 +0200 | <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 16:16:16 +0200 | <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 16:16:35 +0200 | <geekosaur> | which means what arch packages *is* unstable |
| 2022-04-19 16:16:59 +0200 | <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 16:18:50 +0200 | <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 16:25:38 +0200 | <abastro[m]> | Ignoring version bounds???? |
| 2022-04-19 16:27:21 +0200 | <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 16:27:51 +0200 | <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 16:28:06 +0200 | <geekosaur> | it was pretty ugly |
| 2022-04-19 16:28:37 +0200 | <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 16:29:34 +0200 | <abastro[m]> | Oh noo |
| 2022-04-19 16:29:39 +0200 | <abastro[m]> | Why is arch repo managed like this |
| 2022-04-19 16:30:16 +0200 | <geekosaur> | you would have to ask them |
| 2022-04-19 16:30:33 +0200 | <abastro[m]> | :P |
| 2022-04-19 16:30:36 +0200 | <geekosaur> | at this point we just tell people touse ghcup and ignore the arch repo for anything haskell related |
| 2022-04-19 16:30:38 +0200 | <Ether[m]> | Arch used to be awesome |
| 2022-04-19 16:30:45 +0200 | <Ether[m]> | Its getting worse.. |
| 2022-04-19 16:30:48 +0200 | <geekosaur> | it'sfine for anything else |
| 2022-04-19 16:31:15 +0200 | <Ether[m]> | geekosaur: Not really, systemd and all the broken packages |
| 2022-04-19 16:31:16 +0200 | <geekosaur> | keep in mindthat rolling release is a lot of work as more and more packages interact |
| 2022-04-19 16:31:36 +0200 | <geekosaur> | there'sa reason it's an uncommon way of managing distributions |
| 2022-04-19 16:31:44 +0200 | <Ether[m]> | Some of the core packages are broken too |
| 2022-04-19 16:32:58 +0200 | <abastro[m]> | Are many package managers like this? |
| 2022-04-19 16:33:12 +0200 | <abastro[m]> | I wonder how they somehow work in a sense.. |
| 2022-04-19 16:33:58 +0200 | <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 16:35:11 +0200 | <Ether[m]> | Wow what a pain! |
| 2022-04-19 16:35:19 +0200 | <Ether[m]> | I pitty you.. |
| 2022-04-19 16:35:52 +0200 | abastro | (~abab9579@220.75.216.63) |
| 2022-04-19 16:39:44 +0200 | <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 16:40:20 +0200 | <geekosaur> | not yet |
| 2022-04-19 16:40:29 +0200 | <geekosaur> | haven't really seen anyone around #ghc |
| 2022-04-19 16:40:43 +0200 | <geekosaur> | you may want to monitor it via matrix so you get logs |
| 2022-04-19 16:40:53 +0200 | <abastro> | Thank you! Yea I joined via matrix as well |
| 2022-04-19 16:41:11 +0200 | <abastro> | So ye I can check log myself from now on |
| 2022-04-19 16:43:32 +0200 | <geekosaur> | oh goodie, reboot in my near future |
| 2022-04-19 16:49:04 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) (Quit: Leaving) |
| 2022-04-19 16:56:30 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) |
| 2022-04-19 17:05:25 +0200 | <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 17:12:43 +0200 | <geekosaur> | we are very careful to not commit things that will break someone's running xmonad |
| 2022-04-19 17:13:01 +0200 | <geekosaur> | after all, it's how you interact with the computer |
| 2022-04-19 17:20:34 +0200 | Natch | (~natch@c-9e07225c.038-60-73746f7.bbcust.telenor.se) |
| 2022-04-19 17:20:47 +0200 | <abastro> | I cannot coerce over X.. :( |
| 2022-04-19 17:21:24 +0200 | <geekosaur> | ? |
| 2022-04-19 17:30:39 +0200 | abiss27 | (~abiss27@user/abiss) |
| 2022-04-19 17:33:56 +0200 | stackdroid18 | (14094@user/stackdroid) |
| 2022-04-19 17:36:53 +0200 | <abastro> | I am using ExtensibleState facility. |
| 2022-04-19 17:37:15 +0200 | <abastro> | (Realized it would be useful for persistent state) |
| 2022-04-19 17:37:58 +0200 | <geekosaur> | that'll break coercion, yep |
| 2022-04-19 17:38:07 +0200 | <geekosaur> | type level shenanigans often do |
| 2022-04-19 17:38:20 +0200 | <geekosaur> | even though XS is relatively simple as such go |
| 2022-04-19 17:38:33 +0200 | <abastro> | It's simply because the constructor is not exported, I think. |
| 2022-04-19 17:38:47 +0200 | <abastro> | (Or isn't it?) |
| 2022-04-19 17:39:03 +0200 | <abastro> | That, or just `coerce` being overly fragile |
| 2022-04-19 17:47:08 +0200 | abastro | (~abab9579@220.75.216.63) (Remote host closed the connection) |
| 2022-04-19 17:49:54 +0200 | twiclo | (~twiclo@mail.twil.cx) (Ping timeout: 276 seconds) |
| 2022-04-19 17:51:35 +0200 | twiclo | (~twiclo@vpn.utahbroadband.com) |
| 2022-04-19 17:58:00 +0200 | <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 17:58:43 +0200 | <Ether[m]> | https://github.com/Ahanaf-Ether/xmonad/blob/stable/x.hs |
| 2022-04-19 17:59:09 +0200 | abastro | (~abab9579@220.75.216.63) |
| 2022-04-19 18:05:51 +0200 | <abastro> | Hmm `XMonad.Config.Prime` irks me |
| 2022-04-19 18:06:15 +0200 | <abastro> | Easier for imperative programmers.. ee |
| 2022-04-19 18:13:49 +0200 | <geekosaur> | it's going away |
| 2022-04-19 18:15:43 +0200 | <abastro> | Oh. |
| 2022-04-19 18:15:47 +0200 | <abastro> | "This module is a perpetual draft and will therefore be removed from xmonad-contrib in the near future." |
| 2022-04-19 18:16:58 +0200 | <geekosaur> | it was an experimental new way of configuring xmonad. it never really went anywhere and works poorly with many contrib modules because you have to work out how to integrate it yourself, the standard instructions generally don't work |
| 2022-04-19 18:17:54 +0200 | <abastro> | I see |
| 2022-04-19 18:18:13 +0200 | <abastro> | Personally I think declarative syntax works better for configs |
| 2022-04-19 18:18:41 +0200 | <abastro> | (I guess "wrapping by ewmh etc" part is a bit confusing tho) |
| 2022-04-19 18:19:12 +0200 | <geekosaur> | that stuff allcame after X.C.Prime anyway,mostof the combinator style stuff is within the past few years |
| 2022-04-19 18:19:26 +0200 | <geekosaur> | ]originally you had to stick hooks everywhere |
| 2022-04-19 18:20:04 +0200 | <geekosaur> | Ether[m], I don't know why you think throwing a thousand line config at me and expecting me to understand it immediately is going to work well |
| 2022-04-19 18:20:05 +0200 | <abastro[m]> | Stick hooks? |
| 2022-04-19 18:20:27 +0200 | Ether[m] | uploaded an image: (275KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/XaKhFUKpHpvZheEhnBxdybcv/20220419_222… > |
| 2022-04-19 18:20:29 +0200 | <geekosaur> | you had to manually add the hooks to your startupHook, logHook, etc. |
| 2022-04-19 18:20:50 +0200 | <Ether[m]> | Trying to install 0.17 getting this error, do use sudo? |
| 2022-04-19 18:21:01 +0200 | <geekosaur> | almost never do you want sudo |
| 2022-04-19 18:21:09 +0200 | <abastro[m]> | geekosaur: <del>Oh, I mean I am okay with that</del> |
| 2022-04-19 18:21:29 +0200 | <Ether[m]> | geekosaur: Any idea why i am getting this error |
| 2022-04-19 18:22:31 +0200 | <geekosaur> | ls -ld ~/.config/xmonad |
| 2022-04-19 18:22:40 +0200 | <geekosaur> | run that, pastebin the result |
| 2022-04-19 18:25:49 +0200 | <Ether[m]> | geekosaur: Is that a capital i? |
| 2022-04-19 18:26:22 +0200 | <abastro[m]> | I think it is l |
| 2022-04-19 18:26:26 +0200 | <Ether[m]> | Yep |
| 2022-04-19 18:26:29 +0200 | <abastro[m]> | You know, l |
| 2022-04-19 18:26:33 +0200 | <geekosaur> | loweercase l for both |
| 2022-04-19 18:26:48 +0200 | <Ether[m]> | geekosaur: Nothing to paste bin |
| 2022-04-19 18:26:52 +0200 | abastro | (~abab9579@220.75.216.63) (Ping timeout: 246 seconds) |
| 2022-04-19 18:26:58 +0200 | <geekosaur> | huh? |
| 2022-04-19 18:27:03 +0200 | <Ether[m]> | It just shows contents of the directory |
| 2022-04-19 18:27:15 +0200 | <abastro[m]> | No content in the directory I guess |
| 2022-04-19 18:27:25 +0200 | <abastro[m]> | Eh |
| 2022-04-19 18:27:26 +0200 | <abastro[m]> | Well |
| 2022-04-19 18:27:31 +0200 | <geekosaur> | then you did something wrong |
| 2022-04-19 18:27:49 +0200 | <geekosaur> | -lmeans long listing, -d means show the directory itself instead of its contents |
| 2022-04-19 18:27:58 +0200 | <abastro[m]> | Doesn't it show permission |
| 2022-04-19 18:28:02 +0200 | <Ether[m]> | geekosaur: I did? |
| 2022-04-19 18:28:13 +0200 | <abastro[m]> | Oh |
| 2022-04-19 18:28:51 +0200 | <geekosaur> | example output: https://paste.tomsmeding.com/cyM5clBe |
| 2022-04-19 18:29:07 +0200 | Ether[m] | uploaded an image: (302KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/RZTnXAswxbAVfWyxokqlrbZX/20220419_222… > |
| 2022-04-19 18:29:43 +0200 | <abastro[m]> | Why is it owned by root |
| 2022-04-19 18:29:54 +0200 | <abastro[m]> | Now this is curious situation |
| 2022-04-19 18:30:03 +0200 | <geekosaur> | no idea, I assume you used sudo at some point when you shouldn't have |
| 2022-04-19 18:30:11 +0200 | <geekosaur> | sudo is a big hammer, it should be avoided |
| 2022-04-19 18:30:27 +0200 | <Ether[m]> | I think i used it to move the file |
| 2022-04-19 18:30:27 +0200 | <abastro[m]> | Something owned by root in home directory.. |
| 2022-04-19 18:31:15 +0200 | <Ether[m]> | abastro[m]: Yep thats the case |
| 2022-04-19 18:31:22 +0200 | <Ether[m]> | Had to run chown |
| 2022-04-19 18:31:30 +0200 | <Ether[m]> | It works not, thanks |
| 2022-04-19 18:31:33 +0200 | <geekosaur> | and I expect a lot of stuff to break if anything else in .config is owned by root |
| 2022-04-19 18:31:35 +0200 | <Ether[m]> | Noe* |
| 2022-04-19 18:31:42 +0200 | <Ether[m]> | Now* |
| 2022-04-19 18:31:47 +0200 | <geekosaur> | you type almost as bad as I do :þ |
| 2022-04-19 18:36:06 +0200 | <abastro[m]> | What is different between forkIO and forkProcess? |
| 2022-04-19 18:38:18 +0200 | <geekosaur> | everything :) |
| 2022-04-19 18:38:24 +0200 | <geekosaur> | forkIO creates a new thread |
| 2022-04-19 18:38:33 +0200 | <geekosaur> | forkProcess creates a new process |
| 2022-04-19 18:38:36 +0200 | <abastro[m]> | Oh |
| 2022-04-19 18:38:45 +0200 | <abastro[m]> | How about forkOS? |
| 2022-04-19 18:38:47 +0200 | <geekosaur> | linux tried to combine those in the 2.x days, it wasa disaster |
| 2022-04-19 18:39:04 +0200 | <geekosaur> | forkOS makes a bound thread (the Haskell thread always runs on the same OS thread) |
| 2022-04-19 18:39:59 +0200 | stackdroid18 | (14094@user/stackdroid) (Quit: hasta la vista... tchau!) |
| 2022-04-19 18:40:05 +0200 | <geekosaur> | you need forkOS if the thread makes use of FFI that uses thread-local storage, or similar |
| 2022-04-19 18:40:12 +0200 | <abastro[m]> | Meh I wonder why forkProcess is not part of base |
| 2022-04-19 18:40:31 +0200 | <geekosaur> | you can't do it on Windows |
| 2022-04-19 18:40:39 +0200 | <abastro[m]> | In this application of xmonad, it doesn't matter but.. if you want to fork a procees.. |
| 2022-04-19 18:40:59 +0200 | <geekosaur> | windows can spawn a new program, but not duplicate a process like forkProcess does |
| 2022-04-19 18:41:25 +0200 | <abastro[m]> | What do you do in Windows if you want to create a copy program? |
| 2022-04-19 18:41:35 +0200 | <geekosaur> | (not that unix's fork()+exec() turns out to be a good API) |
| 2022-04-19 18:41:48 +0200 | <abastro[m]> | Oh wait |
| 2022-04-19 18:42:01 +0200 | Ether[m] | uploaded an image: (266KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/wAtmwwtcMzeIHjnelMBSCdWp/20220419_224… > |
| 2022-04-19 18:42:15 +0200 | <Ether[m]> | Jeez what did i do? |
| 2022-04-19 18:42:22 +0200 | <geekosaur> | you don't. and you don't generally want to; back in theold days the only uses of fork() were immediately followed by exec() (which is windows' "spawn") or as a workaround for lack of threads |
| 2022-04-19 18:42:27 +0200 | <abastro[m]> | I learned it the linux way so I did not think of spawning executable as brand new |
| 2022-04-19 18:43:05 +0200 | <geekosaur> | but then, back in the old days fork() was cheap enough that it basically worked as an alternative to threads, for most stuff |
| 2022-04-19 18:44:07 +0200 | <geekosaur> | o.O |
| 2022-04-19 18:45:09 +0200 | stackdroid18 | (~stackdroi@user/stackdroid) |
| 2022-04-19 18:46:18 +0200 | <abastro[m]> | geekosaur: Meh, I guess I should be more familiar with building multiple executables |
| 2022-04-19 18:46:24 +0200 | <geekosaur> | Ether[m], when you installed ghcup, did you do it as root? |
| 2022-04-19 18:46:43 +0200 | <Ether[m]> | I think |
| 2022-04-19 18:46:44 +0200 | <geekosaur> | althouhg I can't see why that would produce *that* error |
| 2022-04-19 18:47:05 +0200 | <geekosaur> | but it sounds like you need to nuke ~/.ghcup and start over |
| 2022-04-19 18:47:11 +0200 | <Ether[m]> | geekosaur: Wait what, i didn't |
| 2022-04-19 18:47:29 +0200 | <Ether[m]> | I am on debian |
| 2022-04-19 18:49:57 +0200 | <Ether[m]> | You dont install ghcup in debian its supposed to be installed as a dependency |
| 2022-04-19 18:50:09 +0200 | <Ether[m]> | I think* |
| 2022-04-19 18:50:33 +0200 | <geekosaur> | you switched from arch? |
| 2022-04-19 18:50:46 +0200 | <geekosaur> | is your stack from debian then? |
| 2022-04-19 18:51:00 +0200 | <geekosaur> | in that case it might be old enough that the first thing you need to do is stack upgrade |
| 2022-04-19 18:51:16 +0200 | <Ether[m]> | I did |
| 2022-04-19 18:51:30 +0200 | <Ether[m]> | I am follow the xmonad guide |
| 2022-04-19 18:51:34 +0200 | <geekosaur> | unless you run debian testing |
| 2022-04-19 18:51:45 +0200 | <geekosaur> | which might be close enough to arch to make you happy |
| 2022-04-19 18:51:48 +0200 | <Ether[m]> | And fyi i am on debian unstable |
| 2022-04-19 18:51:52 +0200 | <geekosaur> | ah |
| 2022-04-19 18:52:02 +0200 | <Ether[m]> | Meh |
| 2022-04-19 18:52:13 +0200 | <geekosaur> | I found that a little *too* unstable back when I tried it, but who knows |
| 2022-04-19 18:52:25 +0200 | <Ether[m]> | Only for sake of trying xmonad 0.17 |
| 2022-04-19 18:52:43 +0200 | <Ether[m]> | I think i have to edit stack.yaml |
| 2022-04-19 18:56:05 +0200 | <geekosaur> | congratulations,k there are no hits for that gcc error in a web search :/ |
| 2022-04-19 18:56:42 +0200 | <geekosaur> | somehow you have confused the hell out of stack |
| 2022-04-19 18:58:58 +0200 | <Ether[m]> | Turns out i did not clone xmonad and xmonad-contrib in .config/xmonad |
| 2022-04-19 18:59:10 +0200 | <Ether[m]> | It was in my home directory 🤣 |
| 2022-04-19 19:05:53 +0200 | <geekosaur> | that shouldn't matter, it still shouldn't throw a weird gcc error while installing ghc |
| 2022-04-19 19:06:18 +0200 | <geekosaur> | (I mean, I know why it runs gcc during ghc install, but it still shouldn't get that error) |
| 2022-04-19 19:09:54 +0200 | gdd | (~gdd@129.199.146.230) (Ping timeout: 272 seconds) |
| 2022-04-19 19:10:22 +0200 | gdd | (~gdd@129.199.146.230) |
| 2022-04-19 20:57:53 +0200 | abiss27 | (~abiss27@user/abiss) (Quit: hasta la vista... tchau!) |
| 2022-04-19 21:50:52 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) (Remote host closed the connection) |
| 2022-04-19 21:54:20 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) |
| 2022-04-19 22:34:40 +0200 | twiclo | (~twiclo@vpn.utahbroadband.com) (Ping timeout: 246 seconds) |
| 2022-04-19 22:36:54 +0200 | twiclo | (~twiclo@mail.twil.cx) |
| 2022-04-19 23:41:05 +0200 | jeeeun0 | (~jeeeun@78.40.148.178) |
| 2022-04-19 23:41:36 +0200 | jeeeun | (~jeeeun@78.40.148.178) (Ping timeout: 272 seconds) |
| 2022-04-19 23:41:36 +0200 | jeeeun0 | jeeeun |
