2023/09/30

2023-09-30 00:17:23 +0200jabuxas(~jabuxas@user/jabuxas) (Remote host closed the connection)
2023-09-30 01:20:29 +0200chomwitt(~chomwitt@2a02:587:7a24:b000:1ac0:4dff:fedb:a3f1) (Ping timeout: 255 seconds)
2023-09-30 04:07:05 +0200td_(~td@i53870934.versanet.de) (Ping timeout: 255 seconds)
2023-09-30 04:08:41 +0200td_(~td@i5387090E.versanet.de)
2023-09-30 06:55:19 +0200 <haskellbridge> <f​loweyn't (@flowey> Anyone know why xmonad will freeze up whenever a window rapidly changes it's name? dwm doesn't seem to care at all. There are also other cases where a window tries to behave in a strange way, and xmonad will just completely freeze up, whereas dwm just doesn't care
2023-09-30 09:17:30 +0200chomwitt(~chomwitt@2a02:587:7a24:b000:1ac0:4dff:fedb:a3f1)
2023-09-30 09:22:56 +0200chomwitt(~chomwitt@2a02:587:7a24:b000:1ac0:4dff:fedb:a3f1) (Ping timeout: 260 seconds)
2023-09-30 11:26:22 +0200 <liskin> Sounds like the good old "pipe to xmobar filling up" thing
2023-09-30 12:56:08 +0200chomwitt(~chomwitt@2a02:587:7a24:b000:1ac0:4dff:fedb:a3f1)
2023-09-30 13:26:16 +0200jabuxas(~jabuxas@user/jabuxas)
2023-09-30 13:33:17 +0200jabuxas(~jabuxas@user/jabuxas) (Ping timeout: 260 seconds)
2023-09-30 13:49:34 +0200jabuxas(~jabuxas@user/jabuxas)
2023-09-30 14:05:02 +0200jabuxas(~jabuxas@user/jabuxas) (Remote host closed the connection)
2023-09-30 14:06:32 +0200jabuxas(~jabuxas@user/jabuxas)
2023-09-30 14:23:43 +0200jabuxas(~jabuxas@user/jabuxas) (Ping timeout: 264 seconds)
2023-09-30 14:41:19 +0200redgloboli(~redglobol@user/redgloboli) (Quit: ...enter the matrix...)
2023-09-30 14:42:25 +0200redgloboli(~redglobol@user/redgloboli)
2023-09-30 16:49:08 +0200jabuxas(~jabuxas@user/jabuxas)
2023-09-30 17:16:26 +0200jabuxas(~jabuxas@user/jabuxas) (Remote host closed the connection)
2023-09-30 17:17:28 +0200jabuxas(~jabuxas@user/jabuxas)
2023-09-30 17:29:46 +0200jabuxas(~jabuxas@user/jabuxas) (Remote host closed the connection)
2023-09-30 19:10:20 +0200 <haskellbridge> <H​arry Pray IV> Hi everyone. I made new keybindings in my config. They work great but I found a file at I don't know how to get them to update the keybindings file I found at ~/.xmonad/keybindings with out of date keybindings in it. Why doesn't it pull all of my latest keybindings into this file? Is there some way to force xmonad to update that file?
2023-09-30 19:11:01 +0200 <haskellbridge> <H​arry Pray IV> Hi everyone. I made new keybindings in my config. They work great but I don't know how to get them to update the keybindings file I found at ~/.xmonad/keybindings with out of date keybindings in it. Why doesn't it pull all of my latest keybindings into this file? Is there some way to force xmonad to update that file? I have a few like mirror shrink and mirror expand which
2023-09-30 19:11:01 +0200 <haskellbridge> wor <clipped message>
2023-09-30 19:11:02 +0200 <haskellbridge> <H​arry Pray IV> k in my config but don't get output into that keybindings file
2023-09-30 19:13:47 +0200 <geekosaur> we have no clue what that keybindings file is about
2023-09-30 19:19:38 +0200 <haskellbridge> <H​arry Pray IV> interesting. Maybe it was a feature of the config that I forked. I checked the date on it and it seems to coincide with when I originally forked this config.
2023-09-30 19:22:40 +0200 <haskellbridge> <H​arry Pray IV> here's the function that generates them. Pretty cool thing I inherited for free from gvolpe, I guess:
2023-09-30 19:22:41 +0200 <haskellbridge> <H​arry Pray IV> -- Key bindings. Add, modify or remove key bindings here.
2023-09-30 19:22:42 +0200 <haskellbridge> <H​arry Pray IV> ```
2023-09-30 19:22:43 +0200 <haskellbridge> <H​arry Pray IV> showKeybindings :: [((KeyMask, KeySym), NamedAction)] -> NamedAction
2023-09-30 19:22:45 +0200 <haskellbridge> <H​arry Pray IV> showKeybindings xs =
2023-09-30 19:22:46 +0200 <haskellbridge> <H​arry Pray IV> let
2023-09-30 19:22:47 +0200 <haskellbridge> <H​arry Pray IV> filename = "/home/bismuth/.xmonad/keybindings"
2023-09-30 19:22:49 +0200 <haskellbridge> <H​arry Pray IV> command f = "alacritty -e dialog --title 'XMonad Key Bindings' --colors --hline \"$(date)\" --textbox " ++ f ++ " 50 100"
2023-09-30 19:22:50 +0200 <haskellbridge> <H​arry Pray IV> in addName "Show Keybindings" $ do
2023-09-30 19:22:51 +0200 <haskellbridge> <H​arry Pray IV> b <- liftIO $ doesFileExist filename
2023-09-30 19:22:52 +0200 <haskellbridge> <H​arry Pray IV> unless b $ liftIO (writeFile filename (unlines $ showKm xs))
2023-09-30 19:22:54 +0200 <haskellbridge> <H​arry Pray IV> spawnOn webWs $ command filename -- show dialog on webWs
2023-09-30 19:22:55 +0200 <haskellbridge> <H​arry Pray IV> windows $ W.greedyView webWs -- switch to webWs
2023-09-30 19:22:56 +0200 <haskellbridge> <H​arry Pray IV> ```
2023-09-30 19:33:18 +0200 <haskellbridge> <H​arry Pray IV> hiding in plain sight in my config!
2023-09-30 19:33:20 +0200 <haskellbridge> <H​arry Pray IV> 🤣
2023-09-30 19:39:43 +0200 <haskellbridge> <H​arry Pray IV> https://github.com/harryprayiv/nix-config/blob/57cb9cc1309af380d495873adc7572b0fed01742/home/progr…
2023-09-30 19:53:24 +0200 <haskellbridge> <H​arry Pray IV> I had been manually adding new shortcuts without realizing that he had provided an interface for it.
2023-09-30 20:26:34 +0200jabuxas(~jabuxas@user/jabuxas)
2023-09-30 21:46:01 +0200 <haskellbridge> <g​alactic_starfish> Have we as a project considered placing a monetary bounty on Wayland support?
2023-09-30 21:48:13 +0200 <haskellbridge> <g​alactic_starfish> I'd be happy to set aside some ca$h from my paycheck to a bounty fund to get this done sometime
2023-09-30 21:48:37 +0200 <haskellbridge> <g​alactic_starfish> Gaming on X11 is getting increasingly buggier
2023-09-30 21:50:36 +0200 <geekosaur> I still think that's what we should apply our OC money to, but there seems no consensus to do so
2023-09-30 22:07:46 +0200jabuxas(~jabuxas@user/jabuxas) (Remote host closed the connection)
2023-09-30 22:51:01 +0200 <liskin> Well, I don't disagree
2023-09-30 22:51:53 +0200 <liskin> It's just that we probably need some admin/mentor/etc. to oversee the effort
2023-09-30 22:53:00 +0200 <liskin> Right now we don't even have the "manpower" to communicate what we want :-(