2022/09/10

2022-09-10 00:01:48 +0000diep(~diep@2a01:cb11:2d7:4a00:a13f:e40c:c4e8:736c)
2022-09-10 00:06:44 +0000diep(~diep@2a01:cb11:2d7:4a00:a13f:e40c:c4e8:736c) (Remote host closed the connection)
2022-09-10 00:07:28 +0000diep(~diep@2a01:cb11:2d7:4a00:12c3:4372:12dc:27ce)
2022-09-10 00:19:25 +0000diep(~diep@2a01:cb11:2d7:4a00:12c3:4372:12dc:27ce) (Remote host closed the connection)
2022-09-10 02:02:43 +0000banc(banc@gateway/vpn/airvpn/banc) (Ping timeout: 248 seconds)
2022-09-10 02:23:00 +0000banc(banc@gateway/vpn/airvpn/banc)
2022-09-10 02:36:19 +0000td_(~td@94.134.91.37) (Ping timeout: 248 seconds)
2022-09-10 02:38:12 +0000td_(~td@muedsl-82-207-238-006.citykom.de)
2022-09-10 03:39:22 +0000noex(~null@user/noex)
2022-09-10 03:40:21 +0000mvk(~mvk@2607:fea8:5ce3:8500::875a) (Ping timeout: 244 seconds)
2022-09-10 04:22:19 +0000justJingo(~justache@user/justache) (Quit: ZNC 1.8.2 - https://znc.in)
2022-09-10 04:22:38 +0000justache(~justache@user/justache)
2022-09-10 05:23:15 +0000jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 248 seconds)
2022-09-10 06:32:45 +0000chomwitt(~chomwitt@2a02:587:dc16:fe00:b62b:4d00:b365:1fd8)
2022-09-10 08:11:25 +0000 <Solid> liskin: sounds great :)
2022-09-10 08:19:20 +0000mc47(~mc47@xmonad/TheMC47)
2022-09-10 08:20:51 +0000mc47committed the sin of calling `windows` insde `logHook`, and wondering why my system broke
2022-09-10 08:21:59 +0000 <Solid> :]
2022-09-10 08:28:02 +0000 <xmonadtrack> New branch created: pull/421 (1 commit) https://github.com/xmonad/xmonad/pull/421
2022-09-10 08:28:02 +0000 <xmonadtrack> xmonad Tony Zorman https://github.com/xmonad/xmonad/pull/421 * v0.17.1-8-g3d8238b: Expose buildLaunch, sendRestart, and sendReplace (47 minutes ago, 3 files, 59+ 54-) https://github.com/xmonad/xmonad/commit/3d8238b35d0f
2022-09-10 08:46:14 +0000mc47(~mc47@xmonad/TheMC47) (Read error: Connection reset by peer)
2022-09-10 10:14:26 +0000logzet(~quassel@2001:9e8:e52d:1c00:dabb:c1ff:fed3:a1b9)
2022-09-10 10:25:15 +0000nomadxx3(~lanomadx@180-150-32-38.b49620.mel.static.aussiebb.net) (Quit: ZNC 1.8.2 - https://znc.in)
2022-09-10 10:27:31 +0000nomadxx3(~lanomadx@180-150-32-38.b49620.mel.static.aussiebb.net)
2022-09-10 11:29:27 +0000geekosaurwonders if that's worth documenting as part of `logHook`
2022-09-10 11:44:26 +0000alternateved(~user@staticline-31-183-146-203.toya.net.pl)
2022-09-10 11:52:43 +0000mc47(~mc47@xmonad/TheMC47)
2022-09-10 11:56:02 +0000 <mc47> maybe we should, I shot myself in the foot a couple of times trying to add this new functionality
2022-09-10 11:56:09 +0000 <mc47> sticky windows
2022-09-10 12:07:12 +0000 <geekosaur> hm, why logHook? afaik it should be in manageHook and handleEventHook
2022-09-10 12:15:19 +0000nomadxx3(~lanomadx@180-150-32-38.b49620.mel.static.aussiebb.net) (Quit: ZNC 1.8.2 - https://znc.in)
2022-09-10 12:16:27 +0000nomadxx3(~lanomadx@208.91.67.65)
2022-09-10 12:21:09 +0000 <mc47> I want to detect when visible workspaces change
2022-09-10 12:22:19 +0000 <geekosaur> hm. so you want to move the window dynamically instead of just using copyToAll?
2022-09-10 12:22:25 +0000 <mc47> yes
2022-09-10 12:22:44 +0000 <mc47> I mean I remember trying copyToAll and not liking it
2022-09-10 12:22:53 +0000 <mc47> totally forgot about it when I wanted to add this lol
2022-09-10 12:22:56 +0000 <mc47> might take another look
2022-09-10 12:27:15 +0000 <liskin> we could also extend XConf and use Control.Monad.Reader.local to prevent recursion in windows :-)
2022-09-10 12:34:13 +0000 <[Leary]> I have some changes I've been sitting on / testing for months now which also provide a fix for logHook. In particular, any changes it makes are handled in the same refresh.
2022-09-10 12:35:37 +0000 <[Leary]> The changes are reasonably small, not outwardly breaking, and essentially semantics preserving ... but they touch deep stuff. Like, redefining X.
2022-09-10 12:37:01 +0000 <[Leary]> So I'm not really sure if they'd go in. That said, I still plan to write up a motivating PR some time soon.
2022-09-10 12:39:22 +0000 <geekosaur> I don't thhink a lot of stuff depends on the exact structure of X; that's what the mtl classes are for
2022-09-10 12:43:55 +0000andi_(~andi@user/andi/x-3467420)
2022-09-10 12:49:19 +0000 <andi_> where there some breaking changes from 0.16. to 0.17?
2022-09-10 12:50:01 +0000alternateved(~user@staticline-31-183-146-203.toya.net.pl) (Remote host closed the connection)
2022-09-10 12:51:45 +0000 <geekosaur> we made some default* names go away as they;ve been deprecated for several versions. there were a few others; check the changelog
2022-09-10 12:51:54 +0000 <geekosaur> no major breaking changes to the core
2022-09-10 12:53:55 +0000logzet(~quassel@2001:9e8:e52d:1c00:dabb:c1ff:fed3:a1b9) (Ping timeout: 248 seconds)
2022-09-10 12:55:23 +0000 <geekosaur> https://github.com/xmonad/xmonad-contrib/blob/master/CHANGES.md#breaking-changes-2
2022-09-10 13:03:37 +0000 <andi_> see this is my xmonad.hs https://paste.xinu.at/kywzt/ but i cannot recompile, because of line 73 (myXPConfig = defaultXPConfig, variable not found in scope) and line 102 with the same problem but i don't see why this is a problem?
2022-09-10 13:10:03 +0000 <geekosaur> that's one of the removed names I mentioned. use `def` instead
2022-09-10 13:12:11 +0000lazyrat(~lazycat@user/lazycat) (Quit: ZNC - https://znc.in)
2022-09-10 13:13:06 +0000lazycat(~lazycat@user/lazycat)
2022-09-10 13:15:26 +0000 <andi_> but as they're depreciated i probably should get rid of them, wouldn't that be a better idea?
2022-09-10 13:17:07 +0000 <geekosaur> no? the only things deprecated are the old names, `def` is the new way to do it
2022-09-10 13:27:13 +0000 <andi_> alright, thank you very much geekosaur
2022-09-10 13:31:33 +0000 <Solid> andi_: you can also read through the breaking changes for contrib 0.17.0 here: https://github.com/xmonad/xmonad-contrib/blob/master/CHANGES.md#breaking-changes-2
2022-09-10 14:05:16 +0000 <geekosaur> I pointed to that already 🙂
2022-09-10 14:05:39 +0000 <Solid> oh
2022-09-10 14:05:41 +0000 <Solid> sorry about that
2022-09-10 14:15:16 +0000mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2022-09-10 14:16:37 +0000mc47(~mc47@xmonad/TheMC47)
2022-09-10 14:17:47 +0000 <mc47> geekosaur I remember why I CopyWindow didn't do it for me: it breaks with multiple monitors
2022-09-10 14:21:32 +0000 <geekosaur> breaks how? (aside from the fact that X11 won't let a window be more than one place at a time)
2022-09-10 14:26:26 +0000chomwitt(~chomwitt@2a02:587:dc16:fe00:b62b:4d00:b365:1fd8) (Ping timeout: 260 seconds)
2022-09-10 14:31:36 +0000 <xmonadtrack> xmonad-contrib Luca Leon Happel {Tony Zorman} * v0.17.1-11-gae652b40: X.L.BorderResize: Add borderResizeNear (26 hours ago, 2 files, 43+ 29-) https://github.com/xmonad/xmonad-contrib/commit/ae652b40f498
2022-09-10 14:31:37 +0000 <xmonadtrack> xmonad-contrib Tony Zorman {GitHub} * v0.17.1-12-gb0fc5549: Merge pull request #754 from Quoteme/master (79 seconds ago, 0 files, 0+ 0-) https://github.com/xmonad/xmonad-contrib/commit/b0fc55499d16
2022-09-10 14:41:07 +0000 <mc47> geekosaur it would move the window between screens, whereas I want it to stick on one screen
2022-09-10 14:41:20 +0000 <mc47> breaks as in breaks for my usecase
2022-09-10 14:51:00 +0000logzet(~quassel@2001:9e8:e52d:1c00:dabb:c1ff:fed3:a1b9)
2022-09-10 15:01:24 +0000mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2022-09-10 15:02:24 +0000mc47(~mc47@xmonad/TheMC47)
2022-09-10 15:06:15 +0000Natch(~natch@c-9e07225c.038-60-73746f7.bbcust.telenor.se) (Remote host closed the connection)
2022-09-10 15:28:48 +0000Natch(~natch@c-9e07225c.038-60-73746f7.bbcust.telenor.se)
2022-09-10 16:17:59 +0000jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-09-10 16:29:11 +0000thunderrd(~thunderrd@183.182.114.129)
2022-09-10 17:14:54 +0000chomwitt(~chomwitt@2a02:587:dc16:fe00:5010:70b4:e094:50b5)
2022-09-10 19:09:05 +0000mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2022-09-10 20:13:23 +0000steve_(~steve@ool-182c2b80.dyn.optonline.net) (Ping timeout: 244 seconds)
2022-09-10 21:00:53 +0000noex(~null@user/noex) (Quit: :q!)
2022-09-10 21:05:14 +0000chomwitt(~chomwitt@2a02:587:dc16:fe00:5010:70b4:e094:50b5) (Ping timeout: 268 seconds)
2022-09-10 21:09:11 +0000henninb(~henninb@97-116-154-134.mpls.qwest.net)
2022-09-10 21:24:32 +0000 <henninb> Hi, I am trying to fix a formatting issue with my bar dzen in xmonad. I posted the question on reddit which describes the problem 'https://www.reddit.com/r/xmonad/comments/x9so8z/dzen2_bar_spacing_issue/' please provide any suggestions on how I can troubleshoot this issue.
2022-09-10 21:32:22 +0000 <geekosaur> gentoo just upgraded their xmonad, but I don't think any of the changes in 0.17.1 could have caused that. or 0.17.0 for that matter
2022-09-10 21:33:24 +0000 <henninb> geekosaur, I don't think so either on the gentoo comment. I suppose I could try and downgrade.
2022-09-10 21:34:03 +0000 <geekosaur> I don't know of a dzen2 upgrade but the workspace information would be coming from xmonad, dzaen2 doesn't reformat it
2022-09-10 21:34:20 +0000 <geekosaur> it just displays what it's given
2022-09-10 21:34:33 +0000 <henninb> agreed, it is a very strange issue.
2022-09-10 21:35:14 +0000 <henninb> i think the data coming out of xmonad is stored in a pipe, do I have that right?
2022-09-10 21:35:32 +0000 <geekosaur> try the downgrade I guess, if that fixes it then we'll have to see if something unexpectedly changed with the dzen formatting. (I think only the xmobar stuff had actually been tested, but I have trouble imagining something that would break only dzen like that)
2022-09-10 21:35:46 +0000 <geekosaur> depends on how you have it configured
2022-09-10 21:36:14 +0000 <geekosaur> we've been moving to using properties because it's kinda bad when someone misconfigures their bar and xmonad hands writing to the pipe
2022-09-10 21:36:19 +0000 <geekosaur> *hangs
2022-09-10 21:36:49 +0000 <geekosaur> but neither pipes nor X11 properties alter what they contain
2022-09-10 21:37:10 +0000 <henninb> agreed
2022-09-10 21:37:41 +0000 <henninb> I may end up switching to xmobar if I can't figure this out :)
2022-09-10 21:38:05 +0000 <henninb> for what it is worth, this is my config. https://github.com/henninb/dotfiles/blob/main/.config/xmonad/xmonad.hs
2022-09-10 21:38:59 +0000 <geekosaur> I was about to ask for that 🙂
2022-09-10 21:39:52 +0000 <henninb> :)
2022-09-10 21:40:27 +0000 <henninb> do you have a good example of using properties vs using pipes? I can also do some digging on my own.
2022-09-10 21:48:43 +0000noex(~null@user/noex)
2022-09-10 21:49:43 +0000 <geekosaur> hm. this is dzen2, I think it can only be fed via a pipe
2022-09-10 21:50:09 +0000 <geekosaur> xmobar has a property reader that can be used in place of StdinReader but dzen2 only does stdin
2022-09-10 21:51:35 +0000 <henninb> Thank you geekosaur, that makes sense. I just reading some points on that topic.
2022-09-10 21:53:23 +0000 <geekosaur> sorry for delay, I had popped outward from your xmonad.hs to look at the local dzen module and see if anything stood out in there
2022-09-10 21:54:39 +0000 <henninb> I just appreciate you taking a look and providing your thoughts. Thank you.
2022-09-10 21:55:47 +0000 <henninb> is there a way to "intercept" the content of the pipe before it is displayed?
2022-09-10 21:56:56 +0000 <geekosaur> not as such. you could arrange to write it to a file as well as the pipe though
2022-09-10 21:57:26 +0000 <henninb> that is a great idea. then I could see what is going on.
2022-09-10 21:58:15 +0000 <geekosaur> https://github.com/henninb/dotfiles/blob/main/.config/xmonad/lib/Local/DzenLogHook.hs#L41
2022-09-10 21:59:05 +0000 <geekosaur> ppOutput = \s -> hPutStrLn h s >> hPutStrLn stderr s
2022-09-10 21:59:15 +0000 <geekosaur> may have to import stderr from System.IO
2022-09-10 21:59:33 +0000 <henninb> awesome, i will give it a try.
2022-09-10 21:59:54 +0000 <geekosaur> and the output should go to ~/.xsession-errors unless you';re using startx, in which case you either need to redirect its output to a file or switch to the original console
2022-09-10 22:00:17 +0000 <henninb> I am using sddm
2022-09-10 22:01:12 +0000 <geekosaur> you may have to check iots configuration to see where the session output goes
2022-09-10 22:02:29 +0000 <henninb> ok
2022-09-10 22:04:09 +0000 <geekosaur> hah, knew I remembered something about that. ~/.local/share/sddm/xorg-session.log
2022-09-10 22:05:18 +0000 <geekosaur[m]> Test
2022-09-10 22:05:39 +0000 <geekosaur> only working in one direction 😞
2022-09-10 22:06:10 +0000 <henninb> found it.
2022-09-10 22:07:28 +0000 <henninb> I am going to paste the content in my reddit post. give me a few seconds.
2022-09-10 22:09:34 +0000 <henninb> posted.
2022-09-10 22:20:10 +0000 <geekosaur> that looks correct
2022-09-10 22:20:35 +0000 <geekosaur> most of the "noise" is setting the font or specifying the click behavior for clickableWorkspaces
2022-09-10 22:20:58 +0000 <henninb> exactly
2022-09-10 22:21:14 +0000 <geekosaur> so either the font metrics are wildly off or dzen is inserting spaces. since dzen has no code or, or reason to, edit its input, I'd check the font
2022-09-10 22:21:37 +0000 <geekosaur> or whether it changed in such a way that dzen can't handle it any more
2022-09-10 22:21:41 +0000 <henninb> good idea, I will try a different font.
2022-09-10 22:22:25 +0000 <henninb> this seems like a dzen2 issue vs an xmonad issue.
2022-09-10 22:23:27 +0000 <geekosaur> or dzaen is allocating screen space for its escapes for some reason which would be a dzen bug
2022-09-10 22:25:13 +0000 <henninb> thank you for taking a look geekosaur.
2022-09-10 22:27:41 +0000 <geekosaur> no problem, that's what we're here in #xmonad for
2022-09-10 23:03:02 +0000henninb(~henninb@97-116-154-134.mpls.qwest.net) (Quit: leaving)
2022-09-10 23:32:12 +0000noex(~null@user/noex) (Quit: :q!)
2022-09-10 23:51:31 +0000logzet(~quassel@2001:9e8:e52d:1c00:dabb:c1ff:fed3:a1b9) (Ping timeout: 248 seconds)