Home liberachat/#xmonad: Logs Calendar

Logs on 2023-04-02 (liberachat/#xmonad)

00:23:11 × MrElendig quits (~Urist@archlinux/op/MrElendig) (Quit: rock and stone)
00:24:23 MrElendig joins (~Urist@archlinux/op/MrElendig)
01:14:50 catern joins (~sbaugh@2604:2000:8fc0:b:a9c7:866a:bf36:3407)
01:15:59 <catern> sorry to ask a slightly lazy question, but... how does xmonad know to float windows that have a floating _NET_WM_WINDOW_TYPE ? e.g. _NET_WM_WINDOW_TYPE_UTILITY; I can't see any code which deals with that
01:20:42 <liskin> catern: it doesn't, there's a different heuristic: https://github.com/xmonad/xmonad/blob/b06d885e764cc57d78e94402d583cbf72741d583/src/XMonad/ManageHook.hs#L110
01:21:17 <liskin> https://github.com/xmonad/xmonad/blob/ab99c17a68144013d4c109e80ec9e51b16a64d54/src/XMonad/Operations.hs#L93
01:22:08 <catern> liskin: aha i seeeeee, thank you
01:22:32 <catern> (how vexing, now I have to figure out how to achieve one of these conditions with emacs...)
01:23:09 <liskin> catern: it's probably easier to add a managehook :-)
01:23:30 <catern> I'm trying to fix something upstream :) https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62164
01:23:39 <liskin> oh
01:24:36 × hightower2 quits (~hightower@213.149.61.142) (Remote host closed the connection)
01:26:01 <liskin> https://tronche.com/gui/x/icccm/sec-4.html#WM_TRANSIENT_FOR possibly? not sure if that has the required semantics though
01:27:04 <liskin> "_NET_WM_WINDOW_TYPE_UTILITY indicates a small persistent utility window, such as a palette or toolbox. It is distinct from type TOOLBAR because it does not correspond to a toolbar torn off from the main application. It's distinct from type DIALOG because it isn't a transient dialog, the user will probably keep it open while they're working. Windows of this type may set the WM_TRANSIENT_FOR hint
01:27:06 <liskin> indicating the main application window." is what EWMH spec says
01:27:26 <catern> oh hah I missed that, well, perfect then!
01:27:54 <catern> liskin: great find, thank you!
01:28:39 <liskin> always glad to be helpful :-)
01:35:14 <catern> liskin: thank you very much, that was the last bit I needed, I now have a beautifully floating emacs frame :)
02:25:51 × td_ quits (~td@i5387093C.versanet.de) (Ping timeout: 255 seconds)
02:27:36 td_ joins (~td@i53870922.versanet.de)
02:31:28 th3m45t3rm1nd joins (~th3m45t3r@2401:4900:b09:664b:f57e:f75:d154:5f39)
02:33:08 × th3m45t3rm1nd quits (~th3m45t3r@2401:4900:b09:664b:f57e:f75:d154:5f39) (Client Quit)
03:49:33 IsaacShapira[m] joins (~isaacshap@2001:470:69fc:105::1:c253)
03:49:56 <IsaacShapira[m]> I am looking to get notified when my laptop battery is low
03:50:56 <IsaacShapira[m]> I was thinking I would forkIO and then recurse with a threadDelay, but the Dzen stuff is in X not IO
03:57:02 noex joins (~null@user/noex)
06:35:21 × stellacy quits (~stellacy@gateway/tor-sasl/stellacy) (Remote host closed the connection)
06:37:58 stellacy joins (~stellacy@gateway/tor-sasl/stellacy)
08:17:35 × werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 260 seconds)
08:19:16 werneta joins (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
08:46:00 <Solid> should we draft a release announcement for 0.17.2? I'm thinking that the release is so small it may not be necessary, as most user will not notice any difference
08:46:11 <Solid> On the other hand, people should of course be informed that we're doing something
08:46:18 <Solid> so… thoughts?
10:16:27 chomwitt joins (~chomwitt@2a02:587:7a16:e500:1ac0:4dff:fedb:a3f1)
10:36:03 thyriaen joins (~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1)
10:36:42 <thyriaen> Howdy friends, what was the layout again that shows only a single window in the middle of the screen ( not stretched over everything ) ?
10:44:54 <thyriaen> I think i found it: CenteredIfSingle
10:56:08 <liskin> Solid: *drafting* a release announcement may indeed be unnecessary :-)
10:57:09 × thyriaen quits (~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1) (Remote host closed the connection)
10:57:34 thyriaen joins (~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1)
10:57:53 <thyriaen> What do i have to import for https://hackage.haskell.org/package/xmonad-contrib-0.17.1/docs/XMonad-Layout-CenteredIfSingle.html Grid ?
11:00:19 <liskin> Solid: it'd only make sense if you wanted to talk about what is *not* in the release and is coming, but then we did that quite recently, so now it's totally fine to justify say "we released a quick .2 with a single fix for ghc 9.2"
11:00:39 <liskin> s/justify/just/
11:04:03 <thyriaen> how do i have to restart xmonad if the type of the things don't change ?
11:05:06 × thyriaen quits (~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1) (Remote host closed the connection)
11:10:53 malook joins (~Thunderbi@5.109.228.143)
11:12:00 × malook quits (~Thunderbi@5.109.228.143) (Client Quit)
11:19:28 mc47 joins (~mc47@xmonad/TheMC47)
11:33:45 thyriaen joins (~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1)
11:41:20 thyriaen_ joins (~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1)
11:42:05 × thyriaen quits (~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1) (Ping timeout: 250 seconds)
12:33:20 <geekosaur> @tell thyriaen I think you wanted mod-shift-space?
12:33:20 <lambdabot> Consider it noted.
12:38:51 × thyriaen_ quits (~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1) (Ping timeout: 250 seconds)
12:39:46 <Solid> liskin: alright, sounds good
13:11:29 <liskin> Solid: once you're done, good practice is that you merge the release branch back into master
13:11:47 <liskin> you could reconcile CHANGES.md manually but it's nicer to just see everything in git log
13:12:01 <liskin> (well you will have to resolve the conflicts manually anyway)
13:12:03 <Solid> liskin: I was going to cherry pick the 2 or 3 commits that we actually need
13:12:20 <Solid> but if you want I can also just merge the branch
13:13:17 <liskin> I think merge is better in this case
13:13:28 <liskin> what would you cherry-pick anyway? the version bump and changes?
13:14:31 <Solid> yeah
13:22:54 <Solid> just feels weird pushing 30 commits with the content of 4, I guess :)
13:23:15 <Solid> but you're right that it probably resutls in a more readable git log
13:23:35 <liskin> well you're not pushing 30 commits, you're just drawing a line in the git log from one branch to another :-)
13:23:50 <liskin> (git is about trees, not diffs)
13:26:30 <Solid> but I do, right? When I merge the branch commit X will get a new hash and appear a second time in git log
13:27:19 <liskin> you will make some commits appear twice in the history, yes
13:29:13 <liskin> my point was that these commits already have new hashes and already had been pushed
13:29:27 <liskin> they just wouldn't be visible in the history of master by default without the merge
13:33:51 <Solid> ah, I see what you mean
13:35:29 <xmonadtrack> xmonad a5ob7r {Tony Zorman} * v0.17.1-1-g9d0fd62: Fix compatibilities with mtl 2.3.1 (5 months ago, 3 files, 5+ 2-) https://github.com/xmonad/xmonad/commit/9d0fd62cb281
13:35:30 <xmonadtrack> xmonad a5ob7r {Tony Zorman} * v0.17.1-2-gfaf5cf7: Fix compatibilities with unix 2.8.0.0 (5 months ago, 1 file, 5+ 0-) https://github.com/xmonad/xmonad/commit/faf5cf7b2737
13:35:37 <xmonadtrack> xmonad Tomas Janousek {Tony Zorman} * v0.17.1-3-gf2c9c75: ci: Add hlint workflow (5 months ago, 1 file, 22+ 0-) https://github.com/xmonad/xmonad/commit/f2c9c75f671d
13:35:44 <xmonadtrack> ... and 28 more commits
13:38:15 <liskin> https://github.com/xmonad/xmonad/blame/40f8246080e1e7eb04e887e1fca05840901e75ff/MAINTAINERS.md#L120 keeps biting us
13:38:33 <liskin> I'll need to figure out a way to make that less error-prone :-)
13:40:00 <liskin> I mean, nobody's really going to miss this because it's just xmonad-contrib that actually links to the specific version
13:40:19 <liskin> and the docs for 0.17.1 are missing as well :-)
13:42:46 × mc47 quits (~mc47@xmonad/TheMC47) (Remote host closed the connection)
13:45:38 <xmonadtrack> New xmonad-contrib branch created: pull/807 (1 commit) https://github.com/xmonad/xmonad-contrib/pull/807
13:46:05 <liskin> Solid: shall we drop the release branch now?
13:47:43 <Solid> r.e. docs: whoops :)
13:47:49 <Solid> liskin: sure, we can do that
13:49:02 <liskin> the docs issue is on me I guess, that infra is from back when a release took an entire day of three of us
13:49:19 thyriaen_ joins (~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1)
13:50:01 <liskin> we didn't even know how we do the dev version bumps
13:50:06 <liskin> I'll need to rethink this
13:52:45 <geekosaur> thyriaen_, you wanted mod-shift-space
13:53:07 <geekosaur> sorry, I was asleep when you were asking stuff and those two are focused on releasing 0.17.2 with ghc 9.6 compat
13:54:59 <thyriaen_> come on
13:55:10 <thyriaen_> i just updated to fedora 38 to get 0.17.1
13:55:30 <thyriaen_> and now you are telling me i have to struggle again to be behind in versions probably missing stuff again
13:55:46 <mc47[m]> You're not missing anything
13:55:49 <geekosaur> fedora doesn't have ghc 9.6 so you're safe. there are no new features in 0.17.2, just ghc 9.6 compat
13:55:56 <thyriaen_> perfect
13:56:05 <thyriaen_> i think my bug report worked
13:56:16 <thyriaen_> that they included 0.17.1 in this release :p
14:02:14 <liskin> oh, is fedora the last distro that still packages reasonably up-to-date xmonad in a reasonably-usable fashion?
14:02:47 <liskin> (I keep forgetting the BSDs, I'll see myself out :-))
14:03:31 <thyriaen_> liskin, it is the reason why i moved to fedora, yes
14:11:03 <xmonadtrack> New branch created: pull/446 (1 commit) https://github.com/xmonad/xmonad/pull/446
14:16:06 <geekosaur> liskin, Solid, re branch merging and such: DCSS never needs to merge branches back into master. everything in a branch, including documentation, originates in a cherrypick from master, so there would be nothing to merge.
14:16:55 <geekosaur> and every release starts with a branch from master, after which only bugfixes and release documentation are cherrypicked.
14:18:19 <geekosaur> bugfixes are cherrypicked to branches when added to master, and every so often if enough such cherrypicks have built up a new branch release is made (this is one reason for the bot, it tracks that)
14:18:56 <geekosaur> or if a severe enough bug is fixed (usually means it's a coredump bug, not that we usually need to worry about that)
14:19:32 <liskin> yeah, if we had longer-lived stable branches and master was already 0.17.999 or 0.18, I probably wouldn't suggest merging back
14:20:11 <liskin> (although it's still nice to update the changelog and see all the releases in git log easily, but the additional noise may not be worth it any more)
14:23:01 <geekosaur> you do that on master and cherrypick it, as with bugfixes, so they should still be visible?
14:25:42 <geekosaur> there are also other ways to do this; I'm just not as aware of them because I'm most involved with DCSS
16:01:11 × liskin[m] quits (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
16:37:20 × chomwitt quits (~chomwitt@2a02:587:7a16:e500:1ac0:4dff:fedb:a3f1) (Ping timeout: 265 seconds)
16:40:39 chomwitt joins (~chomwitt@2a02:587:7a16:e500:1ac0:4dff:fedb:a3f1)
16:42:31 horzion joins (~horzion@ProtonDB/horzion)
16:46:59 <horzion> heya, i feel a bit lost. i am trying to get wireless network working on start, so that it dont need to manually connect and put in credentials. On KDE KDEWallet handles that afaik, but idk how i would go about this in XMonad
16:47:12 liskin[m] joins (~liskinmat@2001:470:69fc:105::768)
16:47:23 <MrElendig> use networkmanager, be happy
16:47:53 <MrElendig> it works independently of X
16:48:08 <horzion> i do use networkmanager
16:48:38 <MrElendig> do you have polkit?
16:48:49 <horzion> yes
16:49:19 <MrElendig> shouldn't be asking for any password then if you tell it to remember the credentials
16:49:40 <horzion> i have the feeling that kdewallet does something to prevent this from working
16:50:20 <MrElendig> not really
16:51:11 <MrElendig> but if you don't check the "allow this connection for all users" or whatever the checkbox is named, then nm will use the user keyring for storage, in which case you would have to unlock said keyring on boot/login
16:52:00 <MrElendig> if you store the connection as global, it will be stored in plaintext in /etc/NetworkManager/system-connections/ and be available before login too
16:52:09 <horzion> i see
16:52:11 <horzion> will try
16:52:49 <MrElendig> hmm, option is called "All users may connect to this network" or similar depending on which frontend you are using
16:52:59 <horzion> qt, and yeah found it
16:53:01 <horzion> will try now
16:53:06 <MrElendig> if you want to unlock kwallet on login, you can do that using pam
16:53:31 <MrElendig> https://wiki.archlinux.org/title/KDE_Wallet#Configure_PAM or similar for your distro
16:55:36 × horzion quits (~horzion@ProtonDB/horzion) (Remote host closed the connection)
16:56:57 horzion joins (~horzion@ProtonDB/horzion)
16:57:03 <horzion> worked like a charm
16:57:44 <MrElendig> downside using the shared connection is of course that the credentials are in plain, but they are not world readable
16:57:44 <horzion> was my main issue for now, since i couldnt open firefox to search for stuff i wanna change
16:57:53 <horzion> aye
16:58:04 <MrElendig> firefox should work fine in xmonad
16:58:18 <horzion> it does, but it cant connect to anything if there is no network connection
16:58:28 <MrElendig> nmcli connect ...
16:58:45 <MrElendig> connection*
16:59:03 <horzion> yeah, but i dont know that out of my head :P
16:59:16 <horzion> it works now, so thats all that matters
16:59:17 <MrElendig> it has pretty good docs and --help
16:59:27 <MrElendig> there is also nmtui
16:59:51 <horzion> last time i used network via cli, i had an aneurism. there is stuff i rather do with gui, ya know
17:00:10 <horzion> but i appreciate your help and suggestions
17:00:25 <horzion> onto getting xmobar and gridselect working
17:00:28 <MrElendig> nmtui is almost gui :)
17:00:33 <horzion> hm
17:01:36 × thyriaen_ quits (~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1) (Quit: Leaving)
17:25:24 × stellacy quits (~stellacy@gateway/tor-sasl/stellacy) (Remote host closed the connection)
17:28:50 stellacy joins (~stellacy@gateway/tor-sasl/stellacy)
17:58:56 × werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 248 seconds)
18:14:58 × stellacy quits (~stellacy@gateway/tor-sasl/stellacy) (Remote host closed the connection)
18:15:16 stellacy joins (~stellacy@gateway/tor-sasl/stellacy)
19:01:01 werneta joins (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
19:25:18 × horzion quits (~horzion@ProtonDB/horzion) (Quit: Off praying to the Omnissiah)
19:36:25 sagax joins (~sagax_nb@user/sagax)
20:01:28 × werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 252 seconds)
20:02:13 werneta joins (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
20:27:11 × sagax quits (~sagax_nb@user/sagax) (Remote host closed the connection)
22:41:59 catman joins (~catman@user/catman)
22:55:09 × catman quits (~catman@user/catman) (Quit: WeeChat 3.8)
23:50:35 × chomwitt quits (~chomwitt@2a02:587:7a16:e500:1ac0:4dff:fedb:a3f1) (Ping timeout: 264 seconds)

All times are in UTC on 2023-04-02.