2024/07/06

Newest at the top

2024-07-06 23:58:45 +0200dysthesis(~dysthesis@user/dysthesis)
2024-07-06 21:28:35 +0200L29Ah(~L29Ah@wikipedia/L29Ah)
2024-07-06 21:22:10 +0200L29Ah(~L29Ah@wikipedia/L29Ah) (Ping timeout: 264 seconds)
2024-07-06 19:49:00 +0200L29Ah(~L29Ah@wikipedia/L29Ah)
2024-07-06 19:22:19 +0200L29Ah(~L29Ah@wikipedia/L29Ah) ()
2024-07-06 16:06:51 +0200vrs(~vrs@user/vrs)
2024-07-06 16:05:56 +0200vrs(~vrs@user/vrs) (Remote host closed the connection)
2024-07-06 13:36:02 +0200dysthesis(~dysthesis@user/dysthesis) (Ping timeout: 260 seconds)
2024-07-06 11:41:58 +0200L29Ah(~L29Ah@wikipedia/L29Ah)
2024-07-06 11:05:01 +0200L29Ah(~L29Ah@wikipedia/L29Ah) (Read error: Connection reset by peer)
2024-07-06 10:54:29 +0200dysthesis(~dysthesis@user/dysthesis)
2024-07-06 10:00:10 +0200catman(~catman@user/catman)
2024-07-06 09:58:22 +0200catman(~catman@user/catman) (Ping timeout: 268 seconds)
2024-07-06 07:50:00 +0200weitcis(~quassel@syn-076-082-169-160.res.spectrum.com)
2024-07-06 07:48:47 +0200weitcis(~quassel@syn-076-082-169-160.res.spectrum.com) (Remote host closed the connection)
2024-07-06 06:59:45 +0200ghormoon(~ghormoon@ghorland.net)
2024-07-06 06:29:39 +0200ghormoon(~ghormoon@ghorland.net) (Ping timeout: 264 seconds)
2024-07-06 04:58:30 +0200dysthesis(~dysthesis@user/dysthesis) (Ping timeout: 260 seconds)
2024-07-06 04:40:03 +0200 <haskellbridge> <iqubic (she/her)> It ends up looking like this now: https://imgur.com/463TCvj
2024-07-06 04:38:59 +0200 <haskellbridge> <iqubic (she/her)> Basically I'm telling XMonad to run a command like "polybar-msg action "#layout.send.Tall"" and I have Polybar configured to respond to these IPC messages and update the layout for me.
2024-07-06 04:38:56 +0200td_(~td@i53870914.versanet.de)
2024-07-06 04:37:27 +0200td_(~td@i53870914.versanet.de) (Ping timeout: 264 seconds)
2024-07-06 04:37:20 +0200 <haskellbridge> <iqubic (she/her)> I could use spawnPID when I spawn multiple Polybars and then use ExtensibleState to track which monitor has which Polybar on it, and then I can specifically tell that one Polybar to update. But I only ever use one monitor, so I don't care to do that right now.
2024-07-06 04:35:03 +0200 <haskellbridge> <iqubic (she/her)> I actually have this comment in my XMonad config: "-- NOTE: Only works on single headed systems"
2024-07-06 04:34:10 +0200 <haskellbridge> <iqubic (she/her)> Oh... I see. I only use a single headed set up.
2024-07-06 04:33:35 +0200 <geekosaur> if a workspace is visible on another monitor, W.view will focus it where it is and W.greedyView will swap it to the default monitor
2024-07-06 04:32:34 +0200 <haskellbridge> <iqubic (she/her)> What the difference between "W.view" and "W.greedyView"?
2024-07-06 04:31:34 +0200 <geekosaur> or easier, just extend `workspaces` with the extra workspaces, since the default keybindings will only bind to the first 9 workspaces listed
2024-07-06 04:31:24 +0200 <haskellbridge> <iqubic (she/her)> Right... and if you don't actually want to view the workspace right after it's been added there's also addHiddenWorkspace and appendHiddenWorkspace
2024-07-06 04:30:49 +0200 <geekosaur> and the workspace target of `W.shift` as used in `manageHook` has to exist already, so you need to create them in `startupHook`
2024-07-06 04:30:01 +0200 <geekosaur> yes, but part of the question was how to bind keys to switch tot hem later
2024-07-06 04:29:39 +0200 <haskellbridge> <iqubic (she/her)> appendWorkspace and addWorkspace both run a W.view for the newly added workspace.
2024-07-06 04:29:39 +0200 <geekosaur> (`selectWorkspace` uses XMonad.Prompt to get the workspace to switch to)
2024-07-06 04:29:11 +0200 <geekosaur> you could then go to it by name with selectWorkspace or with `windows (W.view workspaceName)`
2024-07-06 04:29:03 +0200 <haskellbridge> <iqubic (she/her)> They might also need to add a view command to the startup hook to switch back to the first workspace, otherwise they will be viewing one of the new workspaces they just added.
2024-07-06 04:26:16 +0200 <geekosaur> https://github.com/geekosaur/xmonad.hs/blob/hilfy-2023/xmonad.hs#L144 https://github.com/geekosaur/xmonad.hs/blob/hilfy-2023/xmonad.hs#L63-L83
2024-07-06 04:25:59 +0200 <haskellbridge> <iqubic (she/her)> I'm not sure what the difference between view and greedyView is, but I'm sure others can explain that.
2024-07-06 04:25:40 +0200 <geekosaur> iqubic: it's the `workspaces` field in `XConfig`
2024-07-06 04:25:24 +0200 <haskellbridge> <iqubic (she/her)> Yeah... that's the smarter way to do it.
2024-07-06 04:25:08 +0200 <geekosaur> Leave off rebinding the normal workspace keys and use appendWorkspace in the startupHook to add your special workspaces
2024-07-06 04:25:00 +0200 <haskellbridge> <iqubic (she/her)> geekosaur: How does XMonad know what the default set of workspace tags should be? Is that defined somewhere?
2024-07-06 04:24:05 +0200 <geekosaur> Maybe you want https://hackage.haskell.org/package/xmonad-contrib-0.18.0/docs/XMonad-Actions-DynamicWorkspaces.html ?
2024-07-06 04:22:54 +0200 <haskellbridge> <iqubic (she/her)> geekosaur: Can you help out here?
2024-07-06 04:22:38 +0200 <haskellbridge> <iqubic (she/her)> I think you can define workspaces 0-9 and then those extra workspaces. And then you just have the standard Mod + Number to run view / greedyView and Mod + Shift + Number to run do shift with the current window. And then you can just only have longer keybindings for viewing / greedyViewing these special workspaces. I'm not sure on the details, but I think others can help you here.
2024-07-06 04:15:26 +0200 <haskellbridge> ... long message truncated: https://kf8nh.com/_matrix/media/v3/download/kf8nh.com/OJXmmwBgqTIThxxbgRGmaKAM (14 lines)
2024-07-06 04:15:24 +0200 <haskellbridge> <柱間 (@hashirama:hashi.sbs)> geekosaur: i was reading it, and basically it hides from the statusbar, but i have no statusbar so it's not needed
2024-07-06 01:30:12 +0200ml|(~ml|@user/ml/x-5298235)
2024-07-06 01:16:48 +0200ml|(~ml|@user/ml/x-5298235) (Ping timeout: 255 seconds)
2024-07-06 01:12:23 +0200ml|(~ml|@user/ml/x-5298235)
2024-07-06 00:58:12 +0200ml|(~ml|@user/ml/x-5298235) (Ping timeout: 252 seconds)