| 2023-12-30 02:28:28 +0100 | xmonadtrack | (~xmonadtra@user/geekosaur/bot/xmonadtrack) (Ping timeout: 276 seconds) |
| 2023-12-30 02:29:05 +0100 | haskellbridge | (~haskellbr@069-135-003-034.biz.spectrum.com) (Ping timeout: 252 seconds) |
| 2023-12-30 02:38:52 +0100 | xmonadtrack | (~xmonadtra@069-135-003-034.biz.spectrum.com) |
| 2023-12-30 02:38:52 +0100 | xmonadtrack | (~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host) |
| 2023-12-30 02:38:52 +0100 | xmonadtrack | (~xmonadtra@user/geekosaur/bot/xmonadtrack) |
| 2023-12-30 02:39:25 +0100 | haskellbridge | (~haskellbr@069-135-003-034.biz.spectrum.com) |
| 2023-12-30 03:20:31 +0100 | SpiderPig | (~matt@047-132-235-136.res.spectrum.com) |
| 2023-12-30 04:28:59 +0100 | td_ | (~td@i53870902.versanet.de) (Ping timeout: 252 seconds) |
| 2023-12-30 04:30:38 +0100 | td_ | (~td@i53870904.versanet.de) |
| 2023-12-30 04:35:23 +0100 | thunderrd | (~thunderrd@183.182.110.131) |
| 2023-12-30 06:27:08 +0100 | thunderrd | (~thunderrd@183.182.110.131) (Remote host closed the connection) |
| 2023-12-30 10:33:30 +0100 | T_X_ | (~T_X@diktynna.open-mesh.org) |
| 2023-12-30 10:33:55 +0100 | T_X | (~T_X@diktynna.open-mesh.org) (Read error: Connection reset by peer) |
| 2023-12-30 12:33:18 +0100 | edog | (~edog@alcotrash.org) |
| 2023-12-30 13:04:00 +0100 | Guest67 | (~Guest67@2400:1a00:bd11:7857:2e0:4cff:fefc:a34d) |
| 2023-12-30 13:06:33 +0100 | Guest67 | (~Guest67@2400:1a00:bd11:7857:2e0:4cff:fefc:a34d) () |
| 2023-12-30 14:26:21 +0100 | Guest1 | (~Guest1@2a02:8071:b80:1c20:4ed5:77ff:fea2:6ef5) |
| 2023-12-30 14:42:28 +0100 | Guest1 | Groggermaniac |
| 2023-12-30 14:49:18 +0100 | <Groggermaniac> | Hey all, currently a _NET_ACTIVE_WINDOW request with a bad window id causes (windows id) to be called, which is apparently enough to collapse context menus and such, which is a problem if opening the context menu is what caused the request in the first place: https://old.reddit.com/r/xmonad/comments/18rck0e/reaper_daw_and_xmonad/. Should I make an |
| 2023-12-30 14:49:19 +0100 | <Groggermaniac> | issue and/or a pull request for this, or is it not a bug? |
| 2023-12-30 14:54:17 +0100 | <liskin> | Hm, I guess I should have made the activateHook a MaybeManageHook instead |
| 2023-12-30 14:54:37 +0100 | <liskin> | I vaguely remember thinking about it and deciding against |
| 2023-12-30 14:54:40 +0100 | <liskin> | But why |
| 2023-12-30 14:55:17 +0100 | <liskin> | If I had you'd have the ability to ignore the request more easily |
| 2023-12-30 14:56:04 +0100 | <liskin> | Now you have to code your own event hook that filters the request before EwmhDesktops sees it |
| 2023-12-30 14:56:51 +0100 | <liskin> | Actually I think I wanted to make it possible to use PureX somehow instead of windows, but couldn't figure out a way to do it nicely |
| 2023-12-30 14:57:05 +0100 | <liskin> | Decades of legacy apis... |
| 2023-12-30 16:21:47 +0100 | <haskellbridge> | <Solid> Looking forward to a fresh start with wlroots? :P |
| 2023-12-30 17:13:05 +0100 | <liskin> | :-) |
| 2023-12-30 17:32:16 +0100 | <geekosaur> | I already made that comment on discourse |
| 2023-12-30 17:34:17 +0100 | T_X_ | T_X |
| 2023-12-30 19:09:50 +0100 | portnov | (~portnov@v-20678-unlim.vpn.mgn.ru) |
| 2023-12-30 19:48:16 +0100 | andi_ | (~andi@user/andi/x-3467420) |
| 2023-12-30 19:49:15 +0100 | <andi_> | hello i am using xmonad and xmobar, anybody has an idea why my xmobar (config: https://paste.xinu.at/7XpAD/) looks like: https://paste.xinu.at/qOptdD/ (it's slighly shifted to the top) |
| 2023-12-30 19:51:42 +0100 | <geekosaur> | looks to me like the font's too big for the bar's size? |
| 2023-12-30 19:56:42 +0100 | <andi_> | hmm alright i'll tinker a bit |
| 2023-12-30 19:58:11 +0100 | <geekosaur> | when sizing a font you also have to consider ascenders and descenders; the descenders look like they're in the right place |
| 2023-12-30 20:03:21 +0100 | portnov | (~portnov@v-20678-unlim.vpn.mgn.ru) (Remote host closed the connection) |
| 2023-12-30 20:37:53 +0100 | portnov | (~portnov@v-20678-unlim.vpn.mgn.ru) |
| 2023-12-30 20:43:47 +0100 | <ectospasm> | I've migrated my xmonad.hs to a new laptop, and while I was tweaking things getting things to line up correctly on the screen, I seem to have lost my DynamicWorkspaces prompt. I have (winKey, xK_h) set up to switch to the named workspace, and (winKey, xK_z) to shift the current window to the named workspace. |
| 2023-12-30 20:44:01 +0100 | <ectospasm> | The prompt isn't showing anymore, here's my current xmonad.hs: https://git.eldon.me/trey/XMonad/src/branch/master/xmonad.hs |
| 2023-12-30 21:08:59 +0100 | <geekosaur> | hm. the usual cause of a prompt not showing is a bad font, but you're using the same font everywhere and the monospace alias is mandatory |
| 2023-12-30 21:09:45 +0100 | <geekosaur> | can you check session log output (usually ~/.Xsession-errors) for any exception messages? |
| 2023-12-30 22:19:40 +0100 | portnov | (~portnov@v-20678-unlim.vpn.mgn.ru) (Remote host closed the connection) |
| 2023-12-30 22:30:10 +0100 | Groggermaniac | (~Guest1@2a02:8071:b80:1c20:4ed5:77ff:fea2:6ef5) (Quit: Client closed) |
| 2023-12-30 22:35:15 +0100 | <ectospasm> | geekosaur: I don't have ~/.Xsession-errors, and it looks like ~/.xmonad/xmonad.errors just has where I compiled it last (just before launching this X session with startx) |
| 2023-12-30 22:37:23 +0100 | <geekosaur> | how do you start X11? |
| 2023-12-30 22:37:58 +0100 | <geekosaur> | if you use startx, the session log is on the VT where you ran startx |
| 2023-12-30 22:38:33 +0100 | <geekosaur> | if you use sddm, the session log is ~/.local/share/sddm/xorg-session.log |
| 2023-12-30 22:42:22 +0100 | <ectospasm> | I'm not using a DM, just the Linux console. I have an alias stx='xmonad --recompile && startx', and that's how I start it. |
| 2023-12-30 22:42:51 +0100 | <geekosaur> | okay, then you need to switch back to the text VT to see the log |
| 2023-12-30 22:43:18 +0100 | <geekosaur> | ctrl+alt+F<n> (<n> is usually 1) |
| 2023-12-30 22:43:28 +0100 | <ectospasm> | Hmmmm, X is running on VT1, it doesn't spawn on VT7 like I've seen a long time ago. |
| 2023-12-30 22:44:06 +0100 | <geekosaur> | odd |
| 2023-12-30 22:46:07 +0100 | <geekosaur> | you can try switching to all the VTs to see which one is text, or `ps -ef | grep startx` and see what it shows for its tty |
| 2023-12-30 22:46:07 +0100 | <ectospasm> | This is Arch, and that's how it's been doing it for a while. |
| 2023-12-30 22:46:40 +0100 | <ectospasm> | yeah, it says tty1 |
| 2023-12-30 22:47:17 +0100 | <geekosaur> | odd, that'd be VT 1 |
| 2023-12-30 22:47:39 +0100 | <ectospasm> | And when I press fn + ctrl + F1 it takes me back to X; fn + ctrl + F2..F6 show login prompts on tty2-6 |
| 2023-12-30 22:50:50 +0100 | <geekosaur> | wonder if they're actually switching it to graphics instead of using a different VT; unfortunately that would mean you have no session log and will have to restart X with startx output and error redirected (startx >~/.Xsession-errors 2>&1) |
| 2023-12-30 22:51:10 +0100 | <ectospasm> | I see a bunch of stuff printed in ~/.local/share/xorg/Xorg.0.log when I switch TTYs |
| 2023-12-30 22:51:25 +0100 | <ectospasm> | OK, I can add that to my alias. |
| 2023-12-30 22:51:33 +0100 | <geekosaur> | right, that's the server log |
| 2023-12-30 22:51:43 +0100 | <geekosaur> | it doesn't contain session output |
| 2023-12-30 22:51:49 +0100 | <ectospasm> | OK |
| 2023-12-30 22:54:11 +0100 | <ectospasm> | OK, now that I'm capturing .Xsession-errors I see this: user error (createFontSet) |
| 2023-12-30 22:54:22 +0100 | <ectospasm> | So it doesn't like my font? |
| 2023-12-30 22:54:58 +0100 | <geekosaur> | worse than that, it seems like your xmonad-contrib may have been built without XFT support |
| 2023-12-30 22:54:58 +0100 | <ectospasm> | That's when I press winKey + XK_z or winKey + xK_h. |
| 2023-12-30 22:55:14 +0100 | <geekosaur> | so you would have to use old-style fonts |
| 2023-12-30 22:56:05 +0100 | <ectospasm> | Hmmm, on my other machine this monospace font was working OK, also on Arch. |
| 2023-12-30 22:57:26 +0100 | <geekosaur> | how did you install xmonad and xmonad-contrib, arch packages or hackage/cabal/stack? |
| 2023-12-30 22:59:02 +0100 | <ectospasm> | Arch packages |
| 2023-12-30 23:00:10 +0100 | <ectospasm> | I know the Arch Haskell packages have always been considered broken, but I've had the least trouble with the xmonad stuff (other Haskell packages have had issues) |
| 2023-12-30 23:01:01 +0100 | <geekosaur> | odd. the dependencies indicate that it was built with -fuse_xft |
| 2023-12-30 23:06:03 +0100 | <geekosaur> | oh, wait |
| 2023-12-30 23:06:16 +0100 | <geekosaur> | the font name should be prefixed by "xft:" |
| 2023-12-30 23:06:38 +0100 | <geekosaur> | I'm not sure how it would have been working without that |
| 2023-12-30 23:06:56 +0100 | <geekosaur> | https://github.com/xmonad/xmonad-contrib/blob/master/XMonad/Prompt.hs#L325 for example |
| 2023-12-30 23:08:10 +0100 | <geekosaur> | https://github.com/geekosaur/xmonad.hs/blob/hilfy-2023/xmonad.hs#L340 is what I use |
| 2023-12-30 23:08:28 +0100 | <ectospasm> | Oh, OK. Let me try that. |
| 2023-12-30 23:08:42 +0100 | <geekosaur> | (I have a double resolution monitor so fonts are stupid big…) |
| 2023-12-30 23:09:30 +0100 | <ectospasm> | That fixed it! I don't know how it was working before without it. |
| 2023-12-30 23:10:19 +0100 | <ectospasm> | I've been mucking about with Xft.DPI a bit, when it's set to the DPI as detected by xdpyinfo fonts in GTK+ and Qt apps are too tiny to read |
| 2023-12-30 23:10:53 +0100 | <ectospasm> | I'm getting old, so anything too small is a pain to read. |
| 2023-12-30 23:11:22 +0100 | <ectospasm> | (my new laptop has an OLED screen, and it's much higher resolution than my old laptop) |
| 2023-12-30 23:11:39 +0100 | <ectospasm> | I'm regretting getting this screen, it really reduces battery life quite a bit. |
| 2023-12-30 23:12:09 +0100 | <ectospasm> | I've been told this laptop should be able to get 14 hours out of a charge, but I can only manage just under 7 with this OLED screen. |