Logs: liberachat/#xmonad
| 2022-11-20 23:09:32 | × | hrberg quits (~quassel@171.79-160-161.customer.lyse.net) (Ping timeout: 246 seconds) |
| 2022-11-20 23:12:43 | → | hrberg joins (~quassel@171.79-160-161.customer.lyse.net) |
| 2022-11-20 23:36:34 | × | hrberg quits (~quassel@171.79-160-161.customer.lyse.net) (Ping timeout: 260 seconds) |
| 2022-11-20 23:54:46 | × | srz quits (~srz@181.228.49.93) (Ping timeout: 252 seconds) |
| 2022-11-20 23:55:48 | → | hrberg joins (~quassel@171.79-160-161.customer.lyse.net) |
| 2022-11-21 00:25:56 | → | mncheck joins (~mncheck@193.224.205.254) |
| 2022-11-21 00:26:55 | × | mncheck quits (~mncheck@193.224.205.254) (Remote host closed the connection) |
| 2022-11-21 01:05:40 | → | mvk joins (~mvk@2607:fea8:5ce3:8500::efb) |
| 2022-11-21 01:05:55 | × | mvk quits (~mvk@2607:fea8:5ce3:8500::efb) (Client Quit) |
| 2022-11-21 01:08:24 | <xmonadtrack> | New xmonad-contrib branch created: pull/781 (1 commit) https://github.com/xmonad/xmonad-contrib/pull/781 |
| 2022-11-21 01:32:44 | <liskin> | Uh wtf. The Firefox bug report is 7 years old, and full screen worked with Firefox for quite a while |
| 2022-11-21 01:33:51 | <liskin> | So rather than trying to get this new thing perfect, why don't we step back and figure out why suddenly Firefox doesn't work |
| 2022-11-21 01:33:59 | → | srz joins (~srz@181.228.49.93) |
| 2022-11-21 01:46:18 | <geekosaur> | I was wondering why FF would suddenly start caring when at tis point EWMH is basically DOA |
| 2022-11-21 01:46:25 | <geekosaur> | *this |
| 2022-11-21 02:20:06 | × | srz quits (~srz@181.228.49.93) (Remote host closed the connection) |
| 2022-11-21 03:03:39 | × | banc quits (banc@gateway/vpn/airvpn/banc) (Ping timeout: 260 seconds) |
| 2022-11-21 03:05:44 | × | td_ quits (~td@83.135.9.29) (Ping timeout: 256 seconds) |
| 2022-11-21 03:07:12 | → | td_ joins (~td@83.135.9.24) |
| 2022-11-21 03:24:09 | → | banc joins (banc@gateway/vpn/airvpn/banc) |
| 2022-11-21 03:42:24 | × | terrorjack quits (~terrorjac@2a01:4f8:1c1e:509a::1) (Quit: The Lounge - https://thelounge.chat) |
| 2022-11-21 03:45:00 | → | terrorjack joins (~terrorjac@2a01:4f8:1c1e:509a::1) |
| 2022-11-21 03:54:12 | → | noex joins (~null@user/noex) |
| 2022-11-21 04:02:47 | × | td_ quits (~td@83.135.9.24) (Ping timeout: 260 seconds) |
| 2022-11-21 04:04:14 | → | td_ joins (~td@83.135.9.7) |
| 2022-11-21 04:50:57 | → | DangerBird joins (~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) |
| 2022-11-21 04:51:28 | × | DangerBird quits (~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) (Client Quit) |
| 2022-11-21 04:57:11 | → | DangerBird joins (~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) |
| 2022-11-21 04:57:52 | × | DangerBird quits (~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) (Client Quit) |
| 2022-11-21 04:58:35 | → | DangerBird joins (~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) |
| 2022-11-21 04:58:48 | × | DangerBird quits (~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) (Remote host closed the connection) |
| 2022-11-21 04:59:17 | → | DangerBird joins (~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) |
| 2022-11-21 04:59:45 | × | DangerBird quits (~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) (Remote host closed the connection) |
| 2022-11-21 05:00:32 | → | DangerBird joins (~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) |
| 2022-11-21 05:00:55 | × | DangerBird quits (~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) (Remote host closed the connection) |
| 2022-11-21 05:02:25 | → | DangerBird joins (~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) |
| 2022-11-21 05:03:49 | × | DangerBird quits (~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) (Remote host closed the connection) |
| 2022-11-21 05:10:37 | → | DangerBird joins (~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) |
| 2022-11-21 05:10:52 | × | DangerBird quits (~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) (Remote host closed the connection) |
| 2022-11-21 06:42:45 | × | jao quits (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 260 seconds) |
| 2022-11-21 08:19:18 | × | ft quits (~ft@p508dbd59.dip0.t-ipconnect.de) (Quit: leaving) |
| 2022-11-21 08:46:34 | → | cfricke joins (~cfricke@user/cfricke) |
| 2022-11-21 11:05:23 | × | mightybyte quits (~mightybyt@ec2-52-201-220-249.compute-1.amazonaws.com) (Read error: Software caused connection abort) |
| 2022-11-21 11:05:38 | → | mightybyte joins (~mightybyt@ec2-52-201-220-249.compute-1.amazonaws.com) |
| 2022-11-21 13:39:03 | → | thunderrd joins (~thunderrd@183.182.110.138) |
| 2022-11-21 14:27:54 | <kora9> | Hmm. I've set Xmessage*font (to the proper font/size) in .Xresources but xmonad error logs still shows up with too small a font size. Running `xmessage test` in a terminal shows the font size I set just fine. I `xrdb -merge .Xresources` before `exec xmonad` in my .xinitrc -- any ideas what the issue is? |
| 2022-11-21 14:30:59 | → | srz joins (~srz@181.228.49.93) |
| 2022-11-21 14:37:06 | <geekosaur> | xmonad passes an explicit fontset on the command line; see https://github.com/xmonad/xmonad/blob/master/src/XMonad/Core.hs#L463 |
| 2022-11-21 14:39:06 | <kora9> | geekosaur: That explains a lot! To modify this behaviour, do I just copy that section into my config and modify it? |
| 2022-11-21 14:39:38 | <geekosaur> | there is, sadly, no good way to handle this in general; we need to specify a fontset so it gets the right i18n behavior, but then it also fixes the font size |
| 2022-11-21 14:39:59 | <geekosaur> | this is why newer stuff uses fontconfig instead |
| 2022-11-21 14:40:30 | <geekosaur> | you would have to copy the whole recompile logic, I think 😞 |
| 2022-11-21 14:41:03 | <kora9> | geekosaur: jeez! This is the first time I've run into a limitation in Xmonad's config I think :) I guess it was bound to happen sooner or later |
| 2022-11-21 14:41:39 | <geekosaur> | well, it's not a complete loss; you can ignore the xmessage and look in xmonad.errors afterward |
| 2022-11-21 14:42:36 | <geekosaur> | we should really consider upgrading to a better message display at some point; we used xmessage because when xmonad was written it was the only message program guaranteed to be installed, but these days that's no longer true |
| 2022-11-21 14:43:22 | <Solid[m]> | liskin: mh, are we sure there _is_ a problem with firefox fullscreen? Maybe they just used that as an example to give their PR more weight |
| 2022-11-21 14:43:38 | × | cfricke quits (~cfricke@user/cfricke) (Quit: WeeChat 3.7.1) |
| 2022-11-21 14:43:52 | <Solid[m]> | In https://github.com/xmonad/xmonad-contrib/issues/771 they talked about needing those changes for an application of theirs, so maybe this PR is similar |
| 2022-11-21 14:45:59 | <kora9> | geekosaur: Yeah, the issue I'm having with xmessage is that I'm on a high DPI display so I have to use xrandr dpi/scale workarounds to get a proper size, which unfortunately means I need to modify the fonts in the applications instead |
| 2022-11-21 14:46:55 | <kora9> | If xmonad switched to an application that respected the dpi setting it wouldn't be as much of an issue |
| 2022-11-21 14:49:29 | <geekosaur> | I personally use a wrapper for zenity, which has its shortcomings but I expect it would respect dpi. https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmessage |
| 2022-11-21 14:50:03 | <kora9> | geekosaur, thanks! I'll give that a try :) |
| 2022-11-21 14:50:09 | <geekosaur> | just noticed I could simplify things too, there's an XMONAD_XMESSAGE envar 🙂 but it still has to accept xmessage-style parameters so you can't just set it to zenity |
| 2022-11-21 14:55:47 | <kora9> | geekosaur: Does that env var accept xmessage -fn for font size? |
| 2022-11-21 14:56:24 | <geekosaur> | no, it still passes the fontset which overrides the font size |
| 2022-11-21 14:56:39 | <kora9> | argh :) |
| 2022-11-21 15:08:02 | → | Ehllie joins (~Thunderbi@217-67-208-66.itsa.net.pl) |
| 2022-11-21 15:24:30 | × | Ehllie quits (~Thunderbi@217-67-208-66.itsa.net.pl) (Ping timeout: 240 seconds) |
| 2022-11-21 15:34:03 | → | Ehllie joins (~Thunderbi@217-67-208-66.itsa.net.pl) |
| 2022-11-21 15:46:34 | × | Ehllie quits (~Thunderbi@217-67-208-66.itsa.net.pl) (Ping timeout: 268 seconds) |
| 2022-11-21 15:46:57 | → | srk- joins (~sorki@user/srk) |
| 2022-11-21 15:49:29 | → | clu joins (~clu@user/varjax) |
| 2022-11-21 15:50:12 | × | srk quits (~sorki@user/srk) (Ping timeout: 248 seconds) |
| 2022-11-21 15:50:12 | srk- | is now known as srk |
| 2022-11-21 15:58:58 | <kora9> | geekosaur: How do you use your xmessage wrapper? Do you replace the system-wide binary with it? I've tried sticking it in my $HOME/.local/bin and setting XMONAD_XMESSAGE="/.local/bin/xmessage" but that didn't work (Sorry, I'm not extremely knowledgable) |
| 2022-11-21 16:00:22 | × | elpfen[m] quits (~elpfenmat@2001:470:69fc:105::2:a75f) (Quit: You have been kicked for being idle) |
| 2022-11-21 16:09:56 | <geekosaur> | I currently stick it somewhere in front of /usr/bin in $PATH, but if you use XMONAD_XMESSAGE you need to (a) make sure the new xmessage is executable (chmod +x) and (b) use a full path to it in XMONAD_XMESSAGE |
| 2022-11-21 16:10:15 | <geekosaur> | what you have is not a full path, there is probably no /.local on your system |
| 2022-11-21 16:10:46 | <geekosaur> | /home/kora9/.local/bin/xmessage (or whatever your username is in place of kora9) |
| 2022-11-21 16:29:09 | <kora9> | geekosaur: Ah, yeah I mistyped on the path. I used "$HOME/.local/bin/xmessage" -- but xmonad is still using regular xmessage for some reason |
| 2022-11-21 16:29:37 | <kora9> | echo $XMONAD_XMESSAGE returns "/home/kora9/.local/bin/xmessage" |
| 2022-11-21 16:29:57 | <kora9> | I put it next to my other XMONAD vars which works |
| 2022-11-21 16:30:58 | × | srz quits (~srz@181.228.49.93) (Ping timeout: 256 seconds) |
| 2022-11-21 16:34:22 | <geekosaur> | hm. it'll do that if it doesn't understand the parameters passed to it, so it doesn't break non-xmonad uses of xmessage, but it should work for that |
| 2022-11-21 16:35:30 | <geekosaur> | whoops, I was going to do a quick test but it's recompiling everything instead… |
| 2022-11-21 16:35:58 | <geekosaur> | (my test might not work anyway as I use a build script and cabal, and cabal sends output to the wrong place) |
| 2022-11-21 16:37:09 | <kora9> | geekosaur: Ah, I'm just intentionally making an error in my xmonad.hs and reloading to test the xmessage error prompt |
| 2022-11-21 16:37:27 | <geekosaur> | yeh, I did the same |
| 2022-11-21 16:37:44 | <geekosaur> | but my setup is a lot more complex |
| 2022-11-21 16:39:55 | <geekosaur> | in particular, I use dbus to log to mate-panel and dbus depends on both conduit and lens so I have half of hackage as dependencies 🙂 |
| 2022-11-21 16:44:17 | <kora9> | geekosaur: Cool, so you use mate-panel instead of the more common panels (xmobar etc)? Got any screenshots? |
| 2022-11-21 16:44:59 | <geekosaur> | I run xmonad as window manager for MATE, and maintain the support for it |
| 2022-11-21 16:46:14 | <geekosaur> | https://imgur.com/VhaT5Fz.png |
| 2022-11-21 16:48:00 | <kora9> | geekosaur: That's pretty neat! Why do you do that? Are there any advantages vs something like xmobar? |
| 2022-11-21 16:48:22 | → | jao joins (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-11-21 16:51:50 | × | ml| quits (~ml|@user/ml/x-5298235) (Ping timeout: 268 seconds) |
| 2022-11-21 17:00:19 | <geekosaur> | I just prefer having a full desktop environment including panel |
| 2022-11-21 17:00:31 | <geekosaur> | and I'm not particularly fond of xmobar |
| 2022-11-21 17:00:42 | × | gknux quits (~gknux@user/galaxy-knuckles/x-3015990) (Quit: ....and i am outta here....) |
| 2022-11-21 17:01:18 | <geekosaur> | also my build just finished and my xmessagte fell back to the standard one, so apparently I need to adjust the parameter checking again, sorry 😞 |
All times are in UTC.