2022/02/28

2022-02-28 00:15:39 +0100totte(~totte@h-82-196-112-155.A166.priv.bahnhof.se) (Ping timeout: 268 seconds)
2022-02-28 00:38:15 +0100iqubic(~iqubic@2601:602:9502:c70::7507)
2022-02-28 00:39:35 +0100totte(~totte@h-82-196-112-155.A166.priv.bahnhof.se)
2022-02-28 00:40:21 +0100seschwar(~seschwar@user/seschwar) (Quit: :wq)
2022-02-28 00:40:41 +0100 <iqubic> Alright... I'm having an issue where I can't get fullscreen applications to be fullscreen AND cover up my XMobar at the top of the screen.
2022-02-28 00:42:59 +0100 <iqubic> It was my impression having a manageHook rule of "isFullscreen --> doFullFloat" would just do the trick, but it doesn't. It seems that XMobar remains on the screen.
2022-02-28 00:44:31 +0100 <iqubic> I've got "layoutHook = avoidStruts $ layoutHook def" in my config to prevent XMobar from being covered up, but that seems to strict somehow.
2022-02-28 00:45:56 +0100 <liskin> iqubic: this is a layering issue, that is completely outside of xmonad's control
2022-02-28 00:46:21 +0100 <liskin> you're probably asking your xmonad to not lower itself, so it stays at the top of the stacking order
2022-02-28 00:46:26 +0100 <liskin> *your xmobar
2022-02-28 00:46:42 +0100 <iqubic> How do I ask XMobar to lower itself?
2022-02-28 00:47:34 +0100 <liskin> stop using --dock; set lowerOnStart = True and overrideRedirect = True
2022-02-28 00:48:05 +0100 <iqubic> My .xmobarrc file is non-existant.
2022-02-28 00:49:01 +0100 <iqubic> I'm using spawn "xmobar' to spawn it.
2022-02-28 00:49:11 +0100 <liskin> that's a bit weird, because lowerOnStart = True and overrideRedirect = True is the default
2022-02-28 00:49:54 +0100 <iqubic> Weird.
2022-02-28 00:50:12 +0100 <iqubic> I'm just testing this with YouTube in firefox, as the fullscreen application.
2022-02-28 00:53:42 +0100 <geekosaur> all I can say is it works here, but I don't use xmobar
2022-02-28 00:53:53 +0100 <geekosaur> F11 to toggle fullscreen
2022-02-28 00:54:46 +0100 <iqubic> Yeah, F11 does go fullscreen, but it doesn't hide XMobar.
2022-02-28 00:56:01 +0100 <iqubic> But it actually looks like XMobar isn't covering anything up. No part of the the browser window is covered by xmobar, even in full screen mode.
2022-02-28 00:56:39 +0100 <liskin> uh, so how can you tell it's not hidden when it's not covering anything?
2022-02-28 00:56:53 +0100 <iqubic> I'm not sure.
2022-02-28 00:56:58 +0100 <iqubic> I'm confusing myself
2022-02-28 00:57:16 +0100 <iqubic> When I make Firefox full screen, xmobar remains visible.
2022-02-28 00:57:43 +0100 <liskin> so firefox isn't fullscreen then?
2022-02-28 00:58:49 +0100 <iqubic> Well, I hit F11, which should make Firefox fullscreen, but it doesn't cover xmobar as it should.
2022-02-28 00:59:34 +0100 <liskin> if xmobar is visible and isn't covering any part of firefox, then firefox isn't fullscreen
2022-02-28 00:59:48 +0100 <iqubic> Weird
2022-02-28 00:59:50 +0100 <liskin> which suggests you might actually be missing ewmhFullscreen
2022-02-28 01:00:34 +0100 <iqubic> How do I get that?
2022-02-28 01:01:21 +0100 <iqubic> I've got xmonad 0.15, directly from the arch linux repos.
2022-02-28 01:01:36 +0100 <liskin> https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Hooks-EwmhDesktops.html
2022-02-28 01:02:15 +0100 <liskin> https://hackage.haskell.org/package/xmonad-contrib-0.16/docs/XMonad-Hooks-EwmhDesktops.html if you can't upgrade
2022-02-28 01:02:22 +0100 <liskin> but you should
2022-02-28 01:03:12 +0100 <iqubic> The only way I'll be able to update is whenever the new version hits the arch linux repos.
2022-02-28 01:03:46 +0100 <liskin> isn't there xmonad-contrib-git in aur or something?
2022-02-28 01:05:10 +0100 <iqubic> There might be.
2022-02-28 01:05:52 +0100 <iqubic> Yeah. There is. I'm now compiling the latest version from git.
2022-02-28 01:06:54 +0100 <geekosaur> most OSes won't update until it hits a stackage LTS so they have a stable base to work from for all haskell packages, even if they don't use stack as such
2022-02-28 01:07:01 +0100 <geekosaur> so it'll probably be a while
2022-02-28 01:08:14 +0100 <iqubic> Yeah. I'm just gonna pull xmonad-git and xmonad-contrib-git from the AUR. This essential just grabs the latest git master and complies that + plus other set-up stuff to make my login manager recognize this as a valid WM
2022-02-28 01:11:17 +0100 <iqubic> I've just updated and now I'm getting a deprecation warning here. In main I have: "let defConfig = docks $ ewmhFullscreen def"
2022-02-28 01:11:42 +0100 <iqubic> Then I have "xmonad $ defConfig {handleEventHook    = fullscreenEventHook <+> handleEventHook defConfig}
2022-02-28 01:11:58 +0100 <iqubic> fullscreenEventHook is deprecated. Can I remove that?
2022-02-28 01:12:45 +0100 <geekosaur> that's replaced by ewmhFullscreen
2022-02-28 01:12:49 +0100 <iqubic> Thanks.
2022-02-28 01:14:04 +0100 <iqubic> Do I need to kill xmonad and then log back in to get these changes to stick?
2022-02-28 01:14:42 +0100 <geekosaur> mod-q should be sufficient
2022-02-28 01:15:27 +0100 <iqubic> Cool.
2022-02-28 01:16:46 +0100 <iqubic> I've figured out the issue here...
2022-02-28 01:17:09 +0100 <iqubic> I have "isFullscreen --> doFullFloat" as one of my manageHook rules.
2022-02-28 01:18:36 +0100 <geekosaur> that actually shouldnot be involved here since I don't think firefox withdraws its window when it fullscreens
2022-02-28 01:19:00 +0100 <geekosaur> and in any case doFullFloat ignores struts
2022-02-28 01:23:59 +0100 <iqubic> If have two firefox windows open side by side, and I tell the left one to become fullscreen, it only uses its allotted rectangle of space to go fullscreen, as can be seen here: https://imgur.com/a/DfBM2oY
2022-02-28 01:24:09 +0100 <iqubic> So, it's not floating at all.
2022-02-28 01:25:01 +0100 <iqubic> This is why I don't think my manageHook rule of "isFullscreen --> doFullFloat" is working.
2022-02-28 01:26:11 +0100 <geekosaur> as I just said, manageHooks don't fire in that case. Firefox would have to withdraw the window and remap it with the STATE_FULLSCREEN atom attached
2022-02-28 01:26:33 +0100 <iqubic> Oh. I see. That's an issue.
2022-02-28 01:26:36 +0100 <geekosaur> what Firefox is doing is handled by an event instead
2022-02-28 01:26:45 +0100 <iqubic> Is there anything I can do to fix this?
2022-02-28 01:26:46 +0100 <geekosaur> and that event is what ewmhFullscreen watches for
2022-02-28 01:27:28 +0100 <geekosaur> that said, the default action should be to fullscreen it without regard for struts, like it does here, iirc
2022-02-28 01:27:46 +0100 <iqubic> My main looks like this. https://dpaste.com/H5EXBTRVV
2022-02-28 01:27:58 +0100 <iqubic> I'm very clearly using ewmhFullscreen.
2022-02-28 01:28:59 +0100 <iqubic> But I'm still getting the behavior shown in my latest screenshot.
2022-02-28 01:32:14 +0100 <iqubic> geekosaur: do you know what's going on here?
2022-02-28 01:44:16 +0100 <geekosaur> hm. you have ewmhFullscreen but not ewmh
2022-02-28 01:44:40 +0100 <geekosaur> docks $ ewmh $ ewmhFullscreen def
2022-02-28 01:45:29 +0100 <iqubic> Yeah, I just added ewmh too, and I'm still getting the same behavior.
2022-02-28 01:46:22 +0100 <geekosaur> I'm lost then
2022-02-28 01:46:35 +0100 <iqubic> Yeah... this is weird.
2022-02-28 01:47:09 +0100triumphofdeath[m(~triumphof@2001:470:69fc:105::a5c)
2022-02-28 01:50:14 +0100 <geekosaur> mm, I odn'thave ewmh in mine either, but my config is based on desktopConfig which already includes it
2022-02-28 01:50:55 +0100 <geekosaur> I doubt making that change would help you though
2022-02-28 01:54:29 +0100 <iqubic> No. That didn't help.
2022-02-28 01:55:16 +0100 <iqubic> This is a strange issue..
2022-02-28 02:00:57 +0100 <iqubic> This is an odd issue. Why is firefox being a nuisance here?
2022-02-28 02:01:57 +0100 <geekosaur> I have no idea
2022-02-28 02:02:36 +0100 <geekosaur> hm. I guess the other key difference here is I run chrome instead of firefox. can try launching it in a spare workspace and see if it behaves
2022-02-28 02:03:04 +0100 <iqubic> That might help.
2022-02-28 02:03:15 +0100 <geekosaur> that works here too
2022-02-28 02:03:37 +0100 <iqubic> Weird... Is your config public? Can I see?
2022-02-28 02:04:48 +0100 <geekosaur> https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs if you dare:)
2022-02-28 02:06:56 +0100mvk(~mvk@2607:fea8:5cc3:7e00::8c21)
2022-02-28 02:08:03 +0100 <iqubic> is mateConfig different from desktopConfig in any substantial ways?
2022-02-28 02:08:39 +0100 <geekosaur> it uses mate run and logout dialogs instead of the standard ones, otherwise no
2022-02-28 02:08:45 +0100 <iqubic> I see.
2022-02-28 02:10:12 +0100 <iqubic> I notice that "isFullscreen --> doFullFloat" isn't in your config. Why is that?
2022-02-28 02:10:57 +0100 <geekosaur> I don't use anything that maps itself fullscreened
2022-02-28 02:11:05 +0100 <geekosaur> if I did I'dprobably add it
2022-02-28 02:11:53 +0100 <iqubic> But you do use fullscreen applications, right? Like hitting F11 in Chrome makes that fullscreen for you, right?
2022-02-28 02:12:37 +0100 <geekosaur> yes. also in my IRC client
2022-02-28 02:12:54 +0100 <iqubic> What part of your config is controlling that?
2022-02-28 02:13:12 +0100 <geekosaur> as I mentioned earlier, both of those use events (ewmhFullscreen) instead of unmapping and remapping (which is the only time the manageHook runs)
2022-02-28 02:13:39 +0100 <iqubic> Firefox also uses events, right?
2022-02-28 02:14:03 +0100 <iqubic> So in theory, this should just work...
2022-02-28 02:14:17 +0100 <geekosaur> right. and it does work here
2022-02-28 02:14:32 +0100 <geekosaur> with chrome, with firefox, with hexchat
2022-02-28 02:14:32 +0100 <iqubic> What's different on my system?
2022-02-28 02:14:53 +0100 <iqubic> I'm so confused.
2022-02-28 02:16:03 +0100 <iqubic> Chromium uses event right?
2022-02-28 02:16:34 +0100 <geekosaur> all three of the programs I mentioned use events
2022-02-28 02:16:34 +0100 <iqubic> I just installed Chromium on my machine, to test... That goes fullscreen just fine!
2022-02-28 02:16:43 +0100 <geekosaur> weird
2022-02-28 02:17:04 +0100 <geekosaur> although, you had been missing ewmh before. what happens if you restart firefox?
2022-02-28 02:18:01 +0100 <iqubic> I'll be back in a moment. I haven't set up an IRC client on this machine, so I'm using a web based client in firefox. BRB.
2022-02-28 02:18:06 +0100iqubic(~iqubic@2601:602:9502:c70::7507) (Quit: Client closed)
2022-02-28 02:18:33 +0100iqubic(~iqubic@2601:602:9502:c70::7507)
2022-02-28 02:18:36 +0100 <geekosaur> I suspect firefox only checks _NET_SUPPORTED on startup, and you've made several changes to it so far by upgrading xmonad and changing ewmh and ewmhFullscreen
2022-02-28 02:19:14 +0100 <iqubic> Well, I just restarted firefox. Still not working. :(
2022-02-28 02:19:57 +0100 <iqubic> This is very very weird....
2022-02-28 02:23:31 +0100 <iqubic> I'm so very confused.
2022-02-28 02:29:08 +0100 <iqubic> xmonad is a lovely window manager. There's just this one issue.
2022-02-28 02:30:42 +0100 <iqubic> I'm so very flummoxed here.
2022-02-28 02:38:27 +0100 <iqubic> geekosaur: Just on a whim, I tried changing the value of startupHook from "startupHook = myStartupHook" to "myStartupHook <+> startupHook defConfig". Recall that "defConfig = dock $ ewmh $ ewmhFullscreen" Now firefox is able to go fullscreen just fine.
2022-02-28 02:39:08 +0100 <iqubic> Why the heck would that make any difference, and why would that only affect firefox and not chromium?
2022-02-28 02:42:02 +0100 <fizzie> `ewmhFullscreen` at least adds a startupHook that does the EWMH fullscreen advertisement.
2022-02-28 02:42:55 +0100 <iqubic> Make sense.
2022-02-28 02:43:00 +0100 <fizzie> (As in, adds the _NET_WM_STATE and _NET_WM_STATE_FULLSCREEN atoms to the _NET_SUPPORTED property of the root window.)
2022-02-28 02:44:14 +0100 <geekosaur> but that is added *to* the startupHook, you shouldn't need that
2022-02-28 02:44:37 +0100 <geekosaur> oh wait, but startupHook defConfig. yes, that makes sense
2022-02-28 02:46:03 +0100 <iqubic> Yeah. I'm now mconcat-ing my own startup hook to the startup hooks generated via (docks $ ewmh $ ewmhFullscreen def)
2022-02-28 02:47:12 +0100 <iqubic> <+> is just infix mconcat, right? Why does that exist if <> is also infix mconcat and already in Data.Monoid? Is this just a re-export with a new name so that new users don't need to import Data.Monoid?
2022-02-28 02:47:49 +0100 <geekosaur> <+> came first, and <> was actually borrowed from xmonad
2022-02-28 02:48:06 +0100 <iqubic> Wait... really? That's so wild.
2022-02-28 02:48:09 +0100 <geekosaur> they renamed it because ghc was already using <+> with a different meaning (from one of the prettyprinter packages iirc)
2022-02-28 02:51:24 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 240 seconds)
2022-02-28 02:55:24 +0100 <geekosaur> in the first few releases of xmonad, <+> was mconcat specialized to ManageHooks. That changed around 2008 or 2009 when we removed the specialization and just made it mconcat. <> was around 2013, I think
2022-02-28 03:02:43 +0100 <geekosaur> also it's mappend, not mconcat,whoops. composeAll is mconcat specialized to ManageHooks
2022-02-28 03:07:17 +0100catman(~catman@user/catman)
2022-02-28 03:15:04 +0100 <iqubic> geekosaur: Yeah, I meant mconcat.
2022-02-28 03:18:09 +0100 <catman> got this error on both arch and artix after a haskell update with pacman. not entirely sure how to resolve.
2022-02-28 03:18:16 +0100 <catman> xmonad: error while loading shared libraries: libHSutf8-string-1.0.2-9eFA57BgKXNHtjvfuIOq9f-ghc9.0.2.so: cannot open shared object file: No such file or directory
2022-02-28 03:19:00 +0100 <catman> have tried reinstalling xmonad-contrib and ghc
2022-02-28 03:23:04 +0100catman(~catman@user/catman) (Quit: WeeChat 3.5-dev)
2022-02-28 03:55:46 +0100iqubic(~iqubic@2601:602:9502:c70::7507) (Quit: Client closed)
2022-02-28 03:59:07 +0100 <geekosaur> @tell catman arch screwed something up again. if they handled their haskell packages properly this wouldn't happen. (you're the second one tonight)
2022-02-28 03:59:07 +0100 <lambdabot> Consider it noted.
2022-02-28 04:00:31 +0100 <geekosaur> @tell catman if you want reliably working xmonad and xmobar, wipe all haskell related arch packages from your system, use ghcup to install ghc and stack and/or cabal, then follow https://xmonad.org/INSTALL.html
2022-02-28 04:00:31 +0100 <lambdabot> Consider it noted.
2022-02-28 04:03:00 +0100steve__(~steve@ool-182c2b80.dyn.optonline.net) (Ping timeout: 240 seconds)
2022-02-28 04:03:17 +0100banc(banc@gateway/vpn/airvpn/banc) (Ping timeout: 272 seconds)
2022-02-28 04:21:01 +0100td_(~td@muedsl-82-207-238-210.citykom.de) (Ping timeout: 272 seconds)
2022-02-28 04:22:33 +0100td_(~td@94.134.91.216)
2022-02-28 04:25:13 +0100banc(banc@gateway/vpn/airvpn/banc)
2022-02-28 04:58:42 +0100iqubic(~iqubic@c-67-171-37-233.hsd1.wa.comcast.net)
2022-02-28 05:00:44 +0100 <iqubic> Is it possible to override the borderWidth value for certain windows? Specifically I'd like to remove the border from Firefox's right click context menu (why is this even a separate window?), and also from the windows spawned by the dunst notification daemon.
2022-02-28 05:02:18 +0100catman(~catman@user/catman)
2022-02-28 05:32:52 +0100catman(~catman@user/catman) (Quit: WeeChat 3.5-dev)
2022-02-28 05:55:20 +0100steve__(~steve@ool-182c2b80.dyn.optonline.net)
2022-02-28 05:55:23 +0100Steven_M(~Steven_M@user/steven-m/x-0972586)
2022-02-28 05:59:35 +0100abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 256 seconds)
2022-02-28 06:08:21 +0100Steven_M(~Steven_M@user/steven-m/x-0972586) (Quit: Leaving)
2022-02-28 06:08:28 +0100 <iqubic> Turns out I just need to read the docs for XMonad.Layout.NoBorders
2022-02-28 06:08:37 +0100sagax(~sagax_nb@user/sagax) (Quit: Konversation terminated!)
2022-02-28 06:51:48 +0100iqubic(~iqubic@c-67-171-37-233.hsd1.wa.comcast.net) (Quit: Connection closed)
2022-02-28 06:53:04 +0100catman(~catman@user/catman)
2022-02-28 07:04:55 +0100catman(~catman@user/catman) (Quit: WeeChat 3.5-dev)
2022-02-28 08:16:08 +0100 <Solid> ?tell abhixec I remember seeing some hacks for proper fractional scaling for X11 on the Arch wiki, but I'm not sure how well they work
2022-02-28 08:16:08 +0100 <lambdabot> Consider it noted.
2022-02-28 08:16:36 +0100 <Solid> ?tell abhixec in either case I'm pretty certain you could automate at least switching to bigger fonts when an external monitor is connected and switching back when it's disconnected
2022-02-28 08:16:36 +0100 <lambdabot> Consider it noted.
2022-02-28 08:35:56 +0100cfricke(~cfricke@user/cfricke)
2022-02-28 09:03:19 +0100paul(~paul@2400:4052:10a1:f200:7759:4efa:aa1:b997)
2022-02-28 09:35:16 +0100catman(~catman@user/catman)
2022-02-28 09:36:19 +0100paul(~paul@2400:4052:10a1:f200:7759:4efa:aa1:b997) (Quit: WeeChat 3.3)
2022-02-28 09:37:33 +0100paul(~paul@2400:4052:10a1:f200:7759:4efa:aa1:b997)
2022-02-28 09:38:14 +0100paul(~paul@2400:4052:10a1:f200:7759:4efa:aa1:b997) (Client Quit)
2022-02-28 09:39:52 +0100benthumb2000(~paul@2400:4052:10a1:f200:7759:4efa:aa1:b997)
2022-02-28 10:00:12 +0100mc47[m](~mc47matri@2001:470:69fc:105::733) (Quit: You have been kicked for being idle)
2022-02-28 10:00:24 +0100elonsroadster[m](~elonsroad@2001:470:69fc:105::d121) (Quit: You have been kicked for being idle)
2022-02-28 11:41:50 +0100benthumb2000(~paul@2400:4052:10a1:f200:7759:4efa:aa1:b997) (Quit: WeeChat 3.3)
2022-02-28 12:07:25 +0100yauhsienhuangtw(~Yau-Hsien@2402:7500:5e4:c8b7:c90:6bda:6af1:8273)
2022-02-28 12:11:00 +0100yauhsien_(~Yau-Hsien@61-231-39-29.dynamic-ip.hinet.net) (Ping timeout: 240 seconds)
2022-02-28 12:32:34 +0100sleblanc(~sleblanc@user/sleblanc) (Remote host closed the connection)
2022-02-28 12:54:29 +0100yauhsien_(~Yau-Hsien@61-231-39-29.dynamic-ip.hinet.net)
2022-02-28 12:57:37 +0100yauhsienhuangtw(~Yau-Hsien@2402:7500:5e4:c8b7:c90:6bda:6af1:8273) (Ping timeout: 240 seconds)
2022-02-28 12:57:56 +0100yauhsienhuangtw(~Yau-Hsien@61-231-39-29.dynamic-ip.hinet.net)
2022-02-28 12:59:02 +0100yauhsien_(~Yau-Hsien@61-231-39-29.dynamic-ip.hinet.net) (Ping timeout: 240 seconds)
2022-02-28 13:32:34 +0100zawaken(~zawaken@user/zawaken) (Quit: ZNC 1.9.x-git-unknown - https://znc.in)
2022-02-28 13:57:21 +0100catman(~catman@user/catman) (Quit: WeeChat 3.5-dev)
2022-02-28 15:11:11 +0100catman(~catman@user/catman)
2022-02-28 15:53:02 +0100dschrempf(~dominik@070-207.dynamic.dsl.fonira.net)
2022-02-28 15:58:23 +0100yauhsienhuangtw(~Yau-Hsien@61-231-39-29.dynamic-ip.hinet.net) (Read error: Connection reset by peer)
2022-02-28 16:22:20 +0100dschrempf(~dominik@070-207.dynamic.dsl.fonira.net) (Quit: WeeChat 3.3)
2022-02-28 16:30:13 +0100yauhsien_(~Yau-Hsien@61-231-39-29.dynamic-ip.hinet.net)
2022-02-28 16:58:24 +0100seschwar(~seschwar@user/seschwar)
2022-02-28 17:05:33 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-02-28 20:25:11 +0100cfricke(~cfricke@user/cfricke) (Ping timeout: 256 seconds)
2022-02-28 20:52:28 +0100abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net)
2022-02-28 21:01:59 +0100abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) (Remote host closed the connection)
2022-02-28 22:05:24 +0100twiclo1(~twiclo@vpn.utahbroadband.com) (Ping timeout: 240 seconds)
2022-02-28 22:07:26 +0100twiclo1(~twiclo@mail.twil.cx)
2022-02-28 22:56:48 +0100zawaken(~zawaken@user/zawaken)
2022-02-28 23:36:50 +0100seschwar(~seschwar@user/seschwar) (Quit: :wq)