| 2022-04-03 00:27:00 +0200 | mvk | (~mvk@2607:fea8:5ce3:8500::3800) (Ping timeout: 240 seconds) |
| 2022-04-03 00:53:36 +0200 | steve_ | (~steve@ool-182c2b80.dyn.optonline.net) |
| 2022-04-03 01:10:24 +0200 | thunderrd | (~thunderrd@183.182.111.150) (Remote host closed the connection) |
| 2022-04-03 01:34:08 +0200 | steve_ | (~steve@ool-182c2b80.dyn.optonline.net) (Ping timeout: 260 seconds) |
| 2022-04-03 02:35:58 +0200 | benin | (~benin@183.82.204.110) (Ping timeout: 260 seconds) |
| 2022-04-03 03:28:48 +0200 | mvk | (~mvk@2607:fea8:5ce3:8500::3800) |
| 2022-04-03 04:04:38 +0200 | banc | (banc@gateway/vpn/airvpn/banc) (Ping timeout: 260 seconds) |
| 2022-04-03 04:24:47 +0200 | banc | (banc@gateway/vpn/airvpn/banc) |
| 2022-04-03 05:37:31 +0200 | benin | (~benin@183.82.204.110) |
| 2022-04-03 06:31:00 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection) |
| 2022-04-03 06:32:09 +0200 | <anon_kun600[m]> | geekosaur: I only used a small example config with some explanations for how everything worked, it seems its a little outdated since I get some error on startup, also with errors I have to highlight the text to make it appear since I guess I need to change the basic color but other than that it seems to work. |
| 2022-04-03 06:43:42 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-04-03 06:53:21 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 256 seconds) |
| 2022-04-03 07:13:38 +0200 | benin | (~benin@183.82.204.110) (Ping timeout: 246 seconds) |
| 2022-04-03 07:26:14 +0200 | benin | (~benin@183.82.204.110) |
| 2022-04-03 07:31:00 +0200 | mvk | (~mvk@2607:fea8:5ce3:8500::3800) (Ping timeout: 240 seconds) |
| 2022-04-03 07:32:23 +0200 | <abastro[m]> | I wonder why there are not so many tutorials pointing out that PATH needs to be set up. I used to struggle a lot at some errors, and it turns out to be from "xmonad not on PATH" issues. |
| 2022-04-03 07:37:35 +0200 | <Solid> | installing with stack or cabal puts the xmonad executable into a non-standard (i.e., probably not already in your $PATH) directory |
| 2022-04-03 07:37:55 +0200 | <Solid> | many display managers have trouble finding it in that case |
| 2022-04-03 07:44:03 +0200 | <abastro[m]> | Indeed, and I could not find the help around that |
| 2022-04-03 07:44:42 +0200 | <abastro[m]> | In fact, while currently I have it solved, when I was wondering and searching I could not find the culprit for months. Is this documented somewhere? |
| 2022-04-03 07:47:55 +0200 | <Solid> | it should be in INSTALL |
| 2022-04-03 07:55:37 +0200 | <abastro[m]> | Oh, it says that "Make sure to add that directory to your $PATH". Tho it does not specify how. Given how startup shell is different from terminal emulators, wouldn't it better to specify it with more details? |
| 2022-04-03 07:57:42 +0200 | <abastro[m]> | Like putting command to update $PATH in `.xsession` |
| 2022-04-03 07:58:55 +0200 | <abastro[m]> | For me, `xmonad` worked well in terminal emulators because `.bashrc` took care of it. However, it does not apply to .xsessions |
| 2022-04-03 08:05:27 +0200 | <Solid> | I think it goes into quite some detail in https://xmonad.org/INSTALL.html#make-xmonad-your-window-manager |
| 2022-04-03 08:05:31 +0200 | <Solid> | what do you think is missing? |
| 2022-04-03 08:09:30 +0200 | <abastro[m]> | IIRC, simply `exec xmonad` does not work there. You need to manually change PATH variable beforehand. |
| 2022-04-03 08:09:50 +0200 | <abastro[m]> | PATH update at `~/.bashrc` does not apply there. |
| 2022-04-03 08:11:25 +0200 | <Solid> | I see |
| 2022-04-03 08:11:41 +0200 | <Solid> | I don't use a display manager but if you want to open a PR with a doc fix that would be greatly appreciated! |
| 2022-04-03 08:18:57 +0200 | <abastro[m]> | Yep, perhaps it only applies my case though, so I'll first put in the case about my setup (ubuntu - gdm) first. |
| 2022-04-03 09:29:00 +0200 | iqubic | (~iqubic@2601:602:9502:c70:1794:2be1:4637:cbf5) |
| 2022-04-03 09:29:17 +0200 | <iqubic> | How does one set their default mouse cursor when using XMonad? |
| 2022-04-03 09:35:00 +0200 | <Yehoshua> | With xsetroot |
| 2022-04-03 09:36:20 +0200 | <iqubic> | Thanks. |
| 2022-04-03 09:36:52 +0200 | iqubic | (~iqubic@2601:602:9502:c70:1794:2be1:4637:cbf5) (Quit: Client closed) |
| 2022-04-03 09:40:38 +0200 | iqubic | (~iqubic@2601:602:9502:c70:1794:2be1:4637:cbf5) |
| 2022-04-03 09:41:25 +0200 | <iqubic> | Is it fine to just put an xsetroot in my .xinitrc, or do I need to do something more fancy for xmonad to pick up my new cursor? |
| 2022-04-03 09:55:22 +0200 | x88x88x | (~x88x88x@149.28.53.172) (Quit: ZNC - https://znc.in) |
| 2022-04-03 11:00:06 +0200 | GustavoNasciment | (~gutsvaomm@2001:470:69fc:105::1:cfca) (Quit: You have been kicked for being idle) |
| 2022-04-03 11:00:09 +0200 | M5271[m] | (~fivetwose@2001:470:69fc:105::1:d0e7) (Quit: You have been kicked for being idle) |
| 2022-04-03 11:00:11 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2022-04-03 11:00:45 +0200 | x88x88x | (~x88x88x@2001:19f0:5:39a8:5400:3ff:feb6:73cb) |
| 2022-04-03 11:47:39 +0200 | <Solid[m]> | you can just put it into your xinitrc |
| 2022-04-03 12:03:13 +0200 | Natch | (~natch@c-67bae255.014-297-73746f25.bbcust.telenor.se) (Remote host closed the connection) |
| 2022-04-03 12:05:37 +0200 | <geekosaur> | abastro[m], how you set up $PATH depends on how your session is set up and to some extent on what system you're on; it rapidly becomes a bit of a mess |
| 2022-04-03 12:05:52 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) |
| 2022-04-03 12:08:36 +0200 | Natch | (~natch@c-67bae255.014-297-73746f25.bbcust.telenor.se) |
| 2022-04-03 12:57:40 +0200 | <geekosaur> | anon_kun600[m], you can pastebin your config and we can look it over |
| 2022-04-03 12:57:44 +0200 | <geekosaur> | @where paste |
| 2022-04-03 12:57:44 +0200 | <lambdabot> | Help us help you: please paste full code, input and/or output at e.g. https://paste.tomsmeding.com |
| 2022-04-03 12:59:45 +0200 | <MrElendig> | iqubic: consider using XMonad.Util.Cursor |
| 2022-04-03 15:46:09 +0200 | <Ether[m]> | How do I toggle monocle with Mod and f? |
| 2022-04-03 15:46:46 +0200 | <Ether[m]> | Rather than Mod-f for full screen I would like to use monocle layout. |
| 2022-04-03 15:57:52 +0200 | mekeor[m] | (~mekeormat@2001:470:69fc:105::17e4) |
| 2022-04-03 15:58:10 +0200 | <mekeor[m]> | hello fellows :) |
| 2022-04-03 15:58:39 +0200 | <mekeor[m]> | my XMonad.Prompt won't show up anymore. how can i debug this? |
| 2022-04-03 16:06:38 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-04-03 16:08:21 +0200 | <Solid> | mekeor[m]: check your xsession.errors or similar (though when the prompt doesn't show up at all it's almost always a font issue) |
| 2022-04-03 16:08:31 +0200 | <Solid> | Ether[m]: what's the monocle layout? |
| 2022-04-03 16:36:50 +0200 | <mekeor[m]> | Solid: i set `XPC { font = "xft:Hack:pixelsize=12", ... }` and i have the Hack font installed as confirmed with fc-list. also, my ~/.local/share/xorg/Xorg.0.log does not show any errors when i try to invoke my prompt :/ |
| 2022-04-03 16:39:09 +0200 | mekeor[m] | wonders why files called "-no-pie" keep occuring in ~/.xmonad |
| 2022-04-03 16:41:03 +0200 | mc47 | (~mc47@xmonad/TheMC47) |
| 2022-04-03 16:41:30 +0200 | <vrs> | proto-indoeuropean locale sounds unlikely |
| 2022-04-03 16:44:34 +0200 | <mekeor[m]> | ah, it was occuring every time i ran ~/.xmonad/build myself manually -- without passing xmonad-x86_64-linux as first cli-parameter |
| 2022-04-03 16:45:18 +0200 | <mekeor[m]> | anyway, my prompt is still not showing up. hm |
| 2022-04-03 16:49:53 +0200 | <geekosaur> | Xorg.0.log won't be the place to look, that's the server log and xft: designates a client-sidefont |
| 2022-04-03 16:50:04 +0200 | <geekosaur> | you want your session log (often ~/.xsession-errors) |
| 2022-04-03 17:21:00 +0200 | <mekeor[m]> | thank you. for me, my logs were actually stdout because i call `xinit` directly. it stated that there was a problem with my xpc-config. instead of defining from scratch myself, i switched to update the default implementation `def` per update-syntax. it works now, yay! :) |
| 2022-04-03 17:22:13 +0200 | <geekosaur> | it didn't tell you what the problem was? |
| 2022-04-03 17:30:43 +0200 | <mekeor[m]> | it did. that my xpc-config was missing a field and it also told me the fields name :) |
| 2022-04-03 17:31:23 +0200 | <Solid> | so it was a compilation error? |
| 2022-04-03 17:32:02 +0200 | <Solid> | oh, you might be able to construct partial records if fields are non-strict |
| 2022-04-03 17:32:09 +0200 | <Solid> | which would then fail at runtime |
| 2022-04-03 17:33:09 +0200 | <abastro[m]> | Oh.. haskell records.. |
| 2022-04-03 17:35:43 +0200 | <Solid> | are you going to elaborate on that or...? :) |
| 2022-04-03 17:39:03 +0200 | <abastro[m]> | * haskell records.. why do you let us to shoot on foot by allowing undefined fields |
| 2022-04-03 17:39:26 +0200 | <Solid> | there's probably at least a warning emitted there |
| 2022-04-03 17:39:37 +0200 | <Solid> | (definitely with -Wall) |
| 2022-04-03 17:39:49 +0200 | <Solid> | but most people just compiling their xmonad configs don't care too much about that ;) |
| 2022-04-03 17:41:40 +0200 | <abastro[m]> | Yep, indeed |
| 2022-04-03 17:41:40 +0200 | <abastro[m]> | Even -W is easy to miss for average user |
| 2022-04-03 17:41:43 +0200 | <mekeor[m]> | Solid: exactly, fields were non strict. |
| 2022-04-03 17:43:11 +0200 | mekeor[m] | adds -Wall to build-script |
| 2022-04-03 17:44:39 +0200 | <abastro[m]> | I wonder if -Werror would help or undermine |
| 2022-04-03 17:44:59 +0200 | <Solid> | I've wondered whether we should add -XStrictData to the build options a few times |
| 2022-04-03 17:45:10 +0200 | <Solid> | surely any breakage that it would cause would be a bug |
| 2022-04-03 18:00:06 +0200 | AngryBromide[m] | (~angrybrom@2001:470:69fc:105::1:cfb3) (Quit: You have been kicked for being idle) |
| 2022-04-03 18:00:13 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2022-04-03 18:09:01 +0200 | superusercode[m] | (~sudousrco@2001:470:69fc:105::1:ee77) |
| 2022-04-03 18:21:27 +0200 | superusercode[m] | superusercode |
| 2022-04-03 18:30:36 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 272 seconds) |
| 2022-04-03 18:52:51 +0200 | iqubic | (~iqubic@2601:602:9502:c70:1794:2be1:4637:cbf5) (Quit: Client closed) |
| 2022-04-03 19:05:01 +0200 | <geekosaur> | Solid, no actually. we already have a few cases where we warn people to use hacky workarounds for strict fields because you end up with a cycle otherwise (see for example https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Util-EZConfig.html#v:checkKe…) |
| 2022-04-03 19:05:16 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) |
| 2022-04-03 19:24:50 +0200 | superusercode | (~sudousrco@2001:470:69fc:105::1:ee77) (Quit: Reconnecting) |
| 2022-04-03 19:25:04 +0200 | superusercode | (~sudousrco@2001:470:69fc:105::1:ee77) |
| 2022-04-03 19:27:51 +0200 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2022-04-03 19:30:06 +0200 | <Solid> | huh interesting |
| 2022-04-03 19:30:27 +0200 | <Solid> | but I don't suppose we have many mutually recursive fields in contrib |
| 2022-04-03 19:31:15 +0200 | <geekosaur> | none by default, but you do have to watch out for that with the strict fields |
| 2022-04-03 19:31:38 +0200 | <geekosaur> | (note that strict is only t WHNF which is why a simple `return ()` works as a loop-breaker) |
| 2022-04-03 19:31:55 +0200 | mc47 | (~mc47@xmonad/TheMC47) |
| 2022-04-03 20:05:27 +0200 | rekahsoft | (~rekahsoft@cpe001b21a2fd89-cm64777ddc63a0.cpe.net.cable.rogers.com) |
| 2022-04-03 20:46:03 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-04-03 21:16:02 +0200 | rekahsoft | (~rekahsoft@cpe001b21a2fd89-cm64777ddc63a0.cpe.net.cable.rogers.com) (Read error: Connection reset by peer) |
| 2022-04-03 21:16:26 +0200 | rekahsoft | (~rekahsoft@cpe001b21a2fd89-cm64777ddc63a0.cpe.net.cable.rogers.com) |
| 2022-04-03 21:20:36 +0200 | mvk | (~mvk@2607:fea8:5ce3:8500::3800) |
| 2022-04-03 21:56:48 +0200 | mvk | (~mvk@2607:fea8:5ce3:8500::3800) (Ping timeout: 260 seconds) |