2023-01-20 00:07:44 +0100 | rundown | (~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) |
2023-01-20 01:18:46 +0100 | rundown | (~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) (Remote host closed the connection) |
2023-01-20 01:22:25 +0100 | mazte[m] | (~sujammama@2001:470:69fc:105::2:ea4c) |
2023-01-20 01:39:23 +0100 | geekosaur | (~geekosaur@xmonad/geekosaur) (Remote host closed the connection) |
2023-01-20 01:39:50 +0100 | geekosaur | (~geekosaur@xmonad/geekosaur) |
2023-01-20 02:22:20 +0100 | mncheck | (~mncheck@193.224.205.254) (Ping timeout: 260 seconds) |
2023-01-20 03:55:45 +0100 | yaslam | (~yaslam@user/yaslam) |
2023-01-20 04:03:06 +0100 | banc | (banc@gateway/vpn/protonvpn/banc) (Ping timeout: 272 seconds) |
2023-01-20 04:24:26 +0100 | banc | (banc@gateway/vpn/protonvpn/banc) |
2023-01-20 04:53:38 +0100 | td_ | (~td@83.135.9.34) (Ping timeout: 268 seconds) |
2023-01-20 04:55:25 +0100 | td_ | (~td@83.135.9.28) |
2023-01-20 05:24:05 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 246 seconds) |
2023-01-20 05:28:16 +0100 | jrgiacone | (~jrgiacone@172-112-225-143.res.spectrum.com) |
2023-01-20 05:29:05 +0100 | <jrgiacone> | not sure what update was pushed in the last few weeks but my XMonad.Hooks.DynamicBars is failing from time to time now where it does not remove the second bar if I turn my screen on and off a few times creating extra xmobar instances |
2023-01-20 05:37:23 +0100 | <jrgiacone> | sorry not that module |
2023-01-20 05:37:32 +0100 | <jrgiacone> | just using dynamiceasysbs barspawner |
2023-01-20 06:06:55 +0100 | disobey | (~disobey@2401:4900:6156:12f9:ea1b:57d7:db88:856e) |
2023-01-20 06:07:41 +0100 | disobey | (~disobey@2401:4900:6156:12f9:ea1b:57d7:db88:856e) () |
2023-01-20 06:30:25 +0100 | rundown | (~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) |
2023-01-20 06:41:05 +0100 | jrgiacone | (~jrgiacone@172-112-225-143.res.spectrum.com) (Remote host closed the connection) |
2023-01-20 07:25:18 +0100 | <Solid> | I don't think we did anything relating to status bars in the near past |
2023-01-20 07:25:33 +0100 | <Solid> | s/relating/related/ |
2023-01-20 07:39:16 +0100 | rundown | (~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) (Quit: WeeChat 3.0) |
2023-01-20 08:10:29 +0100 | mncheckm | (~mncheck@193.224.205.254) |
2023-01-20 08:57:14 +0100 | tomjaguarpaw | (~tom@li367-225.members.linode.com) (Remote host closed the connection) |
2023-01-20 09:37:32 +0100 | ft | (~ft@p4fc2a257.dip0.t-ipconnect.de) (Quit: leaving) |
2023-01-20 10:21:05 +0100 | <vrs> | well xmobar got an update removing xft support, could be other things that broke there as well |
2023-01-20 10:23:09 +0100 | <HB[m]> | vrs: Oh dang. |
2023-01-20 10:23:33 +0100 | <HB[m]> | Starting with version 0.45 we use cairo/pango as our drawing engine (instead of plain X11/Xft). From a user's point of view, that change should be mostly transparent, except for the facts that it's allowed fixing quite a few bugs and that your font names in your configuration, if you used xft ones, might need to be adapted to Pango's syntax: please see this section of the documentation for all the details. If you're compiling your own xmobar, there's |
2023-01-20 10:23:33 +0100 | <HB[m]> | a new dependency on libpango (see C library dependencies). |
2023-01-20 10:24:04 +0100 | <HB[m]> | * library dependencies). https://codeberg.org/xmobar/xmobar |
2023-01-20 10:24:24 +0100 | <vrs> | "that change should be mostly transparent" except that I had to take sanity damage from the way pango defines fallback fonts |
2023-01-20 10:26:18 +0100 | <vrs> | afaik xmobar dies when you close the pipe it's reading from, but if it's not reading from a pipe then it doesn't notice screen setup change / xmobar restart |
2023-01-20 10:26:37 +0100 | <vrs> | so depending on whether you have an stdinreader set up, the behavior is different |
2023-01-20 10:26:47 +0100 | <vrs> | I don't know what happens to ones that use property logging |
2023-01-20 10:27:59 +0100 | <vrs> | oh jrgiacone left, didn't notice |
2023-01-20 10:35:51 +0100 | <HB[m]> | ` font = "xft:DejaVu Sans Condensed:size=9::antialias=true",` |
2023-01-20 10:35:59 +0100 | <HB[m]> | I wonder what the new sytnax would be |
2023-01-20 10:36:02 +0100 | <HB[m]> | s/sytnax/syntax/ |
2023-01-20 10:36:52 +0100 | HB[m] | sent a haskell code block: https://libera.ems.host/_matrix/media/v3/download/libera.chat/27e65f4b2984723ec8d0cdc5f5e6eedb5709… |
2023-01-20 10:39:33 +0100 | <vrs> | probably "DejaVu Sans Condensed 9" modulo dpi scaling |
2023-01-20 10:42:43 +0100 | cfricke | (~cfricke@user/cfricke) |
2023-01-20 10:43:46 +0100 | <Solid> | vrs: dynamicSB and such exist exactly for making property-based things aware of these "dynamic" screen changes |
2023-01-20 10:45:44 +0100 | <vrs> | yeah I recently ported to it from dynamicbars |
2023-01-20 10:46:11 +0100 | scardinal | (~supreme@customer-212-237-101-39.ip4.gigabit.dk) (Quit: leaving) |
2023-01-20 10:47:23 +0100 | <vrs> | was nontrivial, multiPP did some magic with the stackset so that loggers didn't need to be aware of what the current screen was, but dynamicSBs does not, so I had to update all my loggers |
2023-01-20 10:47:50 +0100 | mc47 | (~mc47@xmonad/TheMC47) |
2023-01-20 10:48:11 +0100 | scardinal | (~supreme@customer-212-237-101-39.ip4.gigabit.dk) |
2023-01-20 10:48:13 +0100 | <vrs> | (still use stdinreader though - it's never broken for me) |
2023-01-20 11:31:48 +0100 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
2023-01-20 12:39:20 +0100 | rundown | (~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) |
2023-01-20 12:40:25 +0100 | rundown | (~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) (Client Quit) |
2023-01-20 13:40:38 +0100 | <yaslam> | jrgiacone: Happens to me aswell with dynamicSBs but not every time |
2023-01-20 14:27:03 +0100 | jamesreid[m] | (~jamesreid@2001:470:69fc:105::2:f94b) |
2023-01-20 14:47:16 +0100 | cfricke | (~cfricke@user/cfricke) (Quit: WeeChat 3.7.1) |
2023-01-20 16:10:39 +0100 | ft | (~ft@p4fc2a257.dip0.t-ipconnect.de) |
2023-01-20 16:17:38 +0100 | <yaslam> | Hello everyone, why does `docks` from X.H.ManageDocks not work with trayer when more than one screen is active? I have an external monitor connected and the system tray is on my laptops builtin screen, when the external monitor is connected, trayer is below windows, but when the external monitor is disconnected, trayer is visible above windows like it should be, xmobar on the laptops screen is visible above windows like it should be no matter what, here's my |
2023-01-20 16:17:39 +0100 | <yaslam> | full config: http://ix.io/4lL1 |
2023-01-20 16:20:21 +0100 | <geekosaur> | `docks` doesn't control that, it just makes sure the window isn't managed like a normal window. https://hackage.haskell.org/package/xmonad-contrib-0.17.1/docs/XMonad-Util-Hacks.html#v:trayerAbov… might be helpful |
2023-01-20 16:20:45 +0100 | <geekosaur> | possibly along with the rescreen hook https://hackage.haskell.org/package/xmonad-contrib-0.17.1/docs/XMonad-Hooks-Rescreen.html |
2023-01-20 16:21:19 +0100 | <geekosaur> | EWMH requires docks/panels/etc. to manage themselves but trayer doesn't do a good job of it |
2023-01-20 16:22:51 +0100 | mncheckm | (~mncheck@193.224.205.254) (Read error: Connection reset by peer) |
2023-01-20 16:23:03 +0100 | <geekosaur> | also, if it's actually the trayer package, see if trayer-srg is packaged; it does a somewhat better job with multiple screens |
2023-01-20 16:23:55 +0100 | <yaslam> | geekosaur: Yeah I'm on Arch Linux and I use trayer-srg. |
2023-01-20 16:24:12 +0100 | <yaslam> | I'll see if I can get it working with the link that you mentioned X.U.Hacks |
2023-01-20 16:26:44 +0100 | <geekosaur> | if that still doesn't work on the external then try adding the rescreen hook and running it there |
2023-01-20 16:52:52 +0100 | <xmonadtrack> | New xmonad-contrib branch created: pull/794 (1 commit) https://github.com/xmonad/xmonad-contrib/pull/794 |
2023-01-20 17:00:09 +0100 | unclechu | (~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle) |
2023-01-20 17:10:59 +0100 | hrberg | (~quassel@171.79-160-161.customer.lyse.net) (Ping timeout: 260 seconds) |
2023-01-20 17:15:59 +0100 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Remote host closed the connection) |
2023-01-20 17:16:27 +0100 | <geekosaur> | hah. someone in a different project I work with got caught by pending review comments not being visible to others the other day… so I see github explicitly marks them as "Pending" now. |
2023-01-20 17:16:41 +0100 | unclechu | (~unclechu@2001:470:69fc:105::354) |
2023-01-20 17:51:27 +0100 | jludwig | (~justin@li657-110.members.linode.com) (Quit: ZNC - https://znc.in) |
2023-01-20 17:52:28 +0100 | jludwig | (~justin@li657-110.members.linode.com) |
2023-01-20 17:54:49 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
2023-01-20 18:15:35 +0100 | <liskin> | pending means you haven't submitted the review yet, I think |
2023-01-20 18:15:48 +0100 | <liskin> | i.e. it's only visible to you and that's intentional |
2023-01-20 18:16:53 +0100 | <geekosaur> | yes, that was the point |
2023-01-20 18:17:11 +0100 | <geekosaur> | gammafunk thought the unsubmitted comments would be visible to others, whoops |
2023-01-20 18:19:38 +0100 | <geekosaur> | he was hoping to discuss them and maybe revise his comments before pushing the button on the review |
2023-01-20 18:19:48 +0100 | <geekosaur> | which is kinda backwards |
2023-01-20 18:51:54 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection) |
2023-01-20 18:58:26 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
2023-01-20 21:06:40 +0100 | rekahsoft | (~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-39.dsl.bell.ca) (Remote host closed the connection) |
2023-01-20 21:09:07 +0100 | rekahsoft | (~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-39.dsl.bell.ca) |
2023-01-20 21:17:54 +0100 | tremon | (~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl) |
2023-01-20 21:55:00 +0100 | mc47 | (~mc47@xmonad/TheMC47) |
2023-01-20 22:04:17 +0100 | rekahsoft | (~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-39.dsl.bell.ca) (Remote host closed the connection) |
2023-01-20 22:04:59 +0100 | rekahsoft | (~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-39.dsl.bell.ca) |