Home liberachat/#xmonad: Logs Calendar

Logs on 2021-09-04 (liberachat/#xmonad)

00:00:03 × nomadxx3 quits (~lanomadx@208.91.64.181) (*.net *.split)
00:00:03 × benin0369323 quits (~benin@183.82.179.90) (*.net *.split)
00:00:03 × td_ quits (~td@muedsl-82-207-238-018.citykom.de) (*.net *.split)
00:00:03 × kr1x quits (~kriket@170.249.0.122) (*.net *.split)
00:00:03 × jsoo quits (~znc@irc.refl.club) (*.net *.split)
00:00:19 nomadxx3 joins (~lanomadx@208.91.64.181)
00:00:45 kr1x joins (~kriket@170.249.0.122)
00:02:03 jsoo joins (~znc@irc.refl.club)
00:05:16 td_ joins (~td@muedsl-82-207-238-018.citykom.de)
00:06:00 × kr1x quits (~kriket@170.249.0.122) (Quit: .)
01:23:21 sagax joins (~sagax_nb@user/sagax)
01:36:57 nomadxxxx3 joins (~lanomadx@69.167.42.182)
01:38:10 × nomadxx3 quits (~lanomadx@208.91.64.181) (Ping timeout: 240 seconds)
02:03:10 × banc quits (banc@gateway/vpn/airvpn/banc) (Ping timeout: 240 seconds)
02:03:27 × pl quits (sid98063@id-98063.helmsley.irccloud.com) (Ping timeout: 240 seconds)
02:06:23 pl joins (sid98063@id-98063.helmsley.irccloud.com)
02:20:32 × td_ quits (~td@muedsl-82-207-238-018.citykom.de) (Ping timeout: 245 seconds)
02:22:38 td_ joins (~td@94.134.91.73)
02:24:14 banc joins (banc@gateway/vpn/airvpn/banc)
02:45:20 × eyenx quits (~m-5paiux@eyenx.ch) (Remote host closed the connection)
02:46:09 eyenx joins (~m-5paiux@eyenx.ch)
04:04:37 × Nahra quits (~user@static.161.95.99.88.clients.your-server.de) (Ping timeout: 252 seconds)
07:03:19 wonko joins (~wjc@62.115.229.50)
07:11:53 × geekosaur quits (~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
07:17:29 geekosaur joins (~geekosaur@xmonad/geekosaur)
07:29:48 seschwar joins (~seschwar@user/seschwar)
08:17:44 allbery_b joins (~geekosaur@xmonad/geekosaur)
08:17:44 × geekosaur quits (~geekosaur@xmonad/geekosaur) (Killed (NickServ (GHOST command used by allbery_b)))
08:17:47 allbery_b is now known as geekosaur
08:29:57 Andrew is now known as AhkilKumar
08:30:26 AhkilKumar is now known as Andrew
09:10:38 Nahra joins (~user@static.161.95.99.88.clients.your-server.de)
10:01:20 mc47 joins (~mc47@xmonad/TheMC47)
10:04:35 frosch03 joins (~user@2a02:8070:7ab:1b00:1f4a:4f79:a4cd:c73)
10:04:35 × frosch03 quits (~user@2a02:8070:7ab:1b00:1f4a:4f79:a4cd:c73) (Client Quit)
12:43:18 × wonko quits (~wjc@62.115.229.50) (Ping timeout: 256 seconds)
13:16:43 <yuu[m]> is there a specific reason on why workspaces are limited to 9? i mean i've seen ways to workaround that, but i don't see why this was designed this way.
13:17:40 <f-a> I guess because there are 9 numbered keys
13:17:42 <Solid> it was... not? :D
13:17:53 <Solid> you can have as many workspaces as you like
13:18:53 Solid has 25 :]
13:19:57 <yuu[m]> Solid: i mean on the source code https://github.com/xmonad/xmonad/blob/f89df98f4022b5142760b86a2ad85b4e90e583b3/src/XMonad/Config.hs#L59
13:20:10 <yuu[m]> 1 .. 9
13:20:42 <Solid> this is the default config, where it was decided that 9 workspaces seem like a decent default to have
13:21:40 <Solid> You can see in line 261 that these are just assigned to XConfig's `workspaces` field
13:22:07 <Solid> there's nothing stopping you from doing `map show [1 .. 100 :: Int]` :)
13:26:25 <yuu[m]> i mean i was thinking in suggesting to make that an infinite range, but wanted to know the reason behind the 9, but like f-a said that's likely because of the number keys on the keyboard
13:27:02 <f-a> tho there are *ten* numbered keys, of course
13:36:08 <yuu[m]> solid do you have your config public just so that i can see your way to achieve 25 workspaces? i've seen some 3 ways to achieve, but i'm not sure what's the best
13:37:28 <f-a> yuu[m]: out of curiosity, how will you bind them? ⌂+n for the first 10 and then ⌂+⇧+n for other ten?
13:37:43 <f-a> or do you just iterate «next workspace» and «previous workspace»?
13:38:50 <Solid> yuu[m]: sure, though it might not be the easiest thing to understand: https://gitlab.com/slotThe/dotfiles/-/blob/master/xmonad/.config/xmonad/xmonad.hs#L211
13:39:19 <Solid> the main thing I think you saw people do differently is keybindings; I mostly don't bother with that, only binding the first 10 workspaces ( https://gitlab.com/slotThe/dotfiles/-/blob/master/xmonad/.config/xmonad/xmonad.hs#L673 )
13:39:41 <Solid> for anything else I use X.P.Workspace
13:42:56 <yuu[m]> i actually just want 12 workspaces so from 1 until =. i guess you could make something akin to emacs where you prefix a number to a key, eg `Super-24 w`
13:43:58 <yuu[m]> Solid: thank you!
13:44:19 × mc47 quits (~mc47@xmonad/TheMC47) (Remote host closed the connection)
13:46:45 × f-a quits (f2a@f2a.jujube.ircnow.org) (Remote host closed the connection)
13:48:39 <Solid> oh then you just need the keybinding part
13:53:03 <Solid> yuu[m]: something like http://ix.io/3xUW should be a minimal working example
13:58:32 <geekosaur> https://github.com/geekosaur/xmonad.hs/blob/pyanfar/xmonad.hs#L220-L225
14:00:06 <geekosaur> workspacen is defined earlier in the file (and is all names, not numbers; numbers is just so we have something to call the default workspaces)
14:01:09 <geekosaur> it's also somewhat common to have 20 workspaces with the first 10 on mod-<1-10> and the second on mod-<F1-F10>
14:04:02 f2a joins (f2a@f2a.jujube.ircnow.org)
14:05:16 f2a is now known as f-a
14:17:52 × bla quits (~bla@89-67-84-220.dynamic.chello.pl) (Ping timeout: 252 seconds)
14:18:50 <fizzie> I think someone here did workspaces with a two-digit keybinding, which I imagine is achievable with XMonad.Actions.Submap-style logic. Or maybe I'm thinking of IRC client windows instead.
15:39:59 <yuu[m]> Solid: geekosaur thank you!
15:41:01 <yuu[m]> what is the operator i need to use here so that i can have both keys?... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/c147ff51e8dfa36fa18fa82490d4d33e2c3e530d)
15:47:11 <davve> its not about the amount of workspaces, its how you use them!
15:47:45 <geekosaur> yuu[m], what error do you get?
15:49:59 <yuu[m]> geekosaur: oh i should have looked before asking it was just `Variable not in scope: additionalKeys`. fixed! thank you! haskell is kinda magic
15:50:00 <geekosaur> it shouldn't be an operator but it might need parentheses
16:10:19 benin0369323 joins (~benin@183.82.179.90)
16:21:23 × geekosaur quits (~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
16:36:21 geekosaur joins (~geekosaur@xmonad/geekosaur)
16:47:24 qbt joins (~edun@user/edun)
16:47:25 defjam joins (~eb0t@90.194.35.110)
16:49:09 rekahsoft joins (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com)
16:54:54 × defjam quits (~eb0t@90.194.35.110) (Quit: WeeChat 2.3)
16:55:05 defjam joins (~eb0t@90.194.35.110)
17:01:45 benin03693239 joins (~benin@106.198.95.161)
17:03:22 × benin0369323 quits (~benin@183.82.179.90) (Ping timeout: 240 seconds)
17:03:23 benin03693239 is now known as benin0369323
17:09:46 × defjam quits (~eb0t@90.194.35.110) (Quit: WeeChat 2.3)
17:10:47 defjam joins (~eb0t@90.194.35.110)
17:21:29 defjam is now known as rundown
17:21:52 benin03693238 joins (~benin@183.82.207.253)
17:23:35 rundown is now known as eblip
17:23:40 × benin0369323 quits (~benin@106.198.95.161) (Ping timeout: 240 seconds)
17:23:40 benin03693238 is now known as benin0369323
17:24:42 eblip is now known as eb0t
17:26:17 eb0t is now known as defjam
17:26:25 × defjam quits (~eb0t@90.194.35.110) (Quit: WeeChat 2.3)
17:27:13 defjam joins (~eb0t@90.194.35.110)
17:45:43 × defjam quits (~eb0t@90.194.35.110) (Quit: WeeChat 2.3)
17:46:05 defjam joins (~eb0t@90.194.35.110)
17:58:17 × defjam quits (~eb0t@90.194.35.110) (Quit: WeeChat 2.3)
18:06:07 × benin0369323 quits (~benin@183.82.207.253) (Ping timeout: 252 seconds)
18:10:37 defjam joins (~eb0t@90.194.35.110)
18:18:17 jrgiacone joins (~jrgiacone@47.153.194.92)
18:18:20 <jrgiacone> good morning
18:18:36 <jrgiacone> does anyone now how to allow stack to use more cores when compiling updates?
18:18:50 <jrgiacone> ive got 16 threads and it only uses 1
18:19:16 <jrgiacone> know*
18:19:30 <f-a> I know it w/ cabal (-j)
18:19:44 <f-a> are you sure you meant to ask this here (#xmonad), jrgiacone ?
18:20:55 <jrgiacone> yea lol, I only use haskell for xmonad, so I was curious because I build updates from github with stack and just use stack build after updating
18:22:52 <f-a> ah sorry, my bad
18:23:34 <f-a> as I said I do not use stack, but `stack --help | grep core` could be a good starting point. And hang tight, for sure someone is bound to answer
18:24:46 × defjam quits (~eb0t@90.194.35.110) (Quit: WeeChat 2.3)
18:26:26 defjam joins (~eb0t@90.194.35.110)
18:52:33 <Solid> jrgiacone: stack should already build packages in parallel (and use multiple cores for that)
18:53:36 <Solid> if you want to build modules of the same package in parallel then you can just pass -j to `stack build` (or -j16, etc)
18:53:52 bla joins (~bla@89-67-84-220.dynamic.chello.pl)
18:54:18 <Solid> eh, probably `--ghc-options -j16` to directly pass it to ghc
18:55:53 × geekosaur quits (~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
18:57:42 geekosaur joins (~geekosaur@xmonad/geekosaur)
18:58:33 <jrgiacone> hmm solid, my stack only uses one thread when I compile and watch htop
18:59:03 <jrgiacone> but ill try either so like stack build --ghc-options -j16?
18:59:09 <geekosaur> packages, not modules
18:59:39 <liskin> jrgiacone: you can also do this: https://github.com/xmonad/xmonad-contrib/blob/master/stack-master.yaml#L25
18:59:44 <geekosaur> it would build xmonad and xmonad-contrib in parallel, except xmonad-contrib depends on xmonad so it can't
19:00:20 <jrgiacone> ahh, I'll check that out liskin, yea cause contrib only uses one thread when compiling, so i wanted to speed it up
19:00:38 <jrgiacone> ah sick
19:00:54 <jrgiacone> Ill try it on the next update to contrib thanks!
19:01:33 <jrgiacone> liskin, I can add that at the bottom of my stack.yaml?
19:03:28 <Solid> liskin: that doesn't work when building something that depends on contrib right?
19:06:14 <jrgiacone> side note, might not be related to xmonad but more so X11, when my screen turns off after an idle, it seems to revert to an auto state and I will have to reapply monitor settings to not get flickering with gsync
19:06:41 <jrgiacone> I did not know if anyone had experienced this, it's not a big deal, I just set a keybind to reapply the single monitor settings
19:08:10 <geekosaur> that would be an X11 issue
19:10:25 <liskin> jrgiacone: yeah, add that to the bottom
19:11:11 <liskin> Solid: why not? it just makes xmonad-contrib compile in parallel; if whatever depends on xmonad-contrib happens to be larger than xmonad-contrib and would benefit from parallel ghc, then sure, this won't apply to it, but that seems unlikely
19:11:36 <liskin> jrgiacone: are you using X.H.Rescreen or something like that which autotriggers xrandr?
19:13:41 × defjam quits (~eb0t@90.194.35.110) (Quit: WeeChat 2.3)
19:16:34 <jrgiacone> liskin, I am not I just bound a script to reapply my single or dual monitor settings
19:16:52 <jrgiacone> would X.H.Rescreen allow for that if im not hot plugging monitors
19:16:58 <jrgiacone> I switch to single to use gsync in games
19:18:13 <liskin> if you're not hotplugging then X.H.Rescreen wouldn't be as useful
19:18:35 <liskin> although in your case it seems like the external monitor turning off fires the same events like in an actual cable disconnect
19:18:56 <liskin> but you'd probably just get a different chaos of weird behaviours out of that
19:19:26 <liskin> what I do here is that when both outputs are active I disable DPMS so they never turn off
19:20:01 <jrgiacone> haha it's all good, I appreciate that feedback. It's just a minor annoyance I fixed with a few keybind scripts. Oh that's an easy fix too
19:20:30 <jrgiacone> liskin: could I add a similar -j16 for xmonad as well under the ghc-options
19:21:04 <liskin> it's not perfect—no power savings and the monitors get extra wear, but in my case it doesn't really matter as I only leave this when I go to the toilet or kitchen
19:21:19 <liskin> whenever I actually walk away I suspend the laptop
19:21:36 <liskin> jrgiacone: you can but you'll not gain much, xmonad compiles in seconds
19:22:06 <jrgiacone> cool cool, Yea ill see how it works on next update thanks
19:38:11 <jrgiacone> actually side question, anyone use xmobar with temp or weather options, after the number 80 on both it will not display a number and shows blank
19:39:02 <f-a> switch to Celsius ;P
19:39:29 <jrgiacone> I could haha, cpu will hit above 80 though in rendering lol
19:39:42 <f-a> hehe
19:40:27 <liskin> 80 sounds like the threshold between normal and high
19:40:50 <liskin> perhaps it's trying to display a different color or something
19:43:32 <jrgiacone> lmao thanks for the heads up, I forgot #
19:56:44 <jrgiacone> always something smalllll
20:06:52 × bla quits (~bla@89-67-84-220.dynamic.chello.pl) (Remote host closed the connection)
20:33:16 berserk joins (~berserk@108-195-12-248.lightspeed.miamfl.sbcglobal.net)
20:36:25 <berserk> Has someone seen this kind of output from `journalctl`?
20:36:30 <berserk> `XMonad is recompiling and replacing itself with another XMonad process because the current process is called "ah-xmonad" but the compiled configuration should be called "xmonad-x86_64-linux"`
20:36:59 <berserk> `ah-xmonad` is a custom build of xmonad I've got locally. I'm using a nix flake to build it.
20:37:47 <berserk> `ps aux | grep xmonad` reveals that `ah-xmonad` is running
20:39:04 <berserk> Here are the relevant log lines
20:39:05 <geekosaur> xmonad normally comes in two "flavors": "xmonad" is the outer one which does setup and if necessary rebuilds the inner one, "xmonad-x86_64-linux" (or substitute arch and os as needed) the inner one that is your actual config
20:39:54 <geekosaur> if the inner one doesn't have the right name, it assumes it was invoked as the outer vone and outputs that message
20:42:17 <berserk> Got it. So it's to be expected then. Is there anything from the rest of these relevant logs that strikes you as an actual error?
20:42:20 <berserk> ```
20:42:23 <berserk> Sep 04 16:16:00 nixos xsession[5764]: XMonad is recompiling and replacing itself with another XMonad process because the current process is called "ah-xmonad" but the compiled configuration should be called "xmonad-x86_64-linux"
20:42:24 <berserk> Sep 04 16:16:00 nixos xsession[5764]: XMonad will use ghc to recompile, because neither "/home/ah/.config/xmonad/build" nor "/home/ah/.config/xmonad/stack.yaml" exists.
20:42:24 <berserk> Sep 04 16:16:00 nixos xsession[5764]: XMonad skipping recompile because it is not forced (e.g. via --recompile), and neither xmonad.hs nor any *.hs / *.lhs / *.hsc files in lib/ have been changed.
20:42:25 <berserk> Sep 04 16:16:00 nixos xsession[5764]: /home/ah/.cache/xmonad/xmonad-x86_64-linux: executeFile: does not exist (No such file or directory)
20:42:27 <berserk> ```
20:43:08 <berserk> Thanks for the response btw :)
20:46:37 <geekosaur> the last one is an "actual error" but because of the way you're doing things it's okay, ah-xmonad should go on and use the config you built it with instead of defaulting to the wired-in config
20:46:58 <geekosaur> it just means you have a pointless attempt to rebuild going on
21:18:29 defjam joins (~eb0t@90.194.35.110)
21:33:58 × geekosaur quits (~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
21:34:13 geekosaur joins (~geekosaur@xmonad/geekosaur)
21:41:53 × berserk quits (~berserk@108-195-12-248.lightspeed.miamfl.sbcglobal.net) (Quit: Client closed)
21:48:12 kr1x joins (~kriket@170.249.0.122)
21:53:27 × Forkk quits (~forkk@li926-228.members.linode.com) (Ping timeout: 240 seconds)
22:01:48 Forkk joins (~forkk@li926-228.members.linode.com)
22:07:20 × jrgiacone quits (~jrgiacone@47.153.194.92) (Quit: Lost terminal)
22:13:38 × seschwar quits (~seschwar@user/seschwar) (Quit: :wq)
22:26:15 × geekosaur quits (~geekosaur@xmonad/geekosaur) (Killed (NickServ (GHOST command used by allbery_b)))
22:26:15 allbery_b joins (~geekosaur@xmonad/geekosaur)
22:26:18 allbery_b is now known as geekosaur
22:43:03 a6a45081-2b83 joins (~aditya@2601:249:4300:1296:88ec:cc73:84d4:1507)
23:23:10 × thunderrd quits (~thunderrd@183.182.111.87) (Ping timeout: 240 seconds)
23:40:43 benin0369323 joins (~benin@183.82.207.253)

All times are in UTC on 2021-09-04.