| 2022-02-05 00:21:20 +0100 | catman | (~catman@user/catman) (Read error: Connection reset by peer) |
| 2022-02-05 00:27:08 +0100 | catman | (~catman@user/catman) |
| 2022-02-05 00:54:06 +0100 | Czernobog | (~Czernobog@user/czernobog) (Quit: ZNC 1.8.2 - https://znc.in) |
| 2022-02-05 01:25:35 +0100 | Czernobog | (~Czernobog@user/czernobog) |
| 2022-02-05 02:19:56 +0100 | seschwar | (~seschwar@user/seschwar) (Quit: :wq) |
| 2022-02-05 03:43:18 +0100 | catman | (~catman@user/catman) (Read error: Connection reset by peer) |
| 2022-02-05 03:47:28 +0100 | catman | (~catman@user/catman) |
| 2022-02-05 04:04:49 +0100 | banc | (banc@gateway/vpn/airvpn/banc) (Ping timeout: 256 seconds) |
| 2022-02-05 04:14:10 +0100 | mojavve | (~anima@99-70-101-130.lightspeed.rcsntx.sbcglobal.net) |
| 2022-02-05 04:20:31 +0100 | srk | (~sorki@user/srk) (Remote host closed the connection) |
| 2022-02-05 04:20:49 +0100 | srk | (~sorki@user/srk) |
| 2022-02-05 04:22:20 +0100 | <jakeStateless-Fa> | Could someone explain to me what `wrs` is supposed to be in relation to `modifiedLayout`s? In specific - `X.L.Magnifier`s use of it. |
| 2022-02-05 04:22:44 +0100 | banc | (banc@gateway/vpn/airvpn/banc) |
| 2022-02-05 04:33:55 +0100 | mojavve | (~anima@99-70-101-130.lightspeed.rcsntx.sbcglobal.net) (Quit: Lost terminal) |
| 2022-02-05 04:36:53 +0100 | steve__ | (~steve@ool-182c2b80.dyn.optonline.net) (Ping timeout: 256 seconds) |
| 2022-02-05 04:41:25 +0100 | td_ | (~td@muedsl-82-207-238-085.citykom.de) (Ping timeout: 256 seconds) |
| 2022-02-05 04:42:52 +0100 | td_ | (~td@muedsl-82-207-238-241.citykom.de) |
| 2022-02-05 05:05:34 +0100 | <jakeStateless-Fa> | nvm, not relevant, figured stuff out! |
| 2022-02-05 05:25:35 +0100 | thunderrd | (~thunderrd@183.182.111.73) (Remote host closed the connection) |
| 2022-02-05 05:36:31 +0100 | thunderrd | (~thunderrd@183.182.111.73) |
| 2022-02-05 05:37:56 +0100 | thunderrd | (~thunderrd@183.182.111.73) (Remote host closed the connection) |
| 2022-02-05 05:38:25 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 256 seconds) |
| 2022-02-05 05:48:02 +0100 | thunderrd | (~thunderrd@183.182.111.73) |
| 2022-02-05 05:50:06 +0100 | thunderrd | (~thunderrd@183.182.111.73) (Remote host closed the connection) |
| 2022-02-05 05:50:38 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-02-05 05:51:04 +0100 | thunderrd | (~thunderrd@183.182.111.73) |
| 2022-02-05 05:55:57 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 240 seconds) |
| 2022-02-05 06:01:31 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-02-05 06:44:08 +0100 | thunderrd | (~thunderrd@183.182.111.73) (Remote host closed the connection) |
| 2022-02-05 07:05:32 +0100 | Guest77 | (~Guest77@47.153.196.157) |
| 2022-02-05 07:06:27 +0100 | <Guest77> | Hi I am using fedora and I have compiled xmobar and xmonad/xmoad-contrib from source: I have the following flags built: flags: |
| 2022-02-05 07:06:27 +0100 | <Guest77> | xmobar: |
| 2022-02-05 07:06:28 +0100 | <Guest77> | with_alsa: false |
| 2022-02-05 07:06:28 +0100 | <Guest77> | with_dbus: true |
| 2022-02-05 07:06:29 +0100 | <Guest77> | with_threaded: true |
| 2022-02-05 07:06:29 +0100 | <Guest77> | with_utf8: true |
| 2022-02-05 07:06:30 +0100 | <Guest77> | with_xft: true |
| 2022-02-05 07:06:31 +0100 | <Guest77> | with_xpm: true |
| 2022-02-05 07:06:31 +0100 | <Guest77> | with_weather: true |
| 2022-02-05 07:06:31 +0100 | <Guest77> | with_datezone: true |
| 2022-02-05 07:06:32 +0100 | <Guest77> | with_mpris: true |
| 2022-02-05 07:06:32 +0100 | <Guest77> | However, when I try to run xmobar I get an error saying xft is not enabled...? |
| 2022-02-05 07:06:44 +0100 | <Guest77> | ^^ that is in my stack.yaml |
| 2022-02-05 07:07:15 +0100 | <Guest77> | also does anyone now how to get trayer working on fedora, I built from source, however it only seems to run in a grey box |
| 2022-02-05 07:10:33 +0100 | <Guest77> | "Warning: Xmobar must be built with the with_xft flag to support font 'xft:iosevka:weight=bold:pixelsize=14:antialias=true:hinting=true.' Falling back on default." However, it is built with the xft flag i alos have libXft-devel installed |
| 2022-02-05 07:12:38 +0100 | Guest7749 | (~Guest77@47.153.196.157) |
| 2022-02-05 07:26:23 +0100 | <jakeStateless-Fa> | <jakeStateless-Fa> "Could someone explain to me what..." <- Uh, actually, turns out I still need that explanation, how do I know which window's focused within this context? |
| 2022-02-05 07:27:17 +0100 | <jakeStateless-Fa> | I was just pullilng the first item, and that's just a toggle for if the master window is fullscreened, make everything that way... |
| 2022-02-05 07:27:28 +0100 | <jakeStateless-Fa> | s/pullilng/pulling/ |
| 2022-02-05 07:27:54 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection) |
| 2022-02-05 07:29:56 +0100 | <jakeStateless-Fa> | which's pretty much useless |
| 2022-02-05 07:35:31 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-02-05 07:39:18 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection) |
| 2022-02-05 07:41:30 +0100 | Guest7749 | (~Guest77@47.153.196.157) (Quit: Client closed) |
| 2022-02-05 07:41:30 +0100 | Guest77 | (~Guest77@47.153.196.157) (Quit: Client closed) |
| 2022-02-05 08:00:58 +0100 | thunderrd | (~thunderrd@183.182.111.73) |
| 2022-02-05 08:05:52 +0100 | Czernobog | (~Czernobog@user/czernobog) (Quit: ZNC 1.8.2 - https://znc.in) |
| 2022-02-05 08:12:32 +0100 | Guest7768 | (~Guest77@47.153.196.157) |
| 2022-02-05 08:12:48 +0100 | <Guest7768> | Hi I have xprop installed but it does not seem to work on fedora for trayer? as in it is not expanding, this works great on arch, any ideas? |
| 2022-02-05 08:13:01 +0100 | <Guest7768> | script gives no errors and makes xpm |
| 2022-02-05 08:15:05 +0100 | <Solid> | jakeStateless-Fa: the underlying layout (which should be there, since we're talking layout modifiers) arranges the windows on the screen on some way; i.e., it assigns windows to "rectangles" |
| 2022-02-05 08:15:32 +0100 | <Solid> | If you want to filter for some condition you'll need the current stack (which is why `redoLayout` gets that as well) |
| 2022-02-05 08:15:54 +0100 | <Guest7768> | sorry i figured out xprop issue, my issue is my flags in my stack.yaml are not being followed |
| 2022-02-05 08:16:15 +0100 | <Solid> | see e.g. how applyMagnifier is written; it basically filters the list of (window, rectangle) pairs for the focused window, which we get from the stack |
| 2022-02-05 08:16:40 +0100 | <Guest7768> | https://pastebin.com/7z0irW23 anyone have any idea why my xmobar flags won't compile properly? |
| 2022-02-05 08:16:42 +0100 | <Solid> | Guest7768: how are you building xmobar? do you have a repo up somewhere? |
| 2022-02-05 08:18:00 +0100 | <Guest7768> | solid from source, I'm pulling my files from arch to try fedora out, it works if i do stack install --flag xmobar:with_xft but the stack.yaml is not followed currently |
| 2022-02-05 08:18:45 +0100 | <Guest7768> | or the stack.yaml is from my arch system sorry, xmobar is from jaor source |
| 2022-02-05 08:19:02 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-02-05 08:19:21 +0100 | <Guest7768> | it seems to ignore the xft rule |
| 2022-02-05 08:20:00 +0100 | Rue | (~rue@2001-b011-1000-1c39-cdcc-c9c1-11c3-6370.dynamic-ip6.hinet.net) |
| 2022-02-05 08:20:16 +0100 | <Solid> | ` |
| 2022-02-05 08:20:56 +0100 | <Solid> | mh I guess without libxft you would rather get errors at build time |
| 2022-02-05 08:21:10 +0100 | <Solid> | but i guess see if you have that installed in either case |
| 2022-02-05 08:21:51 +0100 | <Guest7768> | yea no errors. |
| 2022-02-05 08:21:51 +0100 | <Guest7768> | I have it installed and it works properly if I run stack install --flag xmobar:with_xft |
| 2022-02-05 08:21:52 +0100 | <Guest7768> | However, it does not work with the arguments in stack.yaml |
| 2022-02-05 08:22:22 +0100 | <Guest7768> | im at a loss lmao solid I appreciate you taking a look |
| 2022-02-05 08:23:44 +0100 | <Solid> | what executable actually gets build if you run stack install? seems like you have your xmonad _and_ xmobar config in a single repo? |
| 2022-02-05 08:25:05 +0100 | <Guest7768> | I have xmobar-git, xmonad-contrib-git, and xmonad-git all in a 'xmonad' folder. The stack.yaml resides in that folder along with xmonad.hs .xmobarrc |
| 2022-02-05 08:25:39 +0100 | <Guest7768> | its funny because I keep referencing my arch system and they are identical |
| 2022-02-05 08:26:15 +0100 | <Guest7768> | im going to try deleting stack folders and rebuilding hang on |
| 2022-02-05 08:27:27 +0100 | <Guest7768> | nada |
| 2022-02-05 08:30:37 +0100 | <Guest7768> | okay interesting, the flags actually have no effect in my stack.yaml.... |
| 2022-02-05 08:30:55 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 256 seconds) |
| 2022-02-05 08:37:34 +0100 | <Guest7768> | solid im a dofus so dont even worry about it |
| 2022-02-05 08:37:37 +0100 | <Guest7768> | I figured it out |
| 2022-02-05 08:38:01 +0100 | <Solid> | Now I'm curious :) |
| 2022-02-05 08:38:12 +0100 | <Guest7768> | my dumbass was building w/out install |
| 2022-02-05 08:38:19 +0100 | <Guest7768> | so i was never refreshing my bin |
| 2022-02-05 08:38:22 +0100 | <Solid> | hah |
| 2022-02-05 08:44:56 +0100 | <Guest7768> | sick looks like I can move to fedora for my dev computer now, i was having issues with trayer but got that working with xmobar so im all set |
| 2022-02-05 08:52:16 +0100 | <Solid> | \o/ |
| 2022-02-05 08:53:18 +0100 | Guest7768 | (~Guest77@47.153.196.157) (Quit: Client closed) |
| 2022-02-05 09:12:51 +0100 | Natch | (~natch@c-4db8e255.014-297-73746f25.bbcust.telenor.se) |
| 2022-02-05 09:31:33 +0100 | catman | (~catman@user/catman) (Ping timeout: 256 seconds) |
| 2022-02-05 09:33:33 +0100 | Rue | (~rue@2001-b011-1000-1c39-cdcc-c9c1-11c3-6370.dynamic-ip6.hinet.net) (Quit: WeeChat 3.4) |
| 2022-02-05 09:33:54 +0100 | Rue | (~rue@2001-b011-1000-1c39-cdcc-c9c1-11c3-6370.dynamic-ip6.hinet.net) |
| 2022-02-05 10:17:39 +0100 | geekosaur | (~geekosaur@xmonad/geekosaur) (Killed (NickServ (GHOST command used by allbery_b))) |
| 2022-02-05 10:17:39 +0100 | allbery_b | (~geekosaur@xmonad/geekosaur) |
| 2022-02-05 10:17:42 +0100 | allbery_b | geekosaur |
| 2022-02-05 10:41:05 +0100 | mc47 | (~mc47@xmonad/TheMC47) |
| 2022-02-05 10:51:20 +0100 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2022-02-05 11:15:24 +0100 | seschwar | (~seschwar@user/seschwar) |
| 2022-02-05 11:16:40 +0100 | chomwitt | (~chomwitt@2a02:587:dc07:dd00:12c3:7bff:fe6d:d374) (Remote host closed the connection) |
| 2022-02-05 11:32:53 +0100 | steve__ | (~steve@ool-182c2b80.dyn.optonline.net) |
| 2022-02-05 11:52:38 +0100 | mc47 | (~mc47@xmonad/TheMC47) |
| 2022-02-05 11:54:07 +0100 | <mc47> | Solid, liskin: I probably won't resolve the issues in my PR any time soon (exams and last week at my job) |
| 2022-02-05 11:54:27 +0100 | <mc47> | (well, there's always the possibility that I get bored from studying and do that anyway) |
| 2022-02-05 12:06:49 +0100 | geekosaur | (~geekosaur@xmonad/geekosaur) (Remote host closed the connection) |
| 2022-02-05 12:08:29 +0100 | geekosaur | (~geekosaur@xmonad/geekosaur) |
| 2022-02-05 12:22:22 +0100 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2022-02-05 13:41:03 +0100 | mc47 | (~mc47@xmonad/TheMC47) |
| 2022-02-05 13:57:44 +0100 | <Solid> | mc47: ah that's totally fine, just pick it up again when you have the time (or one of us will!) |
| 2022-02-05 13:58:02 +0100 | <Solid> | good luck on the exams though :) |
| 2022-02-05 14:02:04 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-02-05 14:09:05 +0100 | <mc47> | thank you! |
| 2022-02-05 14:35:32 +0100 | red-snail | (~snail@static.151.210.203.116.clients.your-server.de) (Leaving) |
| 2022-02-05 14:48:22 +0100 | Czernobog | (~Czernobog@user/czernobog) |
| 2022-02-05 15:21:33 +0100 | catman | (~catman@user/catman) |
| 2022-02-05 15:24:59 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection) |
| 2022-02-05 15:41:48 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-02-05 17:05:49 +0100 | noex | (~null@user/noex) (Quit: :q!) |
| 2022-02-05 17:48:49 +0100 | geekosaur | (~geekosaur@xmonad/geekosaur) (Remote host closed the connection) |
| 2022-02-05 17:50:35 +0100 | geekosaur | (~geekosaur@xmonad/geekosaur) |
| 2022-02-05 17:56:18 +0100 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2022-02-05 17:56:37 +0100 | Rue | (~rue@2001-b011-1000-1c39-cdcc-c9c1-11c3-6370.dynamic-ip6.hinet.net) (WeeChat 3.4) |
| 2022-02-05 18:05:55 +0100 | noex | (~null@user/noex) |
| 2022-02-05 18:36:21 +0100 | catman | (~catman@user/catman) (Read error: Connection reset by peer) |
| 2022-02-05 18:39:24 +0100 | <noex> | having a strange problem. i changed some things around and the keys to swap physical displays are backwards. mod+e and mod+w. in nvidia settings, they are represented correctly. i made some configuration changes that probably broke this, but swapping 'e' and 'w' in my config seemingly doesn't change anything. |
| 2022-02-05 18:45:28 +0100 | <noex> | https://dpaste.com/3FFG9MLZM not sure if config issue |
| 2022-02-05 19:08:21 +0100 | <fizzie> | noex: `xWorkspaceKeys` appears entirely unused in the configuration. |
| 2022-02-05 19:08:42 +0100 | <fizzie> | Or else my find-on-page is acting up. But the only match is the definition. |
| 2022-02-05 19:09:34 +0100 | <fizzie> | You've got ... `removeKeys` xKnoKeys `additionalKeys` xKeys ... in there, but no mention of xWorkspaceKeys. Maybe add ++ xWorkspaceKeys at the end of xKeys, or something. |
| 2022-02-05 19:10:07 +0100 | <noex> | oh, so it just must inherit this behavior automatically then |
| 2022-02-05 19:10:33 +0100 | <fizzie> | Yes, mod-{w,e,r} are in the default keybindings. |
| 2022-02-05 19:10:54 +0100 | <noex> | so i can just delete this I guess |
| 2022-02-05 19:11:04 +0100 | <noex> | because it does nothing |
| 2022-02-05 19:11:15 +0100 | <fizzie> | I thought you wanted to swap w/e though. |
| 2022-02-05 19:11:42 +0100 | <noex> | i could try that, but I feel like that's a band-aid |
| 2022-02-05 19:12:23 +0100 | <fizzie> | Well, yes. There's also https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Actions-PhysicalScreens.html if you want to have versions of those keybindings that depend on the screens' actual locations, making them independent of screen ordering. |
| 2022-02-05 19:12:37 +0100 | banc | (banc@gateway/vpn/airvpn/banc) (Ping timeout: 240 seconds) |
| 2022-02-05 19:12:41 +0100 | <noex> | it's always worked like that though until this week |
| 2022-02-05 19:13:38 +0100 | <fizzie> | The "raw" ScreenID numbering *is* arbitrary. I think (at least on my system) the one set via xrandr as `--primary` has been consistently 0, though. |
| 2022-02-05 19:13:43 +0100 | catman | (~catman@user/catman) |
| 2022-02-05 19:13:48 +0100 | <noex> | they have always exactly mimiced the physical locations of the displays |
| 2022-02-05 19:14:47 +0100 | <noex> | and it's one scree |
| 2022-02-05 19:14:50 +0100 | <noex> | *screen |
| 2022-02-05 19:14:57 +0100 | <noex> | just Screen 0 |
| 2022-02-05 19:18:19 +0100 | <fizzie> | The ScreenId in that context isn't referring to *X* screens. Surely you must have more than one physical screen if you're concerned about those keybindings. |
| 2022-02-05 19:18:41 +0100 | <noex> | yeah just two |
| 2022-02-05 19:19:05 +0100 | <noex> | interestingly i did a diff of my old xorg.conf and there's no clues. the only differences should have nothing to do with screen ordering. |
| 2022-02-05 19:19:20 +0100 | <noex> | brightness control, color depth, and triple buffering |
| 2022-02-05 19:20:41 +0100 | <fizzie> | There's definitely no built-in guarantee about the numbering used there being consistent with the positions of the outputs. At least for me, like I said the "primary" screen seems to always be 0, and I have that as the rightmost one (I keep an extra bottom bar on it). |
| 2022-02-05 19:21:09 +0100 | <noex> | that might be the problem then. maybe it's the "primary screen" that affects it |
| 2022-02-05 19:21:42 +0100 | <noex> | that's interesting that it was correct for so long |
| 2022-02-05 19:22:14 +0100 | <noex> | if the primary screen is static, maybe it does make sense to hardcode and just swap the order |
| 2022-02-05 19:22:33 +0100 | <noex> | i'm almost positive the primary screen was wrong before |
| 2022-02-05 19:25:59 +0100 | <noex> | that worked. thanks fizzie for finding that dead code lol |
| 2022-02-05 19:26:32 +0100 | <noex> | i was trying to figure out how that worked. didn't make sense to me how it could function the way it was written lol |
| 2022-02-05 19:50:19 +0100 | mc47 | (~mc47@xmonad/TheMC47) |
| 2022-02-05 20:12:59 +0100 | <jakeStateless-Fa> | Solid: I've not been able to figure out how to proceed from here: https://0bin.net/paste/gH6xj0hM#sf5SrSuZMKS1uYNrrH6OClaYE50Gi+TCxlnTYIri8Pv |
| 2022-02-05 20:17:03 +0100 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Remote host closed the connection) |
| 2022-02-05 20:19:03 +0100 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2022-02-05 20:19:09 +0100 | <geekosaur> | you have `getFocus` defined as producing `Maybe Window` when to use `withWindowSet` it has to be X (Maybe Window) |
| 2022-02-05 20:22:00 +0100 | <jakeStateless-Fa> | Evidently it's wrong, but what would I do to get it to produce a `Maybe Window`? |
| 2022-02-05 20:22:28 +0100 | <geekosaur> | you can't, if you want to access the WindowSet |
| 2022-02-05 20:22:31 +0100 | <jakeStateless-Fa> | (the focused one - in specific) |
| 2022-02-05 20:25:33 +0100 | <geekosaur> | and then onlyFullScreen is seeing the `>>=` and `return` and trying to figure out how to be an action, but the only Monad it can be an action in is `Maybe` |
| 2022-02-05 20:26:48 +0100 | <geekosaur> | I suggest going through http://www.vex.net/~trebla/haskell/IO.xhtml |
| 2022-02-05 20:27:19 +0100 | <geekosaur> | we use X instead of IO (so it can carry around the config, WindowSet, and various other things) but it's still IO underneath |
| 2022-02-05 20:27:34 +0100 | <jakeStateless-Fa> | OK then, how would I go about running a filter like `applyMagnifier` does, but setting it to use the tag system present in `onlyFullscreen`? |
| 2022-02-05 20:28:51 +0100 | <geekosaur> | look at line 262, as I said, its result type is in the X monad, so it can get at the focused window |
| 2022-02-05 20:28:58 +0100 | <geekosaur> | yours must also be in the X monad |
| 2022-02-05 20:32:44 +0100 | <geekosaur> | then, since onlyFullscreen is in X, line 230 must change to: onlyFullscreen z (applyMagnifier z) r s wrs >>= magnifyAt k |
| 2022-02-05 20:34:59 +0100 | <jakeStateless-Fa> | ah, I see |
| 2022-02-05 20:36:12 +0100 | <jakeStateless-Fa> | I figured something simpler out though, I'd overlooked the `s` variable, that was of type `Stack a`, unlike `wrs` which was of type `[(Window,Rectangle)]`, and therefore I could run `X.Stackset`s `focus` on it. That did the trick |
| 2022-02-05 20:45:25 +0100 | <geekosaur> | I think you still need an X context in onlyFullscreen for hasTag though? |
| 2022-02-05 20:49:15 +0100 | <jakeStateless-Fa> | I believe it's getting passed in through magnifyAt, not 100% sure, but it's compiling and working 🤷. |
| 2022-02-05 21:06:11 +0100 | banc | (banc@gateway/vpn/airvpn/banc) |
| 2022-02-05 21:12:17 +0100 | <jakeStateless-Fa> | https://0bin.net/paste/zMqHfmsm#ZDxF2U8Cfidlxt12ZHvuL9nBnJBmNuptIxq89pawOvK - using this in my loghook causes infinite recursion, boredr flickering, and an unresponsive xmonad (though I can still use the window I was last focused on, and still switch to different vTTYs) |
| 2022-02-05 21:13:38 +0100 | <jakeStateless-Fa> | border* , those messages must trigger the log hook, I'm guessing, how would I go about keeping a small amount of state (a bool) allowing me to prevent the infinite recursion? |
| 2022-02-05 21:13:52 +0100 | <geekosaur> | it's the sendMessage |
| 2022-02-05 21:15:46 +0100 | <geekosaur> | I, uh, don't see why you'd have it say "this is fullscreen, unfullscreen it"/"this is not fullscreen, fullscreen it" unconditionally in a logHook, to be honest |
| 2022-02-05 21:16:16 +0100 | <geekosaur> | isn't the FS tag the state? or do I misunderstand its purpose? |
| 2022-02-05 21:19:34 +0100 | <jakeStateless-Fa> | the FS tag applies to a window, so when that window's focused, it'll fullscreen (magnifier + removal of struts, borders, and spacing) |
| 2022-02-05 21:20:04 +0100 | <jakeStateless-Fa> | you're still allowed to move freely between windows though |
| 2022-02-05 21:20:08 +0100 | <jakeStateless-Fa> | by design |
| 2022-02-05 21:20:27 +0100 | <jakeStateless-Fa> | So, if you switch to a non-fullscreen window right after a fullscreened one, then the struts and spacing will still be gone. |
| 2022-02-05 21:20:49 +0100 | <jakeStateless-Fa> | and vice versa (if you untoggle, or if the prior scenario didn't happen) |
| 2022-02-05 21:21:10 +0100 | <jakeStateless-Fa> | Is there a way for me to query the layout, so I can know when those changes are already applied? |
| 2022-02-05 21:24:51 +0100 | <jakeStateless-Fa> | I could just tie this to a keybind, but if they switch windows via another method, it'll get out of sync. |
| 2022-02-05 21:25:10 +0100 | <jakeStateless-Fa> | or if the window closes / really any focus change |
| 2022-02-05 21:26:36 +0100 | <jakeStateless-Fa> | Ooh, instead of querying for the changes (which may not work for everyone, depending upon their layouts) is there a way I can identify what change occurred? If so, filtering for focus change would be the simplest, and most optimized way to do this. |
| 2022-02-05 21:37:58 +0100 | <geekosaur> | not easily. logHook is executed any time `windows` is and there's no way it can know what e.g. a manageHook did |
| 2022-02-05 21:41:37 +0100 | <geekosaur> | I think there's something that tracks the current workspace and triggers when it changes, but it does so by stuffing its idea of the current workspace in XS and comparing every time the logHook runs |
| 2022-02-05 21:42:20 +0100 | <geekosaur> | conceivably you could handle the focused window the same way; I don't think we provide a way to change the focused window on a non-focused workspace |
| 2022-02-05 22:22:41 +0100 | sogens | (~sogens@pa49-197-132-249.pa.qld.optusnet.com.au) (Quit: WeeChat 3.4) |
| 2022-02-05 22:23:00 +0100 | sogens | (~sogens@pa49-197-132-249.pa.qld.optusnet.com.au) |