IRCBrowse

2021/09/04

2021-09-04 00:07:45 +0200seschwar(~seschwar@user/seschwar) (Quit: :wq)
2021-09-04 00:49:14 +0200benin0369323(~benin@183.82.179.90)
2021-09-04 01:47:27 +0200 <yuu[m]> i'm still interested in a way to bring the mouse cursor to the interior of the window when resizing a floating window as to avoid issues. anyone know how to?
2021-09-04 01:48:21 +0200 <yuu[m]> on i3 this was default, improves usability by 100%
2021-09-04 01:49:35 +0200 <geekosaur> I think you'd have to reimplement resizing
2021-09-04 01:50:35 +0200nomadxx3(~lanomadx@208.91.65.11) (Ping timeout: 244 seconds)
2021-09-04 01:50:53 +0200nomadxx3(~lanomadx@208.91.64.181)
2021-09-04 01:58:02 +0200 <yuu[m]> seems like that, indeed 🥲
2021-09-04 02:00:03 +0200nomadxx3(~lanomadx@208.91.64.181) (*.net *.split)
2021-09-04 02:00:03 +0200benin0369323(~benin@183.82.179.90) (*.net *.split)
2021-09-04 02:00:03 +0200td_(~td@muedsl-82-207-238-018.citykom.de) (*.net *.split)
2021-09-04 02:00:03 +0200kr1x(~kriket@170.249.0.122) (*.net *.split)
2021-09-04 02:00:03 +0200jsoo(~znc@irc.refl.club) (*.net *.split)
2021-09-04 02:00:19 +0200nomadxx3(~lanomadx@208.91.64.181)
2021-09-04 02:00:45 +0200kr1x(~kriket@170.249.0.122)
2021-09-04 02:02:03 +0200jsoo(~znc@irc.refl.club)
2021-09-04 02:05:16 +0200td_(~td@muedsl-82-207-238-018.citykom.de)
2021-09-04 02:06:00 +0200kr1x(~kriket@170.249.0.122) (Quit: .)
2021-09-04 03:23:21 +0200sagax(~sagax_nb@user/sagax)
2021-09-04 03:36:57 +0200nomadxxxx3(~lanomadx@69.167.42.182)
2021-09-04 03:38:10 +0200nomadxx3(~lanomadx@208.91.64.181) (Ping timeout: 240 seconds)
2021-09-04 04:03:10 +0200banc(banc@gateway/vpn/airvpn/banc) (Ping timeout: 240 seconds)
2021-09-04 04:03:27 +0200pl(sid98063@id-98063.helmsley.irccloud.com) (Ping timeout: 240 seconds)
2021-09-04 04:06:23 +0200pl(sid98063@id-98063.helmsley.irccloud.com)
2021-09-04 04:20:32 +0200td_(~td@muedsl-82-207-238-018.citykom.de) (Ping timeout: 245 seconds)
2021-09-04 04:22:38 +0200td_(~td@94.134.91.73)
2021-09-04 04:24:14 +0200banc(banc@gateway/vpn/airvpn/banc)
2021-09-04 04:45:20 +0200eyenx(~m-5paiux@eyenx.ch) (Remote host closed the connection)
2021-09-04 04:46:09 +0200eyenx(~m-5paiux@eyenx.ch)
2021-09-04 06:04:37 +0200Nahra(~user@static.161.95.99.88.clients.your-server.de) (Ping timeout: 252 seconds)
2021-09-04 09:03:19 +0200wonko(~wjc@62.115.229.50)
2021-09-04 09:11:53 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2021-09-04 09:17:29 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2021-09-04 09:29:48 +0200seschwar(~seschwar@user/seschwar)
2021-09-04 10:17:44 +0200allbery_b(~geekosaur@xmonad/geekosaur)
2021-09-04 10:17:44 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Killed (NickServ (GHOST command used by allbery_b)))
2021-09-04 10:17:47 +0200allbery_bgeekosaur
2021-09-04 10:29:57 +0200AndrewAhkilKumar
2021-09-04 10:30:26 +0200AhkilKumarAndrew
2021-09-04 11:10:38 +0200Nahra(~user@static.161.95.99.88.clients.your-server.de)
2021-09-04 12:01:20 +0200mc47(~mc47@xmonad/TheMC47)
2021-09-04 12:04:35 +0200frosch03(~user@2a02:8070:7ab:1b00:1f4a:4f79:a4cd:c73)
2021-09-04 12:04:35 +0200frosch03(~user@2a02:8070:7ab:1b00:1f4a:4f79:a4cd:c73) (Client Quit)
2021-09-04 14:43:18 +0200wonko(~wjc@62.115.229.50) (Ping timeout: 256 seconds)
2021-09-04 15:16:43 +0200 <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.
2021-09-04 15:17:40 +0200 <f-a> I guess because there are 9 numbered keys
2021-09-04 15:17:42 +0200 <Solid> it was... not? :D
2021-09-04 15:17:53 +0200 <Solid> you can have as many workspaces as you like
2021-09-04 15:18:53 +0200Solidhas 25 :]
2021-09-04 15:19:57 +0200 <yuu[m]> Solid: i mean on the source code https://github.com/xmonad/xmonad/blob/f89df98f4022b5142760b86a2ad85b4e90e583b3/src/XMonad/Config.h…
2021-09-04 15:20:10 +0200 <yuu[m]> 1 .. 9
2021-09-04 15:20:42 +0200 <Solid> this is the default config, where it was decided that 9 workspaces seem like a decent default to have
2021-09-04 15:21:40 +0200 <Solid> You can see in line 261 that these are just assigned to XConfig's `workspaces` field
2021-09-04 15:22:07 +0200 <Solid> there's nothing stopping you from doing `map show [1 .. 100 :: Int]` :)
2021-09-04 15:26:25 +0200 <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
2021-09-04 15:27:02 +0200 <f-a> tho there are *ten* numbered keys, of course
2021-09-04 15:36:08 +0200 <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
2021-09-04 15:37:28 +0200 <f-a> yuu[m]: out of curiosity, how will you bind them? ⌂+n for the first 10 and then ⌂+⇧+n for other ten?
2021-09-04 15:37:43 +0200 <f-a> or do you just iterate «next workspace» and «previous workspace»?
2021-09-04 15:38:50 +0200 <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
2021-09-04 15:39:19 +0200 <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 )
2021-09-04 15:39:41 +0200 <Solid> for anything else I use X.P.Workspace
2021-09-04 15:42:56 +0200 <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`
2021-09-04 15:43:58 +0200 <yuu[m]> Solid: thank you!
2021-09-04 15:44:19 +0200mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2021-09-04 15:46:45 +0200f-a(f2a@f2a.jujube.ircnow.org) (Remote host closed the connection)
2021-09-04 15:48:39 +0200 <Solid> oh then you just need the keybinding part
2021-09-04 15:53:03 +0200 <Solid> yuu[m]: something like http://ix.io/3xUW should be a minimal working example
2021-09-04 15:58:32 +0200 <geekosaur> https://github.com/geekosaur/xmonad.hs/blob/pyanfar/xmonad.hs#L220-L225
2021-09-04 16:00:06 +0200 <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)
2021-09-04 16:01:09 +0200 <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>
2021-09-04 16:04:02 +0200f2a(f2a@f2a.jujube.ircnow.org)
2021-09-04 16:05:16 +0200f2af-a
2021-09-04 16:17:52 +0200bla(~bla@89-67-84-220.dynamic.chello.pl) (Ping timeout: 252 seconds)
2021-09-04 16:18:50 +0200 <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.
2021-09-04 17:39:59 +0200 <yuu[m]> Solid: geekosaur thank you!
2021-09-04 17:41:01 +0200 <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/c147ff51e8dfa36fa18fa82490d4d33e2c3e…)
2021-09-04 17:47:11 +0200 <davve> its not about the amount of workspaces, its how you use them!
2021-09-04 17:47:45 +0200 <geekosaur> yuu[m], what error do you get?
2021-09-04 17:49:59 +0200 <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
2021-09-04 17:50:00 +0200 <geekosaur> it shouldn't be an operator but it might need parentheses
2021-09-04 18:10:19 +0200benin0369323(~benin@183.82.179.90)
2021-09-04 18:21:23 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2021-09-04 18:36:21 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2021-09-04 18:47:24 +0200qbt(~edun@user/edun)
2021-09-04 18:47:25 +0200defjam(~eb0t@90.194.35.110)
2021-09-04 18:49:09 +0200rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com)
2021-09-04 18:54:54 +0200defjam(~eb0t@90.194.35.110) (Quit: WeeChat 2.3)
2021-09-04 18:55:05 +0200defjam(~eb0t@90.194.35.110)
2021-09-04 19:01:45 +0200benin03693239(~benin@106.198.95.161)
2021-09-04 19:03:22 +0200benin0369323(~benin@183.82.179.90) (Ping timeout: 240 seconds)
2021-09-04 19:03:23 +0200benin03693239benin0369323
2021-09-04 19:09:46 +0200defjam(~eb0t@90.194.35.110) (Quit: WeeChat 2.3)
2021-09-04 19:10:47 +0200defjam(~eb0t@90.194.35.110)
2021-09-04 19:21:29 +0200defjamrundown
2021-09-04 19:21:52 +0200benin03693238(~benin@183.82.207.253)
2021-09-04 19:23:35 +0200rundowneblip
2021-09-04 19:23:40 +0200benin0369323(~benin@106.198.95.161) (Ping timeout: 240 seconds)
2021-09-04 19:23:40 +0200benin03693238benin0369323
2021-09-04 19:24:42 +0200eblipeb0t
2021-09-04 19:26:17 +0200eb0tdefjam
2021-09-04 19:26:25 +0200defjam(~eb0t@90.194.35.110) (Quit: WeeChat 2.3)
2021-09-04 19:27:13 +0200defjam(~eb0t@90.194.35.110)
2021-09-04 19:45:43 +0200defjam(~eb0t@90.194.35.110) (Quit: WeeChat 2.3)
2021-09-04 19:46:05 +0200defjam(~eb0t@90.194.35.110)
2021-09-04 19:58:17 +0200defjam(~eb0t@90.194.35.110) (Quit: WeeChat 2.3)
2021-09-04 20:06:07 +0200benin0369323(~benin@183.82.207.253) (Ping timeout: 252 seconds)
2021-09-04 20:10:37 +0200defjam(~eb0t@90.194.35.110)
2021-09-04 20:18:17 +0200jrgiacone(~jrgiacone@47.153.194.92)
2021-09-04 20:18:20 +0200 <jrgiacone> good morning
2021-09-04 20:18:36 +0200 <jrgiacone> does anyone now how to allow stack to use more cores when compiling updates?
2021-09-04 20:18:50 +0200 <jrgiacone> ive got 16 threads and it only uses 1
2021-09-04 20:19:16 +0200 <jrgiacone> know*
2021-09-04 20:19:30 +0200 <f-a> I know it w/ cabal (-j)
2021-09-04 20:19:44 +0200 <f-a> are you sure you meant to ask this here (#xmonad), jrgiacone ?
2021-09-04 20:20:55 +0200 <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
2021-09-04 20:22:52 +0200 <f-a> ah sorry, my bad
2021-09-04 20:23:34 +0200 <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
2021-09-04 20:24:46 +0200defjam(~eb0t@90.194.35.110) (Quit: WeeChat 2.3)
2021-09-04 20:26:26 +0200defjam(~eb0t@90.194.35.110)
2021-09-04 20:52:33 +0200 <Solid> jrgiacone: stack should already build packages in parallel (and use multiple cores for that)
2021-09-04 20:53:36 +0200 <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)
2021-09-04 20:53:52 +0200bla(~bla@89-67-84-220.dynamic.chello.pl)
2021-09-04 20:54:18 +0200 <Solid> eh, probably `--ghc-options -j16` to directly pass it to ghc
2021-09-04 20:55:53 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2021-09-04 20:57:42 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2021-09-04 20:58:33 +0200 <jrgiacone> hmm solid, my stack only uses one thread when I compile and watch htop
2021-09-04 20:59:03 +0200 <jrgiacone> but ill try either so like stack build --ghc-options -j16?
2021-09-04 20:59:09 +0200 <geekosaur> packages, not modules
2021-09-04 20:59:39 +0200 <liskin> jrgiacone: you can also do this: https://github.com/xmonad/xmonad-contrib/blob/master/stack-master.yaml#L25
2021-09-04 20:59:44 +0200 <geekosaur> it would build xmonad and xmonad-contrib in parallel, except xmonad-contrib depends on xmonad so it can't
2021-09-04 21:00:20 +0200 <jrgiacone> ahh, I'll check that out liskin, yea cause contrib only uses one thread when compiling, so i wanted to speed it up
2021-09-04 21:00:38 +0200 <jrgiacone> ah sick
2021-09-04 21:00:54 +0200 <jrgiacone> Ill try it on the next update to contrib thanks!
2021-09-04 21:01:33 +0200 <jrgiacone> liskin, I can add that at the bottom of my stack.yaml?
2021-09-04 21:03:28 +0200 <Solid> liskin: that doesn't work when building something that depends on contrib right?
2021-09-04 21:06:14 +0200 <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
2021-09-04 21:06:41 +0200 <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
2021-09-04 21:08:10 +0200 <geekosaur> that would be an X11 issue
2021-09-04 21:10:25 +0200 <liskin> jrgiacone: yeah, add that to the bottom
2021-09-04 21:11:11 +0200 <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
2021-09-04 21:11:36 +0200 <liskin> jrgiacone: are you using X.H.Rescreen or something like that which autotriggers xrandr?
2021-09-04 21:13:41 +0200defjam(~eb0t@90.194.35.110) (Quit: WeeChat 2.3)
2021-09-04 21:16:34 +0200 <jrgiacone> liskin, I am not I just bound a script to reapply my single or dual monitor settings
2021-09-04 21:16:52 +0200 <jrgiacone> would X.H.Rescreen allow for that if im not hot plugging monitors
2021-09-04 21:16:58 +0200 <jrgiacone> I switch to single to use gsync in games
2021-09-04 21:18:13 +0200 <liskin> if you're not hotplugging then X.H.Rescreen wouldn't be as useful
2021-09-04 21:18:35 +0200 <liskin> although in your case it seems like the external monitor turning off fires the same events like in an actual cable disconnect
2021-09-04 21:18:56 +0200 <liskin> but you'd probably just get a different chaos of weird behaviours out of that
2021-09-04 21:19:26 +0200 <liskin> what I do here is that when both outputs are active I disable DPMS so they never turn off
2021-09-04 21:20:01 +0200 <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
2021-09-04 21:20:30 +0200 <jrgiacone> liskin: could I add a similar -j16 for xmonad as well under the ghc-options
2021-09-04 21:21:04 +0200 <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
2021-09-04 21:21:19 +0200 <liskin> whenever I actually walk away I suspend the laptop
2021-09-04 21:21:36 +0200 <liskin> jrgiacone: you can but you'll not gain much, xmonad compiles in seconds
2021-09-04 21:22:06 +0200 <jrgiacone> cool cool, Yea ill see how it works on next update thanks
2021-09-04 21:38:11 +0200 <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
2021-09-04 21:39:02 +0200 <f-a> switch to Celsius ;P
2021-09-04 21:39:29 +0200 <jrgiacone> I could haha, cpu will hit above 80 though in rendering lol
2021-09-04 21:39:42 +0200 <f-a> hehe
2021-09-04 21:40:27 +0200 <liskin> 80 sounds like the threshold between normal and high
2021-09-04 21:40:50 +0200 <liskin> perhaps it's trying to display a different color or something
2021-09-04 21:43:32 +0200 <jrgiacone> lmao thanks for the heads up, I forgot #
2021-09-04 21:56:44 +0200 <jrgiacone> always something smalllll
2021-09-04 22:06:52 +0200bla(~bla@89-67-84-220.dynamic.chello.pl) (Remote host closed the connection)
2021-09-04 22:33:16 +0200berserk(~berserk@108-195-12-248.lightspeed.miamfl.sbcglobal.net)
2021-09-04 22:36:25 +0200 <berserk> Has someone seen this kind of output from `journalctl`?
2021-09-04 22:36:30 +0200 <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"`
2021-09-04 22:36:59 +0200 <berserk> `ah-xmonad` is a custom build of xmonad I've got locally. I'm using a nix flake to build it.
2021-09-04 22:37:47 +0200 <berserk> `ps aux | grep xmonad` reveals that `ah-xmonad` is running
2021-09-04 22:39:04 +0200 <berserk> Here are the relevant log lines
2021-09-04 22:39:05 +0200 <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
2021-09-04 22:39:54 +0200 <geekosaur> if the inner one doesn't have the right name, it assumes it was invoked as the outer vone and outputs that message
2021-09-04 22:42:17 +0200 <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?
2021-09-04 22:42:20 +0200 <berserk> ```
2021-09-04 22:42:23 +0200 <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"
2021-09-04 22:42:24 +0200 <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.
2021-09-04 22:42:24 +0200 <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.
2021-09-04 22:42:25 +0200 <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)
2021-09-04 22:42:27 +0200 <berserk> ```
2021-09-04 22:43:08 +0200 <berserk> Thanks for the response btw :)
2021-09-04 22:46:37 +0200 <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
2021-09-04 22:46:58 +0200 <geekosaur> it just means you have a pointless attempt to rebuild going on
2021-09-04 23:18:29 +0200defjam(~eb0t@90.194.35.110)
2021-09-04 23:33:58 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2021-09-04 23:34:13 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2021-09-04 23:41:53 +0200berserk(~berserk@108-195-12-248.lightspeed.miamfl.sbcglobal.net) (Quit: Client closed)
2021-09-04 23:48:12 +0200kr1x(~kriket@170.249.0.122)
2021-09-04 23:53:27 +0200Forkk(~forkk@li926-228.members.linode.com) (Ping timeout: 240 seconds)