| 2023-12-16 02:41:26 +0100 | dysthesis | (~dysthesis@user/dysthesis) |
| 2023-12-16 02:53:23 +0100 | dysthesis | (~dysthesis@user/dysthesis) (Remote host closed the connection) |
| 2023-12-16 02:53:49 +0100 | dysthesis | (~dysthesis@user/dysthesis) |
| 2023-12-16 03:34:05 +0100 | arkoinad | (~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 240 seconds) |
| 2023-12-16 03:34:06 +0100 | dysthesis | (~dysthesis@user/dysthesis) (Remote host closed the connection) |
| 2023-12-16 03:34:35 +0100 | dysthesis | (~dysthesis@user/dysthesis) |
| 2023-12-16 03:58:56 +0100 | <liskin> | Silly question, but… have people previously complained that restarting a browser doesn't shift windows to their original workspaces? |
| 2023-12-16 04:00:06 +0100 | <liskin> | I've somehow thought it isn't easy to do, for all these years, but it's like 6 lines of code or something :-D |
| 2023-12-16 04:01:23 +0100 | <geekosaur> | have you tried to id those windows? |
| 2023-12-16 04:01:47 +0100 | <liskin> | It's just a matter of making a managehook that looks at _NET_WM_DESKTOP |
| 2023-12-16 04:01:57 +0100 | <liskin> | I'm just totally confused why it hasn't been done before |
| 2023-12-16 04:02:04 +0100 | <liskin> | (as in - isn't in contrib) |
| 2023-12-16 04:03:22 +0100 | <liskin> | (I'll submit a PR later) |
| 2023-12-16 04:32:49 +0100 | td_ | (~td@i53870901.versanet.de) (Ping timeout: 256 seconds) |
| 2023-12-16 04:34:22 +0100 | td_ | (~td@i53870901.versanet.de) |
| 2023-12-16 04:55:39 +0100 | dysthesis | (~dysthesis@user/dysthesis) (Quit: dysthesis) |
| 2023-12-16 08:22:26 +0100 | thunderrd | (~thunderrd@183.182.110.187) |
| 2023-12-16 08:27:13 +0100 | thunderrd | (~thunderrd@183.182.110.187) (Remote host closed the connection) |
| 2023-12-16 08:54:44 +0100 | alp__ | (~alp@2001:861:e3d6:8f80:5927:5ec3:fb09:589c) |
| 2023-12-16 10:20:21 +0100 | alp__ | (~alp@2001:861:e3d6:8f80:5927:5ec3:fb09:589c) (Ping timeout: 268 seconds) |
| 2023-12-16 10:34:23 +0100 | alp__ | (~alp@2001:861:e3d6:8f80:5871:e261:32c:c3e7) |
| 2023-12-16 10:58:48 +0100 | Nixkernal | (~Nixkernal@115.16.194.178.dynamic.wline.res.cust.swisscom.ch) (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) |
| 2023-12-16 11:01:18 +0100 | gypsydanger | (dc7b3a1c5c@irc.cheogram.com) (Ping timeout: 260 seconds) |
| 2023-12-16 11:01:55 +0100 | gypsydanger | (dc7b3a1c5c@irc.cheogram.com) |
| 2023-12-16 11:03:59 +0100 | Nixkernal | (~Nixkernal@115.16.194.178.dynamic.wline.res.cust.swisscom.ch) |
| 2023-12-16 11:08:30 +0100 | Nixkernal | (~Nixkernal@115.16.194.178.dynamic.wline.res.cust.swisscom.ch) (Client Quit) |
| 2023-12-16 11:14:24 +0100 | Nixkernal | (~Nixkernal@115.16.194.178.dynamic.wline.res.cust.swisscom.ch) |
| 2023-12-16 12:22:40 +0100 | Nixkernal | (~Nixkernal@115.16.194.178.dynamic.wline.res.cust.swisscom.ch) (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) |
| 2023-12-16 12:23:00 +0100 | Nixkernal | (~Nixkernal@115.16.194.178.dynamic.wline.res.cust.swisscom.ch) |
| 2023-12-16 12:31:19 +0100 | alp__ | (~alp@2001:861:e3d6:8f80:5871:e261:32c:c3e7) (Ping timeout: 246 seconds) |
| 2023-12-16 12:49:41 +0100 | alp__ | (~alp@2001:861:e3d6:8f80:9e9a:65d5:880b:617e) |
| 2023-12-16 13:33:27 +0100 | h1y0s1lv3r | (~hiyosilve@p200300ed5f4d897c1baef3a8a7a85ad7.dip0.t-ipconnect.de) |
| 2023-12-16 13:35:17 +0100 | <h1y0s1lv3r> | Hello, good morning, I'm trying to recover an xmonad.hs configuration from 2014, but I'm getting errors that I don't know how to solve, sorry if I'm somewhat new to Haskell. Attached xmonad.hs and error capture; I don't have a better way to do it, sorry: CONFIG: https://paste.c-net.org/LiterClever ERROR: https://imgur.com/a/wW0tVLw Any help, pls? |
| 2023-12-16 13:44:31 +0100 | <[Leary]> | h1y0s1lv3r: <https://hackage.haskell.org/package/xmonad-0.17.2/changelog>, <https://hackage.haskell.org/package/xmonad-contrib-0.17.1/changelog> |
| 2023-12-16 13:45:32 +0100 | [Leary] | (~Leary]@user/Leary/x-0910699) (Remote host closed the connection) |
| 2023-12-16 13:45:46 +0100 | [Leary] | (~Leary]@user/Leary/x-0910699) |
| 2023-12-16 13:45:50 +0100 | <h1y0s1lv3r> | Ufs, thanks, a lot of changes and a lot of work Leary, maybe is good idea start with a new configuration... |
| 2023-12-16 13:46:09 +0100 | <[Leary]> | These changelogs can be considered migration guides. If you search for 'default' (a reasonable keyword based on your errors) in these, you'll get helpful hits; no need to start over. |
| 2023-12-16 13:47:01 +0100 | <h1y0s1lv3r> | Yes I see: Use of data-default allows using def where previously you had to write defaultConfig, defaultXPConfig, etc. |
| 2023-12-16 13:48:05 +0100 | <h1y0s1lv3r> | Let's try with def. |
| 2023-12-16 13:52:45 +0100 | <h1y0s1lv3r> | Yes, I need to start with empty xmonad.hs and go step by step, thanks anyway. Enjoy rest of the day. |
| 2023-12-16 13:55:10 +0100 | <h1y0s1lv3r> | Do we have templates updated to start with? pls |
| 2023-12-16 13:55:55 +0100 | <h1y0s1lv3r> | Will try with https://wiki.haskell.org/Xmonad/Config_archive |
| 2023-12-16 13:56:53 +0100 | <[Leary]> | Those configs are probably even older and more broken than yours. |
| 2023-12-16 13:57:45 +0100 | <h1y0s1lv3r> | Yes continues using from 2010 DefaultConfig omg. |
| 2023-12-16 13:58:14 +0100 | <h1y0s1lv3r> | Do we have somewhere templates updated? Leary |
| 2023-12-16 13:58:41 +0100 | <h1y0s1lv3r> | Could you share with me someone, pls? |
| 2023-12-16 13:58:49 +0100 | <[Leary]> | I don't think we've ever actually offered a template; it doesn't really make that sense for xmonad. A lot of work has been put into the tutorial, though: https://xmonad.org/TUTORIAL.html |
| 2023-12-16 13:59:06 +0100 | <h1y0s1lv3r> | Ok, will check, thanks Leary. |
| 2023-12-16 14:00:01 +0100 | <h1y0s1lv3r> | Leary, looks updated using 'main = xmonad $ def' but use xmobar, :( jiji, will try. |
| 2023-12-16 14:04:05 +0100 | Guest2 | (~Guest63@114.206.139.78) |
| 2023-12-16 14:06:20 +0100 | Guest2 | (~Guest63@114.206.139.78) (Client Quit) |
| 2023-12-16 14:11:01 +0100 | <h1y0s1lv3r> | Ok, must to exit to test new config. Will see :) |
| 2023-12-16 14:11:11 +0100 | h1y0s1lv3r | (~hiyosilve@p200300ed5f4d897c1baef3a8a7a85ad7.dip0.t-ipconnect.de) (Quit: Bye!) |
| 2023-12-16 14:26:49 +0100 | <Solid> | liskin: browsers are evil, so I think people just tend to accept when they misbehave :) |
| 2023-12-16 14:38:07 +0100 | alp__ | (~alp@2001:861:e3d6:8f80:9e9a:65d5:880b:617e) (Ping timeout: 268 seconds) |
| 2023-12-16 14:39:42 +0100 | <liskin> | Solid: :-D |
| 2023-12-16 14:40:48 +0100 | <liskin> | speaking of misbehaving, I had to do stringProperty "WM_WINDOW_ROLE" =? "browser" --> desktopHook, because otherwise cantata (gui for mpd) would try to restore itself to the last desktop if was on |
| 2023-12-16 14:41:00 +0100 | <liskin> | and I'm half-sure pavucontrol would do a similar thing too |
| 2023-12-16 14:41:47 +0100 | <liskin> | I quite like the fact these two remember the position (well, otherwise I'd add one line to manageHook, so, um, silly me), but I want them to just appear in front of me wherever I am |
| 2023-12-16 14:42:07 +0100 | <liskin> | anyway, off to the Santa Skate |
| 2023-12-16 14:42:42 +0100 | <liskin> | Solid: week's been busy so I may not manage to review the Cond stuff by tomorrow evening but it's in my "today" todo list :-) |
| 2023-12-16 14:44:27 +0100 | <Solid> | liskin: sounds great! :) |
| 2023-12-16 15:46:02 +0100 | <xmonadtrack> | New xmonad-contrib branch created: pull/850 (1 commit) https://github.com/xmonad/xmonad-contrib/pull/850 |
| 2023-12-16 15:46:51 +0100 | <Solid> | [Leary]: there is a better development workflow than having to push every change to a working commit, change the flake to that branch, nix flake update, remove all unwanted updates, and rebuilding… right? |
| 2023-12-16 17:09:26 +0100 | <[Leary]> | Solid: Yes, though it depends on precisely what you're doing. Not all changes necessarily need to be commited; iirc nix can still build a dirty worktree so long as the files are all tracked. Re `nix flake update`: instead of removing changes, do it pinpoint from the start with `nix flake lock --update-input _`. Of course, it's still a hassle and shouldn't be part of your tight-loop iteration; ideally you just let nix provide an environment that won't |
| 2023-12-16 17:09:27 +0100 | <[Leary]> | need to be rebuilt/restarted often and let less arcane tools handle the rest. |
| 2023-12-16 17:42:29 +0100 | ml| | (~ml|@user/ml/x-5298235) (Quit: WeeChat 4.0.5) |
| 2023-12-16 17:48:43 +0100 | alp__ | (~alp@2001:861:e3d6:8f80:908c:c2d9:53f8:9c71) |
| 2023-12-16 18:37:50 +0100 | todi | (~todi@p5dca55c4.dip0.t-ipconnect.de) (Quit: ZNC - https://znc.in) |
| 2023-12-16 19:04:58 +0100 | alp__ | (~alp@2001:861:e3d6:8f80:908c:c2d9:53f8:9c71) (Ping timeout: 256 seconds) |
| 2023-12-16 19:51:50 +0100 | <Solid> | [Leary]: I was mostly asking about e.g. trying to reproduce a bug. My usual way of doing this would be to copy the given config, pepper some traces all over contrib, recompile, and start xmonad within xephyr |
| 2023-12-16 19:55:35 +0100 | portnov | (~portnov@v-20678-unlim.vpn.mgn.ru) |
| 2023-12-16 21:02:24 +0100 | alp__ | (~alp@2001:861:e3d6:8f80:70a5:2518:c61b:a3f3) |
| 2023-12-16 21:17:13 +0100 | todi | (~todi@p5dca55c4.dip0.t-ipconnect.de) |
| 2023-12-16 21:59:02 +0100 | alp__ | (~alp@2001:861:e3d6:8f80:70a5:2518:c61b:a3f3) (Ping timeout: 268 seconds) |
| 2023-12-16 22:02:23 +0100 | <portnov> | https://i.ibb.co/LdpDS4h/Screenshot-20231217-020105.png sorry, could not stand it. Just too funny :) |
| 2023-12-16 22:02:49 +0100 | <portnov> | it's xmonad, if someone is in doubt. |
| 2023-12-16 22:21:35 +0100 | portnov | (~portnov@v-20678-unlim.vpn.mgn.ru) (Remote host closed the connection) |
