IRCBrowse

2023/04/02

2023-04-02 01:20:59 +0200catman(~catman@user/catman)
2023-04-02 01:26:02 +0200catman(~catman@user/catman) (Quit: WeeChat 3.8)
2023-04-02 02:23:11 +0200MrElendig(~Urist@archlinux/op/MrElendig) (Quit: rock and stone)
2023-04-02 02:24:23 +0200MrElendig(~Urist@archlinux/op/MrElendig)
2023-04-02 03:14:50 +0200catern(~sbaugh@2604:2000:8fc0:b:a9c7:866a:bf36:3407)
2023-04-02 03:15:59 +0200 <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
2023-04-02 03:20:42 +0200 <liskin> catern: it doesn't, there's a different heuristic: https://github.com/xmonad/xmonad/blob/b06d885e764cc57d78e94402d583cbf72741d583/src/XMonad/ManageHo…
2023-04-02 03:21:17 +0200 <liskin> https://github.com/xmonad/xmonad/blob/ab99c17a68144013d4c109e80ec9e51b16a64d54/src/XMonad/Operatio…
2023-04-02 03:22:08 +0200 <catern> liskin: aha i seeeeee, thank you
2023-04-02 03:22:32 +0200 <catern> (how vexing, now I have to figure out how to achieve one of these conditions with emacs...)
2023-04-02 03:23:09 +0200 <liskin> catern: it's probably easier to add a managehook :-)
2023-04-02 03:23:30 +0200 <catern> I'm trying to fix something upstream :) https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62164
2023-04-02 03:23:39 +0200 <liskin> oh
2023-04-02 03:24:36 +0200hightower2(~hightower@213.149.61.142) (Remote host closed the connection)
2023-04-02 03:26:01 +0200 <liskin> https://tronche.com/gui/x/icccm/sec-4.html#WM_TRANSIENT_FOR possibly? not sure if that has the required semantics though
2023-04-02 03:27:04 +0200 <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
2023-04-02 03:27:06 +0200 <liskin> indicating the main application window." is what EWMH spec says
2023-04-02 03:27:26 +0200 <catern> oh hah I missed that, well, perfect then!
2023-04-02 03:27:54 +0200 <catern> liskin: great find, thank you!
2023-04-02 03:28:39 +0200 <liskin> always glad to be helpful :-)
2023-04-02 03:35:14 +0200 <catern> liskin: thank you very much, that was the last bit I needed, I now have a beautifully floating emacs frame :)
2023-04-02 04:25:51 +0200td_(~td@i5387093C.versanet.de) (Ping timeout: 255 seconds)
2023-04-02 04:27:36 +0200td_(~td@i53870922.versanet.de)
2023-04-02 04:31:28 +0200th3m45t3rm1nd(~th3m45t3r@2401:4900:b09:664b:f57e:f75:d154:5f39)
2023-04-02 04:33:08 +0200th3m45t3rm1nd(~th3m45t3r@2401:4900:b09:664b:f57e:f75:d154:5f39) (Client Quit)
2023-04-02 05:49:33 +0200IsaacShapira[m](~isaacshap@2001:470:69fc:105::1:c253)
2023-04-02 05:49:56 +0200 <IsaacShapira[m]> I am looking to get notified when my laptop battery is low
2023-04-02 05:50:56 +0200 <IsaacShapira[m]> I was thinking I would forkIO and then recurse with a threadDelay, but the Dzen stuff is in X not IO
2023-04-02 05:57:02 +0200noex(~null@user/noex)
2023-04-02 08:35:21 +0200stellacy(~stellacy@gateway/tor-sasl/stellacy) (Remote host closed the connection)
2023-04-02 08:37:58 +0200stellacy(~stellacy@gateway/tor-sasl/stellacy)
2023-04-02 10:17:35 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 260 seconds)
2023-04-02 10:19:16 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-04-02 10:46:00 +0200 <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
2023-04-02 10:46:11 +0200 <Solid> On the other hand, people should of course be informed that we're doing something
2023-04-02 10:46:18 +0200 <Solid> so… thoughts?
2023-04-02 12:16:27 +0200chomwitt(~chomwitt@2a02:587:7a16:e500:1ac0:4dff:fedb:a3f1)
2023-04-02 12:36:03 +0200thyriaen(~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1)
2023-04-02 12:36:42 +0200 <thyriaen> Howdy friends, what was the layout again that shows only a single window in the middle of the screen ( not stretched over everything ) ?
2023-04-02 12:44:54 +0200 <thyriaen> I think i found it: CenteredIfSingle
2023-04-02 12:56:08 +0200 <liskin> Solid: *drafting* a release announcement may indeed be unnecessary :-)
2023-04-02 12:57:09 +0200thyriaen(~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1) (Remote host closed the connection)
2023-04-02 12:57:34 +0200thyriaen(~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1)
2023-04-02 12:57:53 +0200 <thyriaen> What do i have to import for https://hackage.haskell.org/package/xmonad-contrib-0.17.1/docs/XMonad-Layout-CenteredIfSingle.html Grid ?
2023-04-02 13:00:19 +0200 <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"
2023-04-02 13:00:39 +0200 <liskin> s/justify/just/
2023-04-02 13:04:03 +0200 <thyriaen> how do i have to restart xmonad if the type of the things don't change ?
2023-04-02 13:05:06 +0200thyriaen(~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1) (Remote host closed the connection)
2023-04-02 13:10:53 +0200malook(~Thunderbi@5.109.228.143)
2023-04-02 13:12:00 +0200malook(~Thunderbi@5.109.228.143) (Client Quit)
2023-04-02 13:19:28 +0200mc47(~mc47@xmonad/TheMC47)
2023-04-02 13:33:45 +0200thyriaen(~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1)
2023-04-02 13:41:20 +0200thyriaen_(~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1)
2023-04-02 13:42:05 +0200thyriaen(~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1) (Ping timeout: 250 seconds)
2023-04-02 14:33:20 +0200 <geekosaur> @tell thyriaen I think you wanted mod-shift-space?
2023-04-02 14:33:20 +0200 <lambdabot> Consider it noted.
2023-04-02 14:38:51 +0200thyriaen_(~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1) (Ping timeout: 250 seconds)
2023-04-02 14:39:46 +0200 <Solid> liskin: alright, sounds good
2023-04-02 15:11:29 +0200 <liskin> Solid: once you're done, good practice is that you merge the release branch back into master
2023-04-02 15:11:47 +0200 <liskin> you could reconcile CHANGES.md manually but it's nicer to just see everything in git log
2023-04-02 15:12:01 +0200 <liskin> (well you will have to resolve the conflicts manually anyway)
2023-04-02 15:12:03 +0200 <Solid> liskin: I was going to cherry pick the 2 or 3 commits that we actually need
2023-04-02 15:12:20 +0200 <Solid> but if you want I can also just merge the branch
2023-04-02 15:13:17 +0200 <liskin> I think merge is better in this case
2023-04-02 15:13:28 +0200 <liskin> what would you cherry-pick anyway? the version bump and changes?
2023-04-02 15:14:31 +0200 <Solid> yeah
2023-04-02 15:22:54 +0200 <Solid> just feels weird pushing 30 commits with the content of 4, I guess :)
2023-04-02 15:23:15 +0200 <Solid> but you're right that it probably resutls in a more readable git log
2023-04-02 15:23:35 +0200 <liskin> well you're not pushing 30 commits, you're just drawing a line in the git log from one branch to another :-)
2023-04-02 15:23:50 +0200 <liskin> (git is about trees, not diffs)
2023-04-02 15:26:30 +0200 <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
2023-04-02 15:27:19 +0200 <liskin> you will make some commits appear twice in the history, yes
2023-04-02 15:29:13 +0200 <liskin> my point was that these commits already have new hashes and already had been pushed
2023-04-02 15:29:27 +0200 <liskin> they just wouldn't be visible in the history of master by default without the merge
2023-04-02 15:33:51 +0200 <Solid> ah, I see what you mean
2023-04-02 15:35:29 +0200 <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
2023-04-02 15:35:30 +0200 <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
2023-04-02 15:35:37 +0200 <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
2023-04-02 15:35:44 +0200 <xmonadtrack> ... and 28 more commits
2023-04-02 15:38:15 +0200 <liskin> https://github.com/xmonad/xmonad/blame/40f8246080e1e7eb04e887e1fca05840901e75ff/MAINTAINERS.md#L120 keeps biting us
2023-04-02 15:38:33 +0200 <liskin> I'll need to figure out a way to make that less error-prone :-)
2023-04-02 15:40:00 +0200 <liskin> I mean, nobody's really going to miss this because it's just xmonad-contrib that actually links to the specific version
2023-04-02 15:40:19 +0200 <liskin> and the docs for 0.17.1 are missing as well :-)
2023-04-02 15:42:46 +0200mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2023-04-02 15:45:38 +0200 <xmonadtrack> New xmonad-contrib branch created: pull/807 (1 commit) https://github.com/xmonad/xmonad-contrib/pull/807
2023-04-02 15:46:05 +0200 <liskin> Solid: shall we drop the release branch now?
2023-04-02 15:47:43 +0200 <Solid> r.e. docs: whoops :)
2023-04-02 15:47:49 +0200 <Solid> liskin: sure, we can do that
2023-04-02 15:49:02 +0200 <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
2023-04-02 15:49:19 +0200thyriaen_(~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1)
2023-04-02 15:50:01 +0200 <liskin> we didn't even know how we do the dev version bumps
2023-04-02 15:50:06 +0200 <liskin> I'll need to rethink this
2023-04-02 15:52:45 +0200 <geekosaur> thyriaen_, you wanted mod-shift-space
2023-04-02 15:53:07 +0200 <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
2023-04-02 15:54:59 +0200 <thyriaen_> come on
2023-04-02 15:55:10 +0200 <thyriaen_> i just updated to fedora 38 to get 0.17.1
2023-04-02 15:55:30 +0200 <thyriaen_> and now you are telling me i have to struggle again to be behind in versions probably missing stuff again
2023-04-02 15:55:46 +0200 <mc47[m]> You're not missing anything
2023-04-02 15:55:49 +0200 <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
2023-04-02 15:55:56 +0200 <thyriaen_> perfect
2023-04-02 15:56:05 +0200 <thyriaen_> i think my bug report worked
2023-04-02 15:56:16 +0200 <thyriaen_> that they included 0.17.1 in this release :p
2023-04-02 16:02:14 +0200 <liskin> oh, is fedora the last distro that still packages reasonably up-to-date xmonad in a reasonably-usable fashion?
2023-04-02 16:02:47 +0200 <liskin> (I keep forgetting the BSDs, I'll see myself out :-))
2023-04-02 16:03:31 +0200 <thyriaen_> liskin, it is the reason why i moved to fedora, yes
2023-04-02 16:11:03 +0200 <xmonadtrack> New branch created: pull/446 (1 commit) https://github.com/xmonad/xmonad/pull/446
2023-04-02 16:16:06 +0200 <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.
2023-04-02 16:16:55 +0200 <geekosaur> and every release starts with a branch from master, after which only bugfixes and release documentation are cherrypicked.
2023-04-02 16:18:19 +0200 <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)
2023-04-02 16:18:56 +0200 <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)
2023-04-02 16:19:32 +0200 <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
2023-04-02 16:20:11 +0200 <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)
2023-04-02 16:23:01 +0200 <geekosaur> you do that on master and cherrypick it, as with bugfixes, so they should still be visible?
2023-04-02 16:25:42 +0200 <geekosaur> there are also other ways to do this; I'm just not as aware of them because I'm most involved with DCSS
2023-04-02 18:01:11 +0200liskin[m](~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
2023-04-02 18:37:20 +0200chomwitt(~chomwitt@2a02:587:7a16:e500:1ac0:4dff:fedb:a3f1) (Ping timeout: 265 seconds)
2023-04-02 18:40:39 +0200chomwitt(~chomwitt@2a02:587:7a16:e500:1ac0:4dff:fedb:a3f1)
2023-04-02 18:42:31 +0200horzion(~horzion@ProtonDB/horzion)
2023-04-02 18:46:59 +0200 <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
2023-04-02 18:47:12 +0200liskin[m](~liskinmat@2001:470:69fc:105::768)
2023-04-02 18:47:23 +0200 <MrElendig> use networkmanager, be happy
2023-04-02 18:47:53 +0200 <MrElendig> it works independently of X
2023-04-02 18:48:08 +0200 <horzion> i do use networkmanager
2023-04-02 18:48:38 +0200 <MrElendig> do you have polkit?
2023-04-02 18:48:49 +0200 <horzion> yes
2023-04-02 18:49:19 +0200 <MrElendig> shouldn't be asking for any password then if you tell it to remember the credentials
2023-04-02 18:49:40 +0200 <horzion> i have the feeling that kdewallet does something to prevent this from working
2023-04-02 18:50:20 +0200 <MrElendig> not really
2023-04-02 18:51:11 +0200 <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
2023-04-02 18:52:00 +0200 <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
2023-04-02 18:52:09 +0200 <horzion> i see
2023-04-02 18:52:11 +0200 <horzion> will try
2023-04-02 18:52:49 +0200 <MrElendig> hmm, option is called "All users may connect to this network" or similar depending on which frontend you are using
2023-04-02 18:52:59 +0200 <horzion> qt, and yeah found it
2023-04-02 18:53:01 +0200 <horzion> will try now
2023-04-02 18:53:06 +0200 <MrElendig> if you want to unlock kwallet on login, you can do that using pam
2023-04-02 18:53:31 +0200 <MrElendig> https://wiki.archlinux.org/title/KDE_Wallet#Configure_PAM or similar for your distro
2023-04-02 18:55:36 +0200horzion(~horzion@ProtonDB/horzion) (Remote host closed the connection)
2023-04-02 18:56:57 +0200horzion(~horzion@ProtonDB/horzion)
2023-04-02 18:57:03 +0200 <horzion> worked like a charm
2023-04-02 18:57:44 +0200 <MrElendig> downside using the shared connection is of course that the credentials are in plain, but they are not world readable
2023-04-02 18:57:44 +0200 <horzion> was my main issue for now, since i couldnt open firefox to search for stuff i wanna change
2023-04-02 18:57:53 +0200 <horzion> aye
2023-04-02 18:58:04 +0200 <MrElendig> firefox should work fine in xmonad
2023-04-02 18:58:18 +0200 <horzion> it does, but it cant connect to anything if there is no network connection
2023-04-02 18:58:28 +0200 <MrElendig> nmcli connect ...
2023-04-02 18:58:45 +0200 <MrElendig> connection*
2023-04-02 18:59:03 +0200 <horzion> yeah, but i dont know that out of my head :P
2023-04-02 18:59:16 +0200 <horzion> it works now, so thats all that matters
2023-04-02 18:59:17 +0200 <MrElendig> it has pretty good docs and --help
2023-04-02 18:59:27 +0200 <MrElendig> there is also nmtui
2023-04-02 18:59:51 +0200 <horzion> last time i used network via cli, i had an aneurism. there is stuff i rather do with gui, ya know
2023-04-02 19:00:10 +0200 <horzion> but i appreciate your help and suggestions
2023-04-02 19:00:25 +0200 <horzion> onto getting xmobar and gridselect working
2023-04-02 19:00:28 +0200 <MrElendig> nmtui is almost gui :)
2023-04-02 19:00:33 +0200 <horzion> hm
2023-04-02 19:01:36 +0200thyriaen_(~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1) (Quit: Leaving)
2023-04-02 19:25:24 +0200stellacy(~stellacy@gateway/tor-sasl/stellacy) (Remote host closed the connection)
2023-04-02 19:28:50 +0200stellacy(~stellacy@gateway/tor-sasl/stellacy)
2023-04-02 19:58:56 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 248 seconds)
2023-04-02 20:14:58 +0200stellacy(~stellacy@gateway/tor-sasl/stellacy) (Remote host closed the connection)
2023-04-02 20:15:16 +0200stellacy(~stellacy@gateway/tor-sasl/stellacy)
2023-04-02 21:01:01 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-04-02 21:25:18 +0200horzion(~horzion@ProtonDB/horzion) (Quit: Off praying to the Omnissiah)
2023-04-02 21:36:25 +0200sagax(~sagax_nb@user/sagax)
2023-04-02 22:01:28 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 252 seconds)
2023-04-02 22:02:13 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-04-02 22:27:11 +0200sagax(~sagax_nb@user/sagax) (Remote host closed the connection)