IRCBrowse

2023/01/07

2023-01-07 00:11:16 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Quit: Lost terminal)
2023-01-07 00:24:36 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-01-07 00:30:03 +0100mncheck(~mncheck@193.224.205.254) (Ping timeout: 256 seconds)
2023-01-07 00:35:12 +0100 <geekosaur> (so of course Ubuntu sends me a kernel update after I've rebooted…)
2023-01-07 00:53:51 +0100jab(~jabuxas@user/jabuxas) (Ping timeout: 256 seconds)
2023-01-07 02:28:00 +0100jab(~jabuxas@user/jabuxas)
2023-01-07 03:36:03 +0100tremon(~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl) (Quit: getting boxed in)
2023-01-07 04:02:55 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 260 seconds)
2023-01-07 04:04:54 +0100banc(banc@gateway/vpn/protonvpn/banc) (Ping timeout: 260 seconds)
2023-01-07 04:10:38 +0100td_(~td@83.135.9.2) (Ping timeout: 272 seconds)
2023-01-07 04:12:00 +0100td_(~td@83.135.9.51)
2023-01-07 04:26:06 +0100banc(banc@gateway/vpn/protonvpn/banc)
2023-01-07 04:31:16 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 04:36:23 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 260 seconds)
2023-01-07 04:48:14 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 04:52:30 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 260 seconds)
2023-01-07 05:20:38 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 05:25:23 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 260 seconds)
2023-01-07 05:38:48 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 05:43:23 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 264 seconds)
2023-01-07 05:56:01 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 06:00:51 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 260 seconds)
2023-01-07 06:12:03 +0100 <vrs> is there a way to reset xmonad state? I have a bunch of old workspaces not present in my config anymore but gridselect still shows them
2023-01-07 06:31:13 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 06:36:34 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 252 seconds)
2023-01-07 06:49:16 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 06:59:13 +0100 <vrs> hm. dunamicworkspaceorder doesn't really handle dynamically created workspaces well
2023-01-07 07:06:04 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 268 seconds)
2023-01-07 07:30:35 +0100jab(~jabuxas@user/jabuxas) (Ping timeout: 260 seconds)
2023-01-07 07:32:13 +0100jab(~jabuxas@user/jabuxas)
2023-01-07 07:43:34 +0100abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net)
2023-01-07 08:43:40 +0100hrberg(~quassel@171.79-160-161.customer.lyse.net) (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
2023-01-07 08:45:28 +0100hrberg(~quassel@171.79-160-161.customer.lyse.net)
2023-01-07 09:34:00 +0100 <vrs> why do the docs for X.C.Prime seem to inline the whole prelude and then some? https://hackage.haskell.org/package/xmonad-contrib-0.17.1/docs/XMonad-Config-Prime.html
2023-01-07 09:47:11 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 260 seconds)
2023-01-07 09:58:41 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 10:00:08 +0100BrynDiscord[m](~brynmmatr@2001:470:69fc:105::2:d43d) (Quit: You have been kicked for being idle)
2023-01-07 10:02:02 +0100Drishal[m](~drishalma@2001:470:69fc:105::a36)
2023-01-07 10:03:05 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 255 seconds)
2023-01-07 10:03:18 +0100 <Drishal[m]> > <@gilganix:matrix.org> What is the current status of wayland interest for xmonad?
2023-01-07 10:03:18 +0100 <Drishal[m]> > I am aware of waymonad and how the project was abandoned a couple of years ago by the maintainer, but afaik no other project has been created in the attempt to create a wayland alt to xmonad (please tell me I am wrong)
2023-01-07 10:03:18 +0100 <Drishal[m]> even I am pretty interested to see where does xmonad go with wayland....because seems like xorg is slowly dying/in maintenance mode apparently
2023-01-07 10:03:20 +0100 <lambdabot> <hint>:1:12: error: parse error on input ‘of’
2023-01-07 10:03:21 +0100 <lambdabot> <hint>:1:1: error: parse error on input ‘<@’
2023-01-07 10:11:05 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 10:51:09 +0100 <kora9> Hi, I'm using scratchpads to show/hide windows and I was wondering how I'd auto-hide a scratchpad to make sure just one scratchpad is visibe at a time *per workspace*.
2023-01-07 10:51:29 +0100 <kora9> I.e. I'd like to be able to call up multiple scratchpads on different workspaces, but not multiple scratchpads on the same workspace
2023-01-07 10:51:43 +0100 <kora9> This is the code that I use: https://sharetext.me/jwelzxfz5m
2023-01-07 10:57:16 +0100 <ChaoticMist[m]> <Drishal[m]> "> <@gilganix:matrix.org> What is..." <- I think that has been rather noticeable in the past 5 years
2023-01-07 10:57:22 +0100 <ChaoticMist[m]> s/in/for/
2023-01-07 11:03:23 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 248 seconds)
2023-01-07 11:11:11 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 12:10:22 +0100 <kora9> Drishal[m]: I read a comment on github somewhere that said that it'd be nearly impossible to implement xmonad in Wayland because Wayland doesn't expose the same functionality as Xorg. Wayland appears to be optimized for "Desktop Environments" (I'm not an expert on this, so feel free to correct me)
2023-01-07 12:10:27 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 260 seconds)
2023-01-07 12:19:02 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 12:45:15 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 248 seconds)
2023-01-07 12:53:29 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 13:05:16 +0100 <Solid> kora9: you're probably looking for nsHideOnFocusLoss ( https://hackage.haskell.org/package/xmonad-contrib-0.17.1/docs/XMonad-Util-NamedScratchpad.html#v:… )
2023-01-07 13:06:31 +0100 <kora9> Solid: Cool, thanks!
2023-01-07 13:11:07 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 260 seconds)
2023-01-07 13:21:43 +0100tremon(~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl)
2023-01-07 13:25:02 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 14:53:05 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 246 seconds)
2023-01-07 15:22:04 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 15:27:15 +0100 <geekosaur> kora9, but that's not true. it exposes it differently (xmonad _per se_ can't even be ported to xcb) but the basic functionality is pretty much the same despite API changes
2023-01-07 15:27:30 +0100 <geekosaur> and there's already a (somewhat buggy) waymonad
2023-01-07 15:27:56 +0100 <geekosaur> also things like sway which would also be impossible if that comment were true
2023-01-07 15:30:41 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 255 seconds)
2023-01-07 15:31:27 +0100 <geekosaur> what is true is that you won't be able to pick up an xmonad config and use it under waymonad, but that's because xmonad is a thin wrapper over xlib
2023-01-07 15:36:28 +0100 <geekosaur> what is also true, and may be the only sense in which that comment is true, is that a window manager is expected to provide the window server / compositor as well. but there's already wlroots for that, and there are multiple window managers that use it although sway is the main one
2023-01-07 15:36:54 +0100 <geekosaur> (I did see a note that KDE was considering switching to it instead of maintaining their own compositor, but I don't know how true it is)
2023-01-07 15:42:27 +0100zawaken(~zawaken@user/zawaken) (Quit: ZNC - https://znc.in)
2023-01-07 15:43:14 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 15:44:21 +0100zawaken(~zawaken@user/zawaken)
2023-01-07 15:47:53 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 252 seconds)
2023-01-07 15:59:48 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 16:00:19 +0100lokesh1197(~Thunderbi@14.139.128.52)
2023-01-07 16:04:18 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 252 seconds)
2023-01-07 16:08:07 +0100tremon(~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl) (Ping timeout: 268 seconds)
2023-01-07 16:10:29 +0100thyriaen(~thyriaen@2a01:aea0:dd4:4bae:2f5b:a119:9b18:3b52)
2023-01-07 16:10:47 +0100lokesh1197(~Thunderbi@14.139.128.52) (Ping timeout: 246 seconds)
2023-01-07 16:12:06 +0100thyriaen(~thyriaen@2a01:aea0:dd4:4bae:2f5b:a119:9b18:3b52) (Client Quit)
2023-01-07 16:16:02 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 16:20:39 +0100tremon(~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl)
2023-01-07 16:20:40 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 252 seconds)
2023-01-07 16:33:11 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 16:34:03 +0100lokesh1197(~Thunderbi@14.139.128.52)
2023-01-07 16:36:22 +0100mc47(~mc47@xmonad/TheMC47)
2023-01-07 16:38:08 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 246 seconds)
2023-01-07 16:39:25 +0100xmonadtrack(~xmonadtra@xmonad/geekosaur) (Remote host closed the connection)
2023-01-07 16:40:17 +0100geekosaur(~geekosaur@xmonad/geekosaur) (Quit: Leaving)
2023-01-07 16:42:11 +0100geekosaur(~geekosaur@xmonad/geekosaur)
2023-01-07 16:44:43 +0100xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com)
2023-01-07 16:44:44 +0100xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host)
2023-01-07 16:44:44 +0100xmonadtrack(~xmonadtra@xmonad/geekosaur)
2023-01-07 16:47:51 +0100 <kora9> geekosaur: Yeah, I read the part about wayland not working for xmonad on the waymonad github somewhere I believe. The last commit to the Waymonad project was 3 years ago
2023-01-07 16:48:37 +0100 <kora9> I'm having some issues figuring out how to implement nsHideOnFocusLoss in my config: https://sharetext.me/wnuko3rchj <- does not work :)
2023-01-07 16:49:32 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 16:50:06 +0100 <geekosaur> uh, why did you use a comma there? it should be >> or <>
2023-01-07 16:50:18 +0100 <geekosaur> probably >> since you used that for the other one
2023-01-07 16:51:48 +0100 <kora9> geekosaur, I tried using a $ first but that didn't work. Let me try >>
2023-01-07 16:52:45 +0100 <geekosaur> $ only works in the layoutHook, other hooks generally want <> to combine things but >> or *> will work in most of them (not manageHook though)
2023-01-07 16:54:11 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 260 seconds)
2023-01-07 17:05:12 +0100 <kora9> geekosaur, cool, thanks :)
2023-01-07 17:07:41 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 17:11:44 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 246 seconds)
2023-01-07 17:24:36 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 17:26:49 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Max SendQ exceeded)
2023-01-07 17:27:17 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 17:54:07 +0100kora9(~kora@user/Kora9) (Quit: WeeChat 3.5)
2023-01-07 18:39:31 +0100MrElendigpantsu
2023-01-07 18:41:59 +0100gdd(~gdd@2001:470:1f13:187:31f4:d139:4ea3:c0fd) (Ping timeout: 246 seconds)
2023-01-07 18:42:54 +0100gdd(~gdd@2001:470:1f13:187:e8a5:fbff:fe29:42f5)
2023-01-07 18:45:05 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2023-01-07 19:02:31 +0100dmn_(~dmn_@ip-078-094-075-193.um19.pools.vodafone-ip.de)
2023-01-07 19:05:23 +0100 <dmn_> I had a working (very simple) xmoand configuration for a while, recently upgraded (archlinux - a lot of packages) and it seems my config is broken. I got 2 Monitors, each on it's own GPU. X11/Xmonad is starting fine (I think). One Screen gives me the 'usual' - e.g. I can use xmonad. As soon as I move the mouse to the second physical screen I get
2023-01-07 19:05:23 +0100 <dmn_> the 'X' pointer shown (not the mouse pointer) and no xmonad command works. My guess is the X11 config got broken - but I'm not really sure. It feels a bit like 'on the second screen xmonad' is not runnig, but X11 is. I'm unsure how to continue or what I should check. Anyone got a hint?
2023-01-07 19:06:34 +0100 <dmn_> Also general question, if using nvidia, should I enable 'Xinerama' or not for dual screen usage?
2023-01-07 19:09:42 +0100 <geekosaur> sounds to me like the monitors are currrently exposed as separate X11 `Screen`s. so you probably want Xinerama turned on since the same low level stuff is used with XRandR
2023-01-07 19:10:43 +0100 <geekosaur> (if this is the case, you would nmeed to run a separate xmonad on `DISPLAY=:0.1`)
2023-01-07 19:12:47 +0100 <geekosaur> also, it won't behave at all like you would expect, because it is a separate DISPLAY so you can't e.g. move windows between them
2023-01-07 19:16:35 +0100 <geekosaur> if you want to test this, you can go to a shell and try `xdpyinfo -display :0.1`, if it doesn't throw an error about being unable to open the display then you're in multi-Screen mode
2023-01-07 19:16:43 +0100 <geekosaur> sometimes called "Zaphod mode"
2023-01-07 19:57:35 +0100mc47(~mc47@xmonad/TheMC47) (Quit: Leaving)
2023-01-07 19:58:15 +0100mc47(~mc47@xmonad/TheMC47)
2023-01-07 20:08:27 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 248 seconds)
2023-01-07 20:15:06 +0100 <dmn_> geekosaur no error :) so I guess I have to figure out how to turn on xinerama :)
2023-01-07 20:20:55 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 20:21:26 +0100dmn_(~dmn_@ip-078-094-075-193.um19.pools.vodafone-ip.de) (Quit: Client closed)
2023-01-07 20:25:58 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 252 seconds)
2023-01-07 20:26:39 +0100lokesh1197(~Thunderbi@14.139.128.52) (Ping timeout: 260 seconds)
2023-01-07 20:28:59 +0100dmn_(~dmn_@ip-078-094-075-193.um19.pools.vodafone-ip.de)
2023-01-07 20:30:26 +0100 <dmn_> geekosaur thank you. Got both screens working now. - Is there a way to check the Hz somehow? I think nvidia might be using only 1 cable for each screen, but must use two for each; Easiest to check would be checking the current resolution/hz combination per screen; sadly the on screen menu of the monitor doesn't offer that...
2023-01-07 20:32:07 +0100 <geekosaur> `xrandr` shows the available and selected rates
2023-01-07 20:33:42 +0100 <dmn_> I might be wrong, but I think enabling xinerma disabled xrandr - because I get now randr extension missing - googeling :)
2023-01-07 20:34:31 +0100 <geekosaur> I don't know enough about nvidia to help there, there might be a switch to get the low level xinerama stuff (all monitors sharing the root window) plus xrandr
2023-01-07 20:36:03 +0100 <dmn_> will try to figure out - I can get the resolution via xdpyinfo, but it feels '30Hz' ;) thank you again!
2023-01-07 20:38:10 +0100dmn_(~dmn_@ip-078-094-075-193.um19.pools.vodafone-ip.de) (Quit: Client closed)
2023-01-07 20:38:19 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 20:42:43 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 256 seconds)
2023-01-07 20:55:34 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 21:00:11 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 248 seconds)
2023-01-07 21:17:19 +0100 <HB[m]> You can't use xinerama with xrandr
2023-01-07 21:17:22 +0100 <HB[m]> One or the other.
2023-01-07 21:17:25 +0100 <HB[m]> s///
2023-01-07 21:17:47 +0100 <HB[m]> xrandr is often better than Xinerama.
2023-01-07 21:18:03 +0100 <geekosaur> the point is he can't find the nvidia knob to activate xrandr
2023-01-07 21:18:19 +0100 <geekosaur> he's offered ximerama and "zaphod mode"
2023-01-07 21:30:52 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 21:36:18 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 260 seconds)
2023-01-07 21:42:00 +0100 <HB[m]> Bind\ary driver or nouveau?
2023-01-07 21:42:03 +0100 <HB[m]> s/Bind\ary/Binary/
2023-01-07 21:43:27 +0100 <geekosaur> they left
2023-01-07 21:43:41 +0100 <geekosaur> IRC doesn't keep backscroll like matrix does
2023-01-07 21:44:22 +0100 <HB[m]> Matrix didn't how his parting/quitting on my end. Hmm
2023-01-07 21:48:20 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 21:52:59 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf) (Ping timeout: 264 seconds)
2023-01-07 22:06:48 +0100defjam(~defjam@2a02:c7e:2807:b900:85e2:4f2b:c50c:70cf)
2023-01-07 22:37:51 +0100mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)