IRCBrowse

2022/11/21

2022-11-21 00:09:32 +0100hrberg(~quassel@171.79-160-161.customer.lyse.net) (Ping timeout: 246 seconds)
2022-11-21 00:12:43 +0100hrberg(~quassel@171.79-160-161.customer.lyse.net)
2022-11-21 00:36:34 +0100hrberg(~quassel@171.79-160-161.customer.lyse.net) (Ping timeout: 260 seconds)
2022-11-21 00:54:46 +0100srz(~srz@181.228.49.93) (Ping timeout: 252 seconds)
2022-11-21 00:55:48 +0100hrberg(~quassel@171.79-160-161.customer.lyse.net)
2022-11-21 01:25:56 +0100mncheck(~mncheck@193.224.205.254)
2022-11-21 01:26:55 +0100mncheck(~mncheck@193.224.205.254) (Remote host closed the connection)
2022-11-21 02:05:40 +0100mvk(~mvk@2607:fea8:5ce3:8500::efb)
2022-11-21 02:05:55 +0100mvk(~mvk@2607:fea8:5ce3:8500::efb) (Client Quit)
2022-11-21 02:08:24 +0100 <xmonadtrack> New xmonad-contrib branch created: pull/781 (1 commit) https://github.com/xmonad/xmonad-contrib/pull/781
2022-11-21 02:32:44 +0100 <liskin> Uh wtf. The Firefox bug report is 7 years old, and full screen worked with Firefox for quite a while
2022-11-21 02:33:51 +0100 <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 02:33:59 +0100srz(~srz@181.228.49.93)
2022-11-21 02:46:18 +0100 <geekosaur> I was wondering why FF would suddenly start caring when at tis point EWMH is basically DOA
2022-11-21 02:46:25 +0100 <geekosaur> *this
2022-11-21 03:20:06 +0100srz(~srz@181.228.49.93) (Remote host closed the connection)
2022-11-21 04:03:39 +0100banc(banc@gateway/vpn/airvpn/banc) (Ping timeout: 260 seconds)
2022-11-21 04:05:44 +0100td_(~td@83.135.9.29) (Ping timeout: 256 seconds)
2022-11-21 04:07:12 +0100td_(~td@83.135.9.24)
2022-11-21 04:24:09 +0100banc(banc@gateway/vpn/airvpn/banc)
2022-11-21 04:42:24 +0100terrorjack(~terrorjac@2a01:4f8:1c1e:509a::1) (Quit: The Lounge - https://thelounge.chat)
2022-11-21 04:45:00 +0100terrorjack(~terrorjac@2a01:4f8:1c1e:509a::1)
2022-11-21 04:54:12 +0100noex(~null@user/noex)
2022-11-21 05:02:47 +0100td_(~td@83.135.9.24) (Ping timeout: 260 seconds)
2022-11-21 05:04:14 +0100td_(~td@83.135.9.7)
2022-11-21 05:50:57 +0100DangerBird(~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu)
2022-11-21 05:51:28 +0100DangerBird(~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) (Client Quit)
2022-11-21 05:57:11 +0100DangerBird(~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu)
2022-11-21 05:57:52 +0100DangerBird(~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) (Client Quit)
2022-11-21 05:58:35 +0100DangerBird(~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu)
2022-11-21 05:58:48 +0100DangerBird(~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) (Remote host closed the connection)
2022-11-21 05:59:17 +0100DangerBird(~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu)
2022-11-21 05:59:45 +0100DangerBird(~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) (Remote host closed the connection)
2022-11-21 06:00:32 +0100DangerBird(~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu)
2022-11-21 06:00:55 +0100DangerBird(~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) (Remote host closed the connection)
2022-11-21 06:02:25 +0100DangerBird(~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu)
2022-11-21 06:03:49 +0100DangerBird(~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) (Remote host closed the connection)
2022-11-21 06:10:37 +0100DangerBird(~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu)
2022-11-21 06:10:52 +0100DangerBird(~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) (Remote host closed the connection)
2022-11-21 07:42:45 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 260 seconds)
2022-11-21 09:19:18 +0100ft(~ft@p508dbd59.dip0.t-ipconnect.de) (Quit: leaving)
2022-11-21 09:46:34 +0100cfricke(~cfricke@user/cfricke)
2022-11-21 12:05:23 +0100mightybyte(~mightybyt@ec2-52-201-220-249.compute-1.amazonaws.com) (Read error: Software caused connection abort)
2022-11-21 12:05:38 +0100mightybyte(~mightybyt@ec2-52-201-220-249.compute-1.amazonaws.com)
2022-11-21 14:39:03 +0100thunderrd(~thunderrd@183.182.110.138)
2022-11-21 15:27:54 +0100 <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 15:30:59 +0100srz(~srz@181.228.49.93)
2022-11-21 15:37:06 +0100 <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 15:39:06 +0100 <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 15:39:38 +0100 <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 15:39:59 +0100 <geekosaur> this is why newer stuff uses fontconfig instead
2022-11-21 15:40:30 +0100 <geekosaur> you would have to copy the whole recompile logic, I think 😞
2022-11-21 15:41:03 +0100 <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 15:41:39 +0100 <geekosaur> well, it's not a complete loss; you can ignore the xmessage and look in xmonad.errors afterward
2022-11-21 15:42:36 +0100 <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 15:43:22 +0100 <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 15:43:38 +0100cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.7.1)
2022-11-21 15:43:52 +0100 <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 15:45:59 +0100 <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 15:46:55 +0100 <kora9> If xmonad switched to an application that respected the dpi setting it wouldn't be as much of an issue
2022-11-21 15:49:29 +0100 <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 15:50:03 +0100 <kora9> geekosaur, thanks! I'll give that a try :)
2022-11-21 15:50:09 +0100 <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 15:55:47 +0100 <kora9> geekosaur: Does that env var accept xmessage -fn for font size?
2022-11-21 15:56:24 +0100 <geekosaur> no, it still passes the fontset which overrides the font size
2022-11-21 15:56:39 +0100 <kora9> argh :)
2022-11-21 16:08:02 +0100Ehllie(~Thunderbi@217-67-208-66.itsa.net.pl)
2022-11-21 16:24:30 +0100Ehllie(~Thunderbi@217-67-208-66.itsa.net.pl) (Ping timeout: 240 seconds)
2022-11-21 16:34:03 +0100Ehllie(~Thunderbi@217-67-208-66.itsa.net.pl)
2022-11-21 16:46:34 +0100Ehllie(~Thunderbi@217-67-208-66.itsa.net.pl) (Ping timeout: 268 seconds)
2022-11-21 16:46:57 +0100srk-(~sorki@user/srk)
2022-11-21 16:49:29 +0100clu(~clu@user/varjax)
2022-11-21 16:50:12 +0100srk(~sorki@user/srk) (Ping timeout: 248 seconds)
2022-11-21 16:50:12 +0100srk-srk
2022-11-21 16:58:58 +0100 <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 17:00:22 +0100elpfen[m](~elpfenmat@2001:470:69fc:105::2:a75f) (Quit: You have been kicked for being idle)
2022-11-21 17:09:56 +0100 <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 17:10:15 +0100 <geekosaur> what you have is not a full path, there is probably no /.local on your system
2022-11-21 17:10:46 +0100 <geekosaur> /home/kora9/.local/bin/xmessage (or whatever your username is in place of kora9)
2022-11-21 17:29:09 +0100 <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 17:29:37 +0100 <kora9> echo $XMONAD_XMESSAGE returns "/home/kora9/.local/bin/xmessage"
2022-11-21 17:29:57 +0100 <kora9> I put it next to my other XMONAD vars which works
2022-11-21 17:30:58 +0100srz(~srz@181.228.49.93) (Ping timeout: 256 seconds)
2022-11-21 17:34:22 +0100 <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 17:35:30 +0100 <geekosaur> whoops, I was going to do a quick test but it's recompiling everything instead…
2022-11-21 17:35:58 +0100 <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 17:37:09 +0100 <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 17:37:27 +0100 <geekosaur> yeh, I did the same
2022-11-21 17:37:44 +0100 <geekosaur> but my setup is a lot more complex
2022-11-21 17:39:55 +0100 <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 17:44:17 +0100 <kora9> geekosaur: Cool, so you use mate-panel instead of the more common panels (xmobar etc)? Got any screenshots?
2022-11-21 17:44:59 +0100 <geekosaur> I run xmonad as window manager for MATE, and maintain the support for it
2022-11-21 17:46:14 +0100 <geekosaur> https://imgur.com/VhaT5Fz.png
2022-11-21 17:48:00 +0100 <kora9> geekosaur: That's pretty neat! Why do you do that? Are there any advantages vs something like xmobar?
2022-11-21 17:48:22 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-11-21 17:51:50 +0100ml|(~ml|@user/ml/x-5298235) (Ping timeout: 268 seconds)
2022-11-21 18:00:19 +0100 <geekosaur> I just prefer having a full desktop environment including panel
2022-11-21 18:00:31 +0100 <geekosaur> and I'm not particularly fond of xmobar
2022-11-21 18:00:42 +0100gknux(~gknux@user/galaxy-knuckles/x-3015990) (Quit: ....and i am outta here....)
2022-11-21 18:01:18 +0100 <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 😞
2022-11-21 18:02:12 +0100 <kora9> geekosaur: np :)
2022-11-21 18:02:13 +0100gknux(~gknux@user/galaxy-knuckles/x-3015990)
2022-11-21 18:02:45 +0100gknux(~gknux@user/galaxy-knuckles/x-3015990) (Remote host closed the connection)
2022-11-21 18:03:04 +0100 <geekosaur> ironically, it seems to be the fontset it's falling over on
2022-11-21 18:05:49 +0100gknux(~gknux@user/galaxy-knuckles/x-3015990)
2022-11-21 18:06:57 +0100 <geekosaur> typo, it seems, I was looking for "fontset" but it's "fontSet"
2022-11-21 18:07:54 +0100gknux(~gknux@user/galaxy-knuckles/x-3015990) (Client Quit)
2022-11-21 18:09:27 +0100 <geekosaur> okay, I just pushed it after verifying it runs zenity. I may need to adjust a bit more though as it comes up really narrow
2022-11-21 18:09:30 +0100gknux(~gknux@user/galaxy-knuckles/x-3015990)
2022-11-21 18:10:08 +0100 <geekosaur> oh, I don't set the width, so it's something zenity is doing. sigh
2022-11-21 18:10:29 +0100 <geekosaur> at one point I was computing a width but that was nonviable as I had to guess at the font width
2022-11-21 18:12:12 +0100 <kora9> geekosaur: Cool, I'll check it out in a bit :)
2022-11-21 18:25:00 +0100srz(~srz@181.228.49.93)
2022-11-21 19:00:26 +0100 <liskin> Solid[m]: of course we're not sure, that's my whole point
2022-11-21 19:00:53 +0100 <liskin> But I've been away from a laptop for ages so can't really write a meaningful comment there
2022-11-21 19:26:45 +0100Ehllie(~Thunderbi@79.184.239.57.ipv4.supernova.orange.pl)
2022-11-21 19:31:06 +0100Ehllie(~Thunderbi@79.184.239.57.ipv4.supernova.orange.pl) (Ping timeout: 256 seconds)
2022-11-21 19:40:05 +0100diep(~diep@2a01:cb11:2d7:4a00:b230:54de:5188:7aeb)
2022-11-21 20:25:35 +0100zawaken(~zawaken@user/zawaken) (Quit: ZNC - https://znc.in)
2022-11-21 20:27:16 +0100zawaken(~zawaken@user/zawaken)
2022-11-21 20:29:30 +0100 <kora9> geekosaur: Hmm, grabbed your latest xmessage and it's now not displaying anything at all (no zenity or xmessage fallback)
2022-11-21 20:31:27 +0100diep(~diep@2a01:cb11:2d7:4a00:b230:54de:5188:7aeb) (Ping timeout: 260 seconds)
2022-11-21 20:35:00 +0100 <geekosaur> 😞
2022-11-21 20:35:09 +0100 <geekosaur> does your zenity support --no-markup ?
2022-11-21 20:36:51 +0100 <kora9> geekosaur: It's in the manpage so I assume so
2022-11-21 20:37:03 +0100 <kora9> I have zenity v3.42.1
2022-11-21 20:40:04 +0100 <geekosaur> hm. can you run manually: zenity --no-markup --title=xmessage --class=Xmessage --name=xmessage --text-info --filename=/path/to/xmonad.errors ? (change the path obviously)
2022-11-21 20:40:20 +0100 <geekosaur> it works here but I wonder if yours has different usage
2022-11-21 20:40:59 +0100 <geekosaur> I have 3.32.0 since ubuntu is debian based
2022-11-21 20:42:55 +0100 <kora9> geekosaur: Yeah, works fine when I do it manually
2022-11-21 20:43:18 +0100 <kora9> I'll try switching out the system-wide xmessage bin just to rule out the env var being the issue
2022-11-21 20:45:21 +0100 <kora9> That didn't work either
2022-11-21 20:45:53 +0100 <kora9> geekosaur: Perhaps it's the perl version?
2022-11-21 20:46:06 +0100 <geekosaur> shouldn't be
2022-11-21 20:46:06 +0100 <kora9> I'm on perl 5.34.1
2022-11-21 20:46:13 +0100 <geekosaur> this is very portable perl
2022-11-21 20:46:38 +0100 <geekosaur> I'm on 5.30.0
2022-11-21 20:46:44 +0100 <kora9> Ah. I'm on Fedora, not sure if it does something very different from Ubuntu
2022-11-21 20:48:08 +0100ft(~ft@p508dbd59.dip0.t-ipconnect.de)
2022-11-21 20:48:15 +0100 <kora9> geekosaur: I see that the file references a "xmessages-wrapper" is that what you've named it? I just named it xmessages since that was the file on github
2022-11-21 20:49:44 +0100 <geekosaur> that's it's "proper" name, but it's kinda useless unless it's named "xmessage". that is mostly so errors /; warnings from the wrapper can be distinguished from those by xmessage itself, since it will find and run the real xmessage if it decides it doesn't understand the parameters rather than possibly mangle someone's output
2022-11-21 20:51:01 +0100 <kora9> geekosaur: Got it to work, it was my fault it seems. When I pasted the file I missed the initial # in the perl shebang
2022-11-21 20:51:04 +0100 <kora9> Sorry about that :)
2022-11-21 20:51:53 +0100 <kora9> Now it's working fine, this really helps! Thanks for the script!
2022-11-21 20:52:30 +0100 <geekosaur> you're welcome
2022-11-21 21:14:23 +0100srz(~srz@181.228.49.93) (Ping timeout: 260 seconds)
2022-11-21 21:19:30 +0100diep(~diep@2a01:cb11:2d7:4a00:b230:54de:5188:7aeb)
2022-11-21 21:39:51 +0100gknux(~gknux@user/galaxy-knuckles/x-3015990) (Quit: ....and i am outta here....)
2022-11-21 21:42:12 +0100gknux(~gknux@user/galaxy-knuckles/x-3015990)
2022-11-21 22:05:23 +0100mc47(~mc47@xmonad/TheMC47)
2022-11-21 22:27:53 +0100diep(~diep@2a01:cb11:2d7:4a00:b230:54de:5188:7aeb) (Remote host closed the connection)
2022-11-21 22:37:45 +0100Ehllie(~Thunderbi@79.184.239.57.ipv4.supernova.orange.pl)
2022-11-21 23:00:19 +0100Ehllie1(~Thunderbi@79.184.239.57.ipv4.supernova.orange.pl)
2022-11-21 23:00:34 +0100Ehllie(~Thunderbi@79.184.239.57.ipv4.supernova.orange.pl) (Ping timeout: 260 seconds)
2022-11-21 23:00:34 +0100Ehllie1Ehllie
2022-11-21 23:05:14 +0100Ehllie(~Thunderbi@79.184.239.57.ipv4.supernova.orange.pl) (Ping timeout: 260 seconds)
2022-11-21 23:18:28 +0100clu(~clu@user/varjax) (Ping timeout: 248 seconds)
2022-11-21 23:18:32 +0100srz(~srz@181.228.49.93)
2022-11-21 23:31:24 +0100srz(~srz@181.228.49.93) (Remote host closed the connection)
2022-11-21 23:35:31 +0100srz(~srz@181.228.49.93)
2022-11-21 23:37:48 +0100Ehllie(~Thunderbi@79.184.239.57.ipv4.supernova.orange.pl)
2022-11-21 23:42:34 +0100Ehllie(~Thunderbi@79.184.239.57.ipv4.supernova.orange.pl) (Ping timeout: 260 seconds)
2022-11-21 23:49:59 +0100mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)