Home liberachat/#xmonad: Logs Calendar

Logs on 2023-01-01 (liberachat/#xmonad)

00:00:48 × thyriaen quits (~thyriaen@2a01:aea0:dd4:4bae:6245:cbff:fe9f:48b1) (Remote host closed the connection)
01:11:20 k` joins (~user@2605:a601:a60d:5400:7c8d:c18:bab3:ff90)
01:12:43 <k`> can anyone who uses nixos tell me whether there's any way to actually use `services.xserver.windowManager.xmonad.config` ?
01:27:15 <k`> It seems to compile properly when you include all the required imports in extraPackages, but changing the config and then running `nixos-rebuild switch` does not seem to actually change the xmonad settings.
02:21:27 × k` quits (~user@2605:a601:a60d:5400:7c8d:c18:bab3:ff90) (Remote host closed the connection)
03:03:06 × banc quits (banc@gateway/vpn/protonvpn/banc) (Ping timeout: 272 seconds)
03:17:02 × td_ quits (~td@83.135.9.29) (Ping timeout: 272 seconds)
03:18:23 td_ joins (~td@83.135.9.35)
03:24:30 banc joins (banc@gateway/vpn/protonvpn/banc)
03:56:53 × tremon quits (~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl) (Quit: getting boxed in)
03:58:49 × werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 260 seconds)
04:00:42 werneta joins (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
06:04:27 × jabuxas quits (~jabuxas@user/jabuxas) (Ping timeout: 248 seconds)
06:06:08 jabuxas joins (~jabuxas@user/jabuxas)
09:00:12 × liskin[m] quits (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
11:28:41 mc47 joins (~mc47@xmonad/TheMC47)
11:49:43 × mc47 quits (~mc47@xmonad/TheMC47) (Remote host closed the connection)
11:57:10 mc47 joins (~mc47@xmonad/TheMC47)
12:47:07 thyriaen joins (~thyriaen@2a01:aea0:dd4:4bae:6245:cbff:fe9f:48b1)
12:47:39 <thyriaen> can i spawn windows always on first monitor no matter which has focus ?
12:47:52 liskin[m] joins (~liskinmat@2001:470:69fc:105::768)
12:52:48 <thyriaen> to clarify - i want to spawn it on the current workspace that is active on my first monitor even if my 2nd one has focus
12:54:38 <thyriaen> my workspaces are withScreens
12:55:06 <thyriaen> i use the IndependentScreens layout
13:03:54 <thyriaen> and i want to use that whole thing in a scratchpad
13:07:42 <Solid> thyriaen: as in, all windows? In that case, just a simple manageHook would do
13:08:17 <thyriaen> no
13:08:22 <thyriaen> just one specific window
13:08:37 <Solid> as long as you can match on it, that should be fine as well
13:08:58 <thyriaen> Solid, how do i do that ?
13:09:36 <thyriaen> Solid, https://paste.tomsmeding.com/IdS9qZ2M I want to change my scratchpad to always be on currently active workspace of the main screen
13:10:21 <thyriaen> Solid, and some other windows i can identify by className for example or replace the spawn command
13:16:01 <Solid> it's probably more complicated for scratchpads, since once you summon them once they just get moved to another workspace and the manageHook isn't executed after that
13:16:18 <Solid> but for normal windows you can just do something like "appName =? "my-query" --> doShift . fromJust =<< liftX (screenWorkspace 0)"
13:19:10 <thyriaen> Solid, ok thanks
13:19:13 <thyriaen> and for scratchpads ?
13:28:10 <Solid> mh, I reckon you'd need to check for that in a logHook or something
13:28:17 <Solid> but it's probably going to be a bit annoying
13:30:25 <thyriaen> ic
13:50:01 <geekosaur> scratchpads have associated manageHooks, you should be able to do that in that and drop the matcher because the scratchpad stuff already does the matching
13:52:31 <geekosaur> you do it where you have the `customFloating` stuff now, and combine them with `<>`
13:52:53 <geekosaur> thyriaen ^^
13:53:45 <Solid> geekosaur: that'd only work on the first invocation
13:53:57 <geekosaur> mm, true
13:54:14 <Solid> btw, happy new year :)
13:56:21 <geekosaur> happy new year to you too
13:56:38 <geekosaur> no control at all over later invocations, they pop up on the focused workspace
13:58:18 <thyriaen> Year ( Happy New )
13:58:21 <Solid> could probably save the window ID to some state in the manageHook and then check against that in the logHook
13:59:14 <thyriaen> geekosaur, good to have you around
14:00:18 <geekosaur> can't use the `logHook` for this unless you've applied those patches Leary submitted; it'd cause an infinite loop
14:00:52 <Solid> oh, right, moving would involve invoking `windows`
16:02:19 <a[m]1> When using nerd fonts with the pango format, my bar doesn't show. Would anyone know why?
16:03:28 <a[m]1> I fixed it, but now changing the font seems to do nothin
17:06:28 tremon joins (~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl)
17:10:21 <thyriaen> when I use picom with xmonad - only my chrome browser gets transparent borders - any ideas is this known ?
17:24:19 jimfarrand[m] joins (~jimfarran@2001:470:69fc:105::2:eab7)
17:27:13 <geekosaur[m]> Sounds like you're on 0.17.0
17:27:59 <geekosaur[m]> Upgrade
17:33:22 <thyriaen> OH !
17:33:55 <thyriaen> geekosaur[m], i am on 17.0 yes
17:35:02 <thyriaen> geekosaur[m], not packaged with fedora on a higher version ;/
17:37:12 <geekosaur[m]> Isn't there some way to subscribe to a pre-release channel with dnf?
17:37:28 <thyriaen> there is fedora-rawhide but they also just have 17.0
17:38:38 <geekosaur[m]> Then you're stuck unless you switch to cabal or git
17:38:55 <thyriaen> cabal?
17:39:14 <thyriaen> do you know when to expect fedora inclusion of 17.1 ?
17:39:47 <thyriaen> geekosaur[m], how do i install with cabal ?
17:40:16 <geekosaur[m]> No clue, I'm an Ubuntu user
17:41:58 <geekosaur[m]> Instructions for cabal or stack should be in the install documents on the website. I'm at my sister's house occasionally looking at my phone so can't help much right now
17:42:12 <geekosaur[m]> Will be back home later today
17:42:14 <thyriaen> geekosaur[m], thanks - take care :p
17:48:24 <jimfarrand[m]> Installing via Cabal is a moderately adventurous endeavour. It's not impossible, but it's also not really optimised for end-users of software.
17:48:24 <jimfarrand[m]> First step is to get a working GHC environment.
17:48:24 <jimfarrand[m]> https://www.haskell.org/cabal/
17:50:46 <geekosaur[m]> There's also stack which makes it somewhat simpler. But it's tempting to say that if you're putting in the effort, might as well go all the way and build from git
17:52:56 jimfarrand[m] is now known as jifarra[m]
18:54:18 <HB[m]> https://xmonad.org/INSTALL.html#build-using-stack I have used these instructions with great success
19:18:33 <geekosaur> Okay, I'm back home if you still need help
19:26:10 <HB[m]> Hey happy new year! 🙂
19:27:13 <geekosaur> happy new year!
19:38:18 <thyriaen> How can i get the xprop from the frame drawn by "maim" ?
19:41:55 <HB[m]> The frame that you draw yourself with the mouse?
19:42:19 <thyriaen> HB[m], aye
19:42:36 <thyriaen> that's why it will be difficult to click it with the xprop command :p
19:42:45 <HB[m]> Well, the mouse is busy, so xprop isn't going to work.
19:43:12 <geekosaur> if you mean the border xmonad draws, that is inside the maim window so just click that
19:43:34 <geekosaur> if it's drawing a separate frame, that should also be inside (properties are set on top level windows)
19:44:47 <thyriaen> geekosaur, no i mean the thing that maim draws
19:46:50 <geekosaur> oh, the screenshot thing? that's override-redirect so you can't do much with it from xmonad
19:47:07 <geekosaur> what did you want to do with it?
19:47:07 <HB[m]> So when you use scrot or another screenshot program, it lets you draw an area on screen with mouse, the rectangle which it takes a shot of.
19:47:18 <HB[m]> He wants to get xprop for that rectangle.
19:47:21 <HB[m]> * that rectangle. I think.
19:47:40 <geekosaur> right, so that is override-redirect and not visible to xmonad
19:47:56 <geekosaur> and very likely has no properties anyway
19:47:59 <HB[m]> There you go
19:48:50 <geekosaur> I am looking at https://github.com/naelstrof/maim now
19:53:54 <geekosaur> (moreover, in most cases it's done a screen grab so xmonad couldn't do anything even if it had the window id)
20:14:45 × Forkk quits (~forkk@li926-228.members.linode.com) (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.)
20:15:11 Forkk joins (~forkk@li926-228.members.linode.com)
20:49:10 abhixec joins (~abhinav@c-67-169-139-16.hsd1.ca.comcast.net)
20:55:35 × abhixec quits (~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 265 seconds)
21:09:54 <thyriaen> geekosaur, i want picom to not draw a shadow on the border :p
21:11:48 <thyriaen> HB[m], and for this i need to identify it somehow for example the window class or something
21:12:00 <thyriaen> i know by trial and error that the type is normal but that doesn't help me
21:16:43 <geekosaur> I strongly suspect that without delving into the code for maim and finding a property it sets (if any), you'll need: shadow-exclude = [ override_redirect@: ]
21:18:07 <geekosaur> (if you have other shadow-exclude items, add that to the list instead of specifying it separately)
21:21:41 <thyriaen> what does override_redirect@: do ?
21:23:00 <thyriaen> apart from generating a syntax error :p
21:26:53 <thyriaen> not sure how to properly integrate it into the config file but starting picom with picom --shadow-exclude="override_redirect = true" does the trick
21:27:31 <thyriaen> geekosaur, what does it do ?
21:29:33 <geekosaur> interesting, I wonder if they changed the syntax in later versions (I'm running a very early one that still calls itself compton)
21:30:45 <geekosaur> `override_redirect@:` means match override-redirect windows without frames; the colon is reported by the documentation to be required, and is normally followed by a type but built-in things like override_redirect don't have types
21:32:40 <thyriaen> i see
21:32:42 <geekosaur> I may have missed part of it, also
21:33:18 <geekosaur> picom configuration is fairly complicated
21:33:19 × mc47 quits (~mc47@xmonad/TheMC47) (Remote host closed the connection)
21:33:21 <thyriaen> https://wiki.archlinux.org/title/Picom_ well here i got the syntax from
21:33:57 <thyriaen> since i have an array for the focus-exclude in my config file i decided better not mess with it and use it as argument
21:34:15 <thyriaen> hang on
21:34:31 <thyriaen> geekosaur, does that mean that polybar will also not have a shadow ?
21:34:34 <geekosaur> I just dug through maim and the slop library it uses for selection, and it sets no properties on the selection window
21:34:51 <thyriaen> also rofi lost it's shadow :/
21:34:53 <thyriaen> but i want it
21:35:13 <geekosaur> then you have a problem because there's no properties to match against
21:35:23 <geekosaur> although, hm…
21:39:31 <geekosaur> override_redirect = true && !_NET_WM_WINDOW_TYPE:32a
21:39:55 <geekosaur> hopefully that matches override-redirect windows that don't have a window type set
21:40:24 <thyriaen> what is the type 32a ?
21:40:32 <geekosaur> 32-bit atom
21:40:44 <thyriaen> i will try it real quick :p
21:40:55 <geekosaur> you can use xlsatoms to see the defined atoms
21:41:10 <geekosaur> the "32" should be optional since it's the default size of atoms
21:41:58 <thyriaen> i think something has to be escaped
21:42:37 <thyriaen> unfortunately rofi still has no shadow
21:42:48 <thyriaen> i escaped the \1
21:42:50 <thyriaen> \!
21:43:01 <geekosaur> oh, yes, some shells will require that
21:43:25 <geekosaur> I set stuff in the config file so I don't have to worry about shell issues
21:44:02 <thyriaen> my rofi window also doesnt have a window type
21:44:13 <geekosaur> you would have to xprop rofi to find out what properties it has that we might check for
21:44:16 <thyriaen> can we do the same approach but use wm_class ?
21:44:45 <geekosaur> sure, use !WM_CLASS:s instead of !_NET_WM_WINDOW_TYPE:32a
21:45:12 <thyriaen> xD
21:45:15 <thyriaen> turns out
21:45:22 <thyriaen> this maim border has a wm_class
21:45:42 <thyriaen> but rofi now has a shadow again but so does the border
21:45:45 <geekosaur> hm, I couldn't find any properties being set on the window
21:46:09 <geekosaur> !WM_NAME:s maybe?
21:46:36 <thyriaen> werks
21:46:49 <thyriaen> neat ! thanks
21:46:52 <thyriaen> one more question
21:48:03 <thyriaen> i know this is out of scope of this channel but, i have rounded rounded corners in rofi -- however picom things these rounded transparent corners in rofi "still exsists" so it draws the shadow around this imaginary squared off window
21:48:28 <thyriaen> that is an exceptionally bad description
21:49:52 <geekosaur> --detect-rounded-corners?
21:49:57 <thyriaen> already active
21:50:19 <geekosaur> that saitd it looks from the docs I have that there is no actual solution, the best you can do is just disable shadows for those windows
21:50:43 <geekosaur> --shadow-ignore-shaped
21:51:22 <thyriaen> i think a better workaround would be to make it squared and let picom do the rounding of the corners
21:51:37 <thyriaen> https://paste.tomsmeding.com/XYCNiCrq
21:51:52 <thyriaen> maybe you find an improvement that wokrs around this issue
21:53:01 <geekosaur> like I said, I have a very early version of picom. it doesn't know how to round corners itself
21:53:11 <thyriaen> ah ok
21:53:16 <thyriaen> well thanks for your help anyways
21:53:21 <thyriaen> fixed my main issue :p
22:21:36 Lin[m] is now known as Chilli[m]
22:50:59 × de-vri-es quits (~de-vri-es@voyager.de-vri.es) (Quit: Bathrobe!)
22:51:28 de-vri-es joins (~de-vri-es@voyager.de-vri.es)
22:57:12 × thyriaen quits (~thyriaen@2a01:aea0:dd4:4bae:6245:cbff:fe9f:48b1) (Quit: Leaving)
23:00:16 defjam joins (~defjam@2a02:c7e:2807:b900:f093:37cf:2efc:6f2b)

All times are in UTC on 2023-01-01.