Logs on 2026-03-10 (liberachat/#xmonad)
| 01:25:26 | ← | stackdroid18 parts (~stackdroi@user/stackdroid) () |
| 03:23:06 | → | thunderrd joins (~thunderrd@1.4.183.228) |
| 03:52:58 | <haskellbridge> | <iqubic (she/her)> Where does the XMobar Battery Module get its data? |
| 03:56:56 | <haskellbridge> | <iqubic (she/her)> Oh speaking of programs doing weird things... When boot up my computer and launch a NamedScratchPad for Emacs, the first time the window opens, it goes off the screen to the right, but if I kill that and then spawn the emacs scratchpad again, things just work. |
| 03:58:09 | <geekosaur> | the simple one uses a fixed list of places to search under `/sys/class/power_supply`. `BatteryP` lets you specify places to look |
| 04:02:24 | <haskellbridge> | <iqubic (she/her)> Here's the relevant section of my config for scratchpads. https://dpaste.alwaysdata.org/k8miJiND |
| 04:03:14 | <haskellbridge> | <iqubic (she/her)> Do you have any idea why the emacs scratchpad get the wrong dimensions the very first time XMonad spawns that window, but not any other times? |
| 04:04:33 | <haskellbridge> | <iqubic (she/her)> Actually this is a better thing to look at, where I actually get the quote marks correct to end the string properly. https://dpaste.alwaysdata.org/031Nwq4M |
| 04:06:12 | <haskellbridge> | <iqubic (she/her)> customFloating is from X.U.NamedScratchpads |
| 06:15:20 | × | vados quits (~vados@46-133-51-198.mobile.vf-ua.net) (Read error: Connection reset by peer) |
| 06:20:55 | → | vados joins (~vados@46-133-184-159.mobile.vf-ua.net) |
| 08:11:38 | × | jusa quits (~jusa@kraa.fi) (Quit: WeeChat 4.8.1) |
| 08:12:49 | → | jusa joins (~jusa@kraa.fi) |
| 08:35:43 | × | thunderrd quits (~thunderrd@1.4.183.228) (Ping timeout: 264 seconds) |
| 08:48:32 | → | thunderrd joins (~thunderrd@113.53.55.165) |
| 11:38:58 | × | gwentpl quits (~gwpl@user/gwentpl) (Quit: ZNC 1.10.1 - https://znc.in) |
| 11:39:39 | → | gwentpl joins (~gwpl@user/gwentpl) |
| 16:05:38 | → | Guest59 joins (~Guest59@31.205.126.187) |
| 16:06:03 | <Guest59> | does xmonad have a future? |
| 16:06:42 | <Guest59> | cause it seems like porting to wayland is pretty hard and X11 will stop being maintained at some point |
| 16:12:12 | <geekosaur> | there's already a maintained fork, although it's not quite trusted by a number of people. also there are enhancemeents to and wrappers for xwayland to enable x11 window managers |
| 16:12:45 | <geekosaur> | and a lot of people who still can't use wayland for various reasons, no matter how badly deadrat wants to force them into it |
| 16:12:59 | <Guest59> | Yeah I don't want to use wayland either |
| 16:13:05 | <Guest59> | but at some point we might be forced to |
| 16:14:12 | <geekosaur> | I am also monitoring some new developments in wayland haskell bindings (being discussed on the fp discord) that might get "xmonad-for-wayland" unstuck. we can hope |
| 16:14:21 | <Guest59> | what's the fork? isn't waymonad dead |
| 16:16:12 | <geekosaur> | no, not an xmonad fork, an X11 fork |
| 16:16:34 | <Guest59> | oh I did see that |
| 16:17:15 | <Guest59> | yeah I mean idk if long term using X11 is going to be viable |
| 16:17:25 | <geekosaur> | I think the biggest problem with the xmonad-for-wayland efforts at this point is everyone's been focusing on wlroots as the bones of a compositor, but (a) that's never managed to go anywhere (b) I think we're finding out why the KDE folks considered adopting it and then dropped it |
| 16:17:34 | <geekosaur> | but there are some alternatives now |
| 16:17:37 | <Guest59> | like I'm not sure exactly what packages depends on it, like most packages should be pretty agnostic right? |
| 16:18:13 | <geekosaur> | X11 has a well defined protocol, anything that supports the protocol will work with a fork |
| 16:18:22 | <Guest59> | like are most normal applications explicitly interacting with X11 somehow |
| 16:19:49 | <Guest59> | yeah I'm just not really aware of the details, for example does Firefox have code specifically made for it to work for X11 or is that handled separately somehow? |
| 16:20:28 | <geekosaur> | that level of code is almost always delegated to UI toolkits (gtk, qt) |
| 16:21:12 | <geekosaur> | the upcoming problem is that gtk is dropping x11 support, and that will affect everything based on it including firefox |
| 16:21:50 | <geekosaur> | but I imagine someone will fork it (again: MATE already did, IIRC, but it's stuck at gtk2 I think) |
| 16:22:42 | <geekosaur> | also some folks have already migrated to qt/kde because of past gtk support issues, and more may do so to retain compatibility |
| 16:22:48 | <Guest59> | right, that's crazy for gtk to drop support already |
| 16:23:22 | <Guest59> | I think they're actively trying to get ppl to go to wayland for some reason |
| 16:23:43 | <geekosaur> | they absolutely are |
| 16:23:51 | <geekosaur> | and have said so quite clearly |
| 16:24:09 | <Guest59> | idk what their problem is |
| 16:24:25 | <geekosaur> | which is angering a lot of people, because not only are there many who don't want to move, there are still many who can't |
| 16:25:10 | <geekosaur> | there are still a decent number of things that don't work in wayland yet |
| 16:25:26 | <geekosaur> | …that said, there are a bunch of things that can't be made to work right in x11 |
| 16:25:31 | <Guest59> | yeah I mean x11 just works |
| 16:26:06 | <Guest59> | I mostly really don't want to switch wm |
| 16:27:55 | <geekosaur> | its whole architecture is designed for 1980s engineering workstations where every display had its own framebuffer card (see x11's Screen), so a really ugly hack is needed for multiple displays on PC-style video cards and that hack + ancient protocol means different resolutions on different displays can't be made to work without a protocol overhaul to plumb screen information through to places that currently can't get it, like client side font |
| 16:27:56 | <geekosaur> | rendering |
| 16:28:49 | <geekosaur> | (the really annoying thing is that wayland's design _can_ support that but I think still doesn't) |
| 16:29:11 | <Guest59> | yeah but as a result of that u can do fun stuff like ssh -x |
| 16:29:56 | <geekosaur> | you could do that just as well with wayland, the problem there is about security |
| 16:30:20 | <Guest59> | uh I didn't know that |
| 16:30:46 | <geekosaur> | and tbh wayland's pretty much right there, it's really hard to configure X11 to block password scraping for example |
| 16:31:15 | <haskellbridge> | <ijouw> There are other niche things like input visualisation, which are not supported by design (last I checked). |
| 16:32:16 | <haskellbridge> | <ijouw> Those programs (ab)use those same features that may be undesirable for security. |
| 16:40:18 | → | Digitteknohippie joins (~user@user/digit) |
| 16:40:36 | × | Digit quits (~user@user/digit) (Ping timeout: 264 seconds) |
| 16:40:52 | × | Guest59 quits (~Guest59@31.205.126.187) (Quit: Client closed) |
| 16:47:06 | × | Digitteknohippie quits (~user@user/digit) (Ping timeout: 255 seconds) |
| 16:48:54 | × | thunderrd quits (~thunderrd@113.53.55.165) (Remote host closed the connection) |
| 17:45:05 | × | tv quits (~tv@user/tv) (Read error: Connection reset by peer) |
| 18:19:51 | × | kaskal quits (~kaskal@2a02:8388:1a8b:7d00:6457:882b:213f:f9cd) (Quit: ZNC - https://znc.in) |
| 18:20:09 | → | kaskal joins (~kaskal@84-115-235-223.cable.dynamic.surfer.at) |
| 18:36:51 | → | Guest59 joins (~Guest59@31.205.126.187) |
| 18:37:41 | × | Guest59 quits (~Guest59@31.205.126.187) (Client Quit) |
| 19:35:55 | → | tv joins (~tv@user/tv) |
| 19:42:27 | × | vados quits (~vados@46-133-184-159.mobile.vf-ua.net) (Quit: WeeChat 4.7.1) |
| 19:46:26 | → | vados joins (~vados@46-133-184-159.mobile.vf-ua.net) |
| 20:14:40 | → | ChubaDuba joins (~ChubaDuba@37.112.225.102) |
| 21:06:13 | → | Digitteknohippie joins (~user@user/digit) |
| 21:36:29 | Digitteknohippie | is now known as Digit |
| 22:00:59 | → | stackdroid18 joins (~stackdroi@user/stackdroid) |
| 22:01:50 | × | ChubaDuba quits (~ChubaDuba@37.112.225.102) (Quit: WeeChat 4.8.1) |
All times are in UTC on 2026-03-10.