| 2023-01-15 01:04:47 +0100 | jabuxas | (~jabuxas@user/jabuxas) (Quit: WeeChat 2.8) |
| 2023-01-15 01:11:29 +0100 | jabuxas | (~jabuxas@user/jabuxas) |
| 2023-01-15 02:10:51 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2023-01-15 02:30:57 +0100 | minnie | (~minnie@159.196.202.199) |
| 2023-01-15 04:02:52 +0100 | banc | (banc@gateway/vpn/protonvpn/banc) (Ping timeout: 252 seconds) |
| 2023-01-15 04:26:06 +0100 | banc | (banc@gateway/vpn/protonvpn/banc) |
| 2023-01-15 04:59:44 +0100 | td_ | (~td@83.135.9.53) (Ping timeout: 272 seconds) |
| 2023-01-15 05:00:59 +0100 | td_ | (~td@83.135.9.57) |
| 2023-01-15 05:24:18 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection) |
| 2023-01-15 05:30:34 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2023-01-15 06:02:21 +0100 | hrberg | (~quassel@171.79-160-161.customer.lyse.net) (Ping timeout: 255 seconds) |
| 2023-01-15 07:12:12 +0100 | lokesh1197 | (~Thunderbi@14.139.128.52) |
| 2023-01-15 07:38:42 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 272 seconds) |
| 2023-01-15 09:01:40 +0100 | lokesh1197 | (~Thunderbi@14.139.128.52) (Ping timeout: 272 seconds) |
| 2023-01-15 09:33:55 +0100 | bla | (~bla@79.191.115.97.ipv4.supernova.orange.pl) (Ping timeout: 260 seconds) |
| 2023-01-15 10:00:11 +0100 | unclechu | (~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle) |
| 2023-01-15 10:00:11 +0100 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2023-01-15 10:00:40 +0100 | bla | (~bla@79.191.115.97.ipv4.supernova.orange.pl) |
| 2023-01-15 10:18:27 +0100 | thunderrd | (~thunderrd@183.182.111.166) (Ping timeout: 265 seconds) |
| 2023-01-15 10:46:48 +0100 | bla | (~bla@79.191.115.97.ipv4.supernova.orange.pl) (Ping timeout: 272 seconds) |
| 2023-01-15 10:51:23 +0100 | lokesh1197 | (~Thunderbi@14.139.128.52) |
| 2023-01-15 10:53:33 +0100 | bla | (~bla@79.191.115.97.ipv4.supernova.orange.pl) |
| 2023-01-15 11:36:05 +0100 | bla | (~bla@79.191.115.97.ipv4.supernova.orange.pl) (Remote host closed the connection) |
| 2023-01-15 11:51:09 +0100 | bla | (~bla@79.191.115.97.ipv4.supernova.orange.pl) |
| 2023-01-15 12:09:19 +0100 | lokesh1197 | (~Thunderbi@14.139.128.52) (Ping timeout: 260 seconds) |
| 2023-01-15 12:20:22 +0100 | lokesh1197 | (~Thunderbi@14.139.128.52) |
| 2023-01-15 12:24:03 +0100 | tremon | (~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl) |
| 2023-01-15 13:04:01 +0100 | rundown | (~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) |
| 2023-01-15 13:29:29 +0100 | <vrs> | the new StatusBar module doesn't really like it when you do screen-specific stuff |
| 2023-01-15 13:29:42 +0100 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) |
| 2023-01-15 13:29:53 +0100 | <vrs> | sure there's the screen-specific loggers in X.U.Loggers but withScreen itself is not exported |
| 2023-01-15 13:29:56 +0100 | unclechu | (~unclechu@2001:470:69fc:105::354) |
| 2023-01-15 13:30:58 +0100 | <vrs> | and it's not *hard* to lift and use it but it's also not documented at all (ok yeah it takes a screen parameter - which you're probably supposed to pass while instantiating the config. very different from multiPP) |
| 2023-01-15 13:31:36 +0100 | <vrs> | granted I was probably one of three users of the original dynamicbars |
| 2023-01-15 13:33:25 +0100 | <vrs> | (I feel like logging screen specific stuff is the only reason you'd have multiple status bars? just to show which screen is focused for example?) |
| 2023-01-15 13:54:40 +0100 | ectospasm | (~ectospasm@user/ectospasm) (Quit: WeeChat 3.7.1) |
| 2023-01-15 14:32:40 +0100 | vifon | (~vifon@user/vifon) |
| 2023-01-15 14:34:23 +0100 | <vifon> | Hello. I've just updated xmobar to 0.45 and it seems it uses a new format to specify fonts. Previously it was possible to specify multiple fonts by separating them with ";" (inside the "font" setting, without using "additionalFonts"). Is it possibly to do so in the new format? |
| 2023-01-15 15:08:39 +0100 | ectospasm | (~ectospasm@user/ectospasm) |
| 2023-01-15 15:11:23 +0100 | <Solid> | vrs: I think any hints (or PRs) in that direction would be most welcome |
| 2023-01-15 15:12:00 +0100 | <Solid> | I reckon for most people the only screen-specific stuff they show is the workspaces on that monitor (at least that's the case for me) so that front could probably use some love |
| 2023-01-15 15:13:11 +0100 | <Solid> | vifon: I believe so; now you just separate them with commas: https://codeberg.org/xmobar/xmobar/src/branch/master/doc/quick-start.org#fonts |
| 2023-01-15 15:13:29 +0100 | <Solid> | (note: I'm just going by the documentation; xmobar 0.45+ doesn't build on musl so I'm still on 0.44) |
| 2023-01-15 15:17:37 +0100 | <vifon> | Oh wow, this syntax really is crazy. |
| 2023-01-15 15:17:48 +0100 | <vifon> | > It's also possible to specify a list of fonts, separating them by commas, so that they act as fallbacks when the preceding one is not able to display a given glyph. A bit confusingly, the styles and sizes come in reverse order after the families: |
| 2023-01-15 15:17:50 +0100 | <lambdabot> | <hint>:1:38: error: parse error on input ‘of’ |
| 2023-01-15 15:17:50 +0100 | <vifon> | > Family 1, Family 2 Styles 2 Size 2, Styles 1 Size 1 |
| 2023-01-15 15:17:52 +0100 | <lambdabot> | <hint>:1:9: error: parse error on input ‘,’ |
| 2023-01-15 15:18:00 +0100 | <vifon> | Ouch, sorry, lambdabot. |
| 2023-01-15 15:18:07 +0100 | <Solid> | It's pretty horrible yeah |
| 2023-01-15 15:18:10 +0100 | jabuxas | (~jabuxas@user/jabuxas) (Quit: WeeChat 2.8) |
| 2023-01-15 15:36:17 +0100 | qbt | (~qbt@user/edun) |
| 2023-01-15 15:51:32 +0100 | wuqas | (~user@2804:14c:8793:97d5:8230:49ff:fe14:1509) |
| 2023-01-15 15:58:02 +0100 | <wuqas> | can i remap default shortcuts in 'additionalKeysP'? |
| 2023-01-15 15:58:27 +0100 | <geekosaur> | yes |
| 2023-01-15 15:58:46 +0100 | <wuqas> | i tried something like ("M-<Enter>", "M-x") but it throws me an error |
| 2023-01-15 15:59:00 +0100 | <geekosaur> | oh, not like that, no |
| 2023-01-15 15:59:37 +0100 | <wuqas> | what should i read on documentation to try to understand that? |
| 2023-01-15 15:59:58 +0100 | <wuqas> | i usually rely on answers from the internet to do my things but i could not find any on remapping default shortcuts |
| 2023-01-15 15:59:59 +0100 | <geekosaur> | I thought you meant replacing the definition on one of the builtin keys |
| 2023-01-15 16:02:01 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2023-01-15 16:02:26 +0100 | <geekosaur> | there's no shorthand for taking the definition from one and putting it on another, especially not like that because the defaults are already converted to `(KeyMask, KeySym)` format |
| 2023-01-15 16:04:18 +0100 | <geekosaur> | you could do something silly like `("M-x", (mod4Mask, xK_Enter) ! keys def def)` but that's error-prone and ugly |
| 2023-01-15 16:04:53 +0100 | <geekosaur> | I may have the lookup reversed. but i8n any case I don't recommend it |
| 2023-01-15 16:05:29 +0100 | <geekosaur> | easier is just to take the definition from https://github.com/xmonad/xmonad/blob/master/src/XMonad/Config.hs and respecifying it |
| 2023-01-15 16:06:43 +0100 | <geekosaur> | yeh, I reversed them. `("M-x", keys def def ! (mod4Mask, xK_Enter))` |
| 2023-01-15 16:09:53 +0100 | <wuqas> | hmmm |
| 2023-01-15 16:10:22 +0100 | <wuqas> | thanks for that, i will try to add 'keys :: Xconfig Layout' to my script |
| 2023-01-15 16:11:03 +0100 | <geekosaur> | keys :: XConfig Layout -> M.Map (KeyMask, KeySym) (X ()) |
| 2023-01-15 16:11:24 +0100 | <geekosaur> | it's the accessor for the `keys` field in an XConfig |
| 2023-01-15 16:11:36 +0100 | <wuqas> | heheh |
| 2023-01-15 16:11:43 +0100 | <wuqas> | this stuff is rocket science |
| 2023-01-15 16:12:24 +0100 | <geekosaur> | nnm actually I missed a step since it's not the Map directly, it takes an XConfig parameter |
| 2023-01-15 16:12:59 +0100 | <vrs> | Solid: I have essentially completely custom logging set up due to how I manage my workspaces (I create sub-workspaces as pseudogroups because X.L.Groups doesn't play well with 2D navigation, among others) and in multiscreen setups, an important part of telling what screen I'm on is which of my xmobars has colors |
| 2023-01-15 16:13:01 +0100 | <geekosaur> | keys :: LayoutClass l a => XConfig (l a) -> (XConfig Layout -> M.Map (KeyMask, KeySym) (X ())) |
| 2023-01-15 16:13:10 +0100 | <vrs> | Solid: https://i.imgur.com/p9qriVe.png |
| 2023-01-15 16:13:26 +0100 | <geekosaur> | this is why AdditionalKeysP exists, it hides the ugly stuff |
| 2023-01-15 16:13:35 +0100 | <geekosaur> | (hence EZConfig) |
| 2023-01-15 16:13:49 +0100 | <wuqas> | yeah, neat solution for adding custom shortcuts |
| 2023-01-15 16:14:09 +0100 | <wuqas> | can i add Xconfig Layout to my 'main = xmonad $ def' in some way? |
| 2023-01-15 16:14:16 +0100 | <wuqas> | i am 102% lost |
| 2023-01-15 16:14:21 +0100 | <vrs> | Solid: I think the most annoying bits of my current config are 1. withScreen is not exported 2. dynamicworkspaceorder doesn't have insertBefore/After functionality |
| 2023-01-15 16:14:24 +0100 | <geekosaur> | no |
| 2023-01-15 16:14:27 +0100 | <vrs> | both of which I think I'll cut PRs for |
| 2023-01-15 16:14:41 +0100 | <geekosaur> | you already have an XConfig, it's the `def $ ...` |
| 2023-01-15 16:14:49 +0100 | <wuqas> | so i have to create something like `additionalKeysP`? |
| 2023-01-15 16:15:30 +0100 | <geekosaur> | `XConfig Layout` is what it becomes internally, your layout is wrapped in an existential so xmonad's guts don't have tpo deal with something whose type depends on what you put in your `layoutHook` |
| 2023-01-15 16:15:41 +0100 | <vrs> | vifon: huhhh that explains some of my recent troubles |
| 2023-01-15 16:16:09 +0100 | <wuqas> | but if i try to add ((modMask .|. shiftMask, xK_Return), spawn $ XMonad.terminal conf) -- %! Launch terminal | to my def $ it throws me an error |
| 2023-01-15 16:16:53 +0100 | <geekosaur> | you just want the `spawn` part |
| 2023-01-15 16:17:25 +0100 | <vrs> | wuqas: I tend to use removeKeysP |
| 2023-01-15 16:17:29 +0100 | <geekosaur> | the rest is the "raw" version of "M-S-<Enter>" |
| 2023-01-15 16:18:35 +0100 | <Solid> | vrs: that's a pretty interesting setup—certainly very far from what I've seen anyone of us use (hence, I suppose, the underdocumented/unexported functions :) |
| 2023-01-15 16:19:25 +0100 | <geekosaur> | it would be possible but unwieldy to write a `remapKeysP`, you'd need to write something that "reversed" the rewriting of "P" format to "raw" |
| 2023-01-15 16:19:26 +0100 | <vrs> | one of these days I'm gonna post my config... |
| 2023-01-15 16:19:38 +0100 | <Solid> | I'd ceratinly be interested |
| 2023-01-15 16:21:20 +0100 | <Solid> | geekosaur: should already be done with XMonad.Prelude.keymaskToString |
| 2023-01-15 16:21:45 +0100 | <Solid> | Er, keyToString |
| 2023-01-15 16:24:01 +0100 | <geekosaur> | oh, huh, right, and I even wrote the first version of that 🙃 |
| 2023-01-15 16:24:10 +0100 | <geekosaur> | (part of the debug stuff) |
| 2023-01-15 16:24:53 +0100 | <wuqas> | how can i use removeKeysP? i am trying this: `removeKeysP` |
| 2023-01-15 16:24:54 +0100 | <wuqas> | [ ("M-<Enter>") |
| 2023-01-15 16:24:54 +0100 | <wuqas> | ] |
| 2023-01-15 16:25:10 +0100 | <wuqas> | but M-Enter still works... |
| 2023-01-15 16:25:40 +0100 | <wuqas> | and just in case i got it correctly, if i remove a shortcut with removeKeysP i can set a new shortcut on the removed key? |
| 2023-01-15 16:25:40 +0100 | <geekosaur> | I think, as shown in Config, that key is actually xK_Return aka <Return> |
| 2023-01-15 16:25:54 +0100 | <geekosaur> | you can as long as the removeKeysP comes first |
| 2023-01-15 16:26:08 +0100 | <geekosaur> | it processes them in order |
| 2023-01-15 16:26:13 +0100 | <wuqas> | uhul! |
| 2023-01-15 16:26:16 +0100 | <wuqas> | thanks >.< |
| 2023-01-15 16:27:07 +0100 | <geekosaur> | which also means if you're replacing a definition you don't need to remove it first, it'll overwrite the existing one if any |
| 2023-01-15 16:27:42 +0100 | <wuqas> | lol |
| 2023-01-15 16:27:58 +0100 | <wuqas> | the whole episode was <Enter> for <Return> |
| 2023-01-15 16:28:08 +0100 | <Solid> | hah |
| 2023-01-15 16:28:26 +0100 | <geekosaur> | old engineering workstations were what X11's key definitions were designed for, and Enter meant something different |
| 2023-01-15 16:29:07 +0100 | <wuqas> | this key definitions on xmonad.hs works like this: https://github.com/k0kubun/xremap? |
| 2023-01-15 16:29:25 +0100 | lb9di | evilop |
| 2023-01-15 16:29:30 +0100 | <wuqas> | i mean, they are the same or some are on a lower level than the other? |
| 2023-01-15 16:30:16 +0100 | <geekosaur> | higher level, but not much higher |
| 2023-01-15 16:30:31 +0100 | <geekosaur> | compare xmonad key bindings to kmonad |
| 2023-01-15 16:30:41 +0100 | <wuqas> | which? the xmonad or the github app i send? |
| 2023-01-15 16:30:46 +0100 | <geekosaur> | (which does for keys roughly what xmonad does for window management) |
| 2023-01-15 16:31:38 +0100 | <geekosaur> | xmonad's key definitions only affect other apps to the extent that they are "passive key grabs" so when the X server sees them it gives xmonad control and sends the key to it |
| 2023-01-15 16:31:50 +0100 | <geekosaur> | but you can't really remap keys for other applications this way |
| 2023-01-15 16:32:07 +0100 | <geekosaur> | (there are some unreliable hacks, but if you want that use kmonad or that app you pointed to) |
| 2023-01-15 16:32:16 +0100 | <wuqas> | interesting |
| 2023-01-15 16:32:28 +0100 | <wuqas> | there is any other $monad app out there? |
| 2023-01-15 16:32:51 +0100 | <geekosaur> | termonad which is a terminal emulator |
| 2023-01-15 16:35:13 +0100 | <wuqas> | ok, here is another one, i typed "startupHook = setDefaultCursor xC_cross" on my xmonad $ def |
| 2023-01-15 16:35:37 +0100 | <wuqas> | but i noticed that when i open some app, the default pointer cursor is the one being used |
| 2023-01-15 16:35:37 +0100 | <Solid> | I think stumpwm works like this where the regrab the keyboard/mouse whenever the focused window changes |
| 2023-01-15 16:35:47 +0100 | <Solid> | in order to faciliate app-specific bindings |
| 2023-01-15 16:36:24 +0100 | <wuqas> | oh! there is a lot of remappers out there no? |
| 2023-01-15 16:36:35 +0100 | <wuqas> | the cutest i found is: https://github.com/sezanzeb/input-remapper |
| 2023-01-15 16:36:51 +0100 | <geekosaur> | `setDefaultCursor`, strictly speaking, sets the cursor for the root window. many but not all apps will inherit that |
| 2023-01-15 16:36:57 +0100 | <wuqas> | but as far as i remember, it did not worked for me... but that was a while ago |
| 2023-01-15 16:37:13 +0100 | <geekosaur> | but an app whoich explicitly sets the arrow cursor will use that regardless of what you specify |
| 2023-01-15 16:37:19 +0100 | <wuqas> | can i set a major default cursor? |
| 2023-01-15 16:37:47 +0100 | <wuqas> | yeah... i got this with xterm and firefox |
| 2023-01-15 16:37:55 +0100 | <wuqas> | and emacs |
| 2023-01-15 16:38:21 +0100 | <geekosaur> | yeh, all of them specify. it's not at all uncommon |
| 2023-01-15 16:38:40 +0100 | <geekosaur> | emacs in particular is constantly changing cursors for me so it can't just inherit |
| 2023-01-15 16:39:19 +0100 | <geekosaur> | text bar over text, pointer over an empty area, double-headed arrows over modelines, etc. |
| 2023-01-15 16:40:35 +0100 | <geekosaur> | if you want more control over mouse cursors, use an app like lxappearance to set and maybe define a cursor theme |
| 2023-01-15 16:43:04 +0100 | wuqas` | (~user@191.177.51.98) |
| 2023-01-15 16:43:17 +0100 | wuqas | (~user@2804:14c:8793:97d5:8230:49ff:fe14:1509) (Ping timeout: 246 seconds) |
| 2023-01-15 16:58:11 +0100 | wuqas` | (~user@191.177.51.98) (Remote host closed the connection) |
| 2023-01-15 17:06:30 +0100 | matijja | (~matijja@193.77.181.201) (Quit: ZNC 1.8.2 - https://znc.in) |
| 2023-01-15 17:06:59 +0100 | matijja | (~matijja@193.77.181.201) |
| 2023-01-15 17:08:11 +0100 | <liskin> | Solid: actually my setup might be similar to vrs's, al least the xmobar bits |
| 2023-01-15 17:09:02 +0100 | <liskin> | X.H.StatusBar works for me, but I don't use PP at all for the screen-specific bars, I just assemble the content manually |
| 2023-01-15 17:09:26 +0100 | <liskin> | Suppose X.something.Loggers might help, but the code works so why change it |
| 2023-01-15 17:09:59 +0100 | wuqas | (~user@2804:14c:8793:97d5:8230:49ff:fe14:1509) |
| 2023-01-15 17:11:25 +0100 | <wuqas> | i think i got the cursor by changing it directly on /usr/share/icons... |
| 2023-01-15 17:13:05 +0100 | <geekosaur> | okay, so you found a different way to manipulate cursor themes 🙂 |
| 2023-01-15 17:13:13 +0100 | <wuqas> | heheh |
| 2023-01-15 17:13:32 +0100 | <wuqas> | all i wanted was to change the default for the icon 'cell' on Adwaita |
| 2023-01-15 17:13:53 +0100 | <wuqas> | so i had to copy and substitute default and left_ptr |
| 2023-01-15 17:14:18 +0100 | <wuqas> | but i installed the app you mentioned.. went to a webpage with icon packs but i could not find an elegant solution to the open crosshair i wanted |
| 2023-01-15 17:14:46 +0100 | <geekosaur> | that was why I mentioned "maybe define" |
| 2023-01-15 17:15:01 +0100 | <geekosaur> | I don't think it has a proper cursor theme editor, though |
| 2023-01-15 17:15:42 +0100 | <wuqas> | yeah.. i noticed that files do not have an .extension |
| 2023-01-15 17:16:05 +0100 | <geekosaur> | yeh, it just uses the names defined by X11 |
| 2023-01-15 17:19:03 +0100 | minnie | (~minnie@159.196.202.199) (Ping timeout: 256 seconds) |
| 2023-01-15 17:26:45 +0100 | <Solid> | liskin: oh, interesting; in that case you should just switch to *Loggers to have PRs for days :P |
| 2023-01-15 17:33:04 +0100 | matijja | (~matijja@193.77.181.201) (Quit: ZNC 1.8.2 - https://znc.in) |
| 2023-01-15 17:33:45 +0100 | matijja | (~matijja@193.77.181.201) |
| 2023-01-15 17:52:37 +0100 | wuqas | (~user@2804:14c:8793:97d5:8230:49ff:fe14:1509) (Remote host closed the connection) |
| 2023-01-15 18:43:50 +0100 | rundown | (~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) (Quit: WeeChat 3.0) |
| 2023-01-15 18:57:09 +0100 | Solitary | (~Solitary@user/solitary) |
| 2023-01-15 19:11:41 +0100 | Solitary | (~Solitary@user/solitary) (Ping timeout: 252 seconds) |
| 2023-01-15 19:13:13 +0100 | Solitary | (~Solitary@user/solitary) |
| 2023-01-15 19:54:14 +0100 | Solitary | (~Solitary@user/solitary) (Ping timeout: 260 seconds) |
| 2023-01-15 19:59:09 +0100 | Solitary | (~Solitary@user/solitary) |
| 2023-01-15 20:18:45 +0100 | Solitary | (~Solitary@user/solitary) (Ping timeout: 265 seconds) |
| 2023-01-15 20:22:42 +0100 | Solitary | (~Solitary@user/solitary) |
| 2023-01-15 20:36:42 +0100 | Solitary | (~Solitary@user/solitary) (Quit: All work and no play makes Jack a dull boy.) |
| 2023-01-15 20:37:51 +0100 | Solitary | (~Solitary@user/solitary) |
| 2023-01-15 20:44:14 +0100 | lokesh1197 | (~Thunderbi@14.139.128.52) (Quit: lokesh1197) |
| 2023-01-15 20:44:37 +0100 | lokesh1197 | (~Thunderbi@14.139.128.52) |
| 2023-01-15 20:53:40 +0100 | Solitary | (~Solitary@user/solitary) (Quit: All work and no play makes Jack a dull boy.) |
| 2023-01-15 20:55:44 +0100 | Solitary | (~Solitary@user/solitary) |
| 2023-01-15 21:09:37 +0100 | Solitary | (~Solitary@user/solitary) (Ping timeout: 268 seconds) |
| 2023-01-15 21:16:12 +0100 | jabuxas | (~jabuxas@user/jabuxas) |
| 2023-01-15 21:17:16 +0100 | jabuxas | (~jabuxas@user/jabuxas) (Client Quit) |
| 2023-01-15 21:17:35 +0100 | jabuxas | (~jabuxas@user/jabuxas) |
| 2023-01-15 21:19:12 +0100 | Solitary | (~Solitary@user/solitary) |
| 2023-01-15 21:20:51 +0100 | jabuxas | (~jabuxas@user/jabuxas) (Client Quit) |
| 2023-01-15 21:21:01 +0100 | jabuxas | (~jabuxas@user/jabuxas) |
| 2023-01-15 21:21:15 +0100 | jabuxas | (~jabuxas@user/jabuxas) (Client Quit) |
| 2023-01-15 21:21:58 +0100 | jabuxas | (~jabuxas@user/jabuxas) |
| 2023-01-15 21:22:05 +0100 | lokesh1197 | (~Thunderbi@14.139.128.52) (Ping timeout: 260 seconds) |
| 2023-01-15 21:33:48 +0100 | Solitary | (~Solitary@user/solitary) (Quit: All work and no play makes Jack a dull boy.) |
| 2023-01-15 21:35:15 +0100 | Solitary | (~Solitary@user/solitary) |
| 2023-01-15 21:42:56 +0100 | bla | (~bla@79.191.115.97.ipv4.supernova.orange.pl) (Ping timeout: 272 seconds) |
| 2023-01-15 21:51:17 +0100 | jabuxas | (~jabuxas@user/jabuxas) (Quit: WeeChat 3.6) |
| 2023-01-15 21:52:04 +0100 | jabuxas | (~jabuxas@user/jabuxas) |
| 2023-01-15 21:55:50 +0100 | hrberg | (~quassel@171.79-160-161.customer.lyse.net) |
| 2023-01-15 21:56:35 +0100 | <geekosaur> | wonder if I should clean up and package this hack: https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs#L300-L311 (comment is wrong, it works now but needs cleanup) |
| 2023-01-15 21:59:17 +0100 | Solitary | (~Solitary@user/solitary) (Ping timeout: 265 seconds) |
| 2023-01-15 22:00:39 +0100 | qbt | (~qbt@user/edun) (Quit: WeeChat 3.5) |
| 2023-01-15 22:11:07 +0100 | hrberg | (~quassel@171.79-160-161.customer.lyse.net) (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) |
| 2023-01-15 22:11:27 +0100 | <liskin> | Solid: hacktoberfest is months away though |
| 2023-01-15 22:11:47 +0100 | hrberg | (~quassel@171.79-160-161.customer.lyse.net) |
| 2023-01-15 22:11:51 +0100 | <liskin> | Which reminds that they still didn't evaluate the maintainers activity it seems |
| 2023-01-15 22:12:05 +0100 | <liskin> | Or just ran out of t-shirts |
| 2023-01-15 22:15:39 +0100 | <vrs> | hmm what could be causing xmobar to suddenly ignore all font configuration? |
| 2023-01-15 22:15:57 +0100 | <vrs> | I seem to have apt-upgraded it, did they break something? |
| 2023-01-15 22:17:48 +0100 | <liskin> | Some might consider switching to pango as breaking everything :-) |
| 2023-01-15 22:18:22 +0100 | <liskin> | Especially those who use bitmap fonts and their distro doesn't ship OpenType versions of them |
| 2023-01-15 22:18:35 +0100 | <liskin> | (not sure if any distro does) |
| 2023-01-15 22:19:09 +0100 | <vrs> | I configured it using xft so far |
| 2023-01-15 22:19:30 +0100 | <liskin> | Yeah that code's gone |
| 2023-01-15 22:19:36 +0100 | <vrs> | reeeee |
| 2023-01-15 22:20:00 +0100 | <vrs> | I mean xft is janky but ignoring it without even so much as an error message? |
| 2023-01-15 22:21:07 +0100 | <geekosaur> | https://ircbrowse.tomsmeding.com/browse/lcxmonad?id=103843#trid103843 |
| 2023-01-15 22:21:46 +0100 | <geekosaur> | read forward, there's some other nasty surprises |
| 2023-01-15 22:24:52 +0100 | <vrs> | such as the bar sizes being pretty off suddenly |
| 2023-01-15 22:28:58 +0100 | <vrs> | it's rendering to something smaller than the font size but reporting the old size to xmonad, afaict |
| 2023-01-15 22:34:39 +0100 | <vrs> | hm "white" now means "white" for <> and "grey" for anything else |
| 2023-01-15 22:34:52 +0100 | <vrs> | I don't like this |
| 2023-01-15 22:36:55 +0100 | <geekosaur> | xmobar doesn't report anything to xmonad |
| 2023-01-15 22:37:04 +0100 | <geekosaur> | what did you mean by that? |
| 2023-01-15 22:37:13 +0100 | <geekosaur> | well, it reports its strut size |
| 2023-01-15 22:38:03 +0100 | <geekosaur> | but that'll follow from some xmobar internal thing; I don't know how it picks its box size relative to the font, or even if it does or makes you pick a suitable font |
| 2023-01-15 22:38:33 +0100 | <vrs> | "a bit confusingly, the styles and sizes come in reverse order after the families" what the shit |
| 2023-01-15 22:38:40 +0100 | <vrs> | who cooked that up |
| 2023-01-15 22:38:46 +0100 | <geekosaur> | that was the main nasty surprise |
| 2023-01-15 22:38:54 +0100 | <geekosaur> | I was referring to |
| 2023-01-15 22:40:40 +0100 | <vrs> | and yeah I was referring to the strut size |
| 2023-01-15 22:41:35 +0100 | <vrs> | whatever it was reporting was inconsistent with what it was displaying |
| 2023-01-15 22:42:16 +0100 | <geekosaur> | I don't think it can pick a box size from the font size because either it has to be able to parse and make sense of font specification strings instead of pushing that off onto pango, or it has to actually render some example text and check the resulting size |
| 2023-01-15 22:43:08 +0100 | <vrs> | yeah I ended up fixing it by using TopH/BottomH instead of TopL/BottomL which I was using previously |
| 2023-01-15 22:48:49 +0100 | <vrs> | seriously though font string specifications shouldn't take inspiration from heptapod A |
| 2023-01-15 23:02:12 +0100 | mc47 | (~mc47@xmonad/TheMC47) |
| 2023-01-15 23:08:28 +0100 | hrberg | (~quassel@171.79-160-161.customer.lyse.net) (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) |
| 2023-01-15 23:14:09 +0100 | hrberg | (~quassel@171.79-160-161.customer.lyse.net) |
| 2023-01-15 23:21:07 +0100 | minnie | (~minnie@159.196.202.199) |
| 2023-01-15 23:28:29 +0100 | Solitary | (~Solitary@user/solitary) |
| 2023-01-15 23:36:26 +0100 | Solitary | (~Solitary@user/solitary) (Quit: All work and no play makes Jack a dull boy.) |
| 2023-01-15 23:39:00 +0100 | Solitary | (~Solitary@user/solitary) |
