Logs: liberachat/#xmonad
| 2021-10-15 13:43:02 | <Guest23> | https://pastebin.com/snK3dnfM |
| 2021-10-15 13:43:59 | <alternateved> | Yeah, I guess that since you are using EZConfig, you might have some troubles with types there. |
| 2021-10-15 13:44:14 | <geekosaur> | oki, that looks like you're already using EZConfig and you want alternateved's solution |
| 2021-10-15 13:44:33 | <geekosaur> | not the (KeyMask,KeySym)-based one |
| 2021-10-15 13:45:32 | <alternateved> | My solution only cares about workspaces order. |
| 2021-10-15 13:46:11 | <alternateved> | So whatever you have in your workspaces, it should assign the respective keys |
| 2021-10-15 13:48:35 | <alternateved> | I play with DynamicWorkspaces so that is why I have it setup like that |
| 2021-10-15 13:53:01 | lis | is now known as lisq |
| 2021-10-15 14:01:35 | × | dschrempf quits (~dominik@070-207.dynamic.dsl.fonira.net) (Ping timeout: 260 seconds) |
| 2021-10-15 14:06:17 | × | Guest23 quits (~Guest23@83.234.98.90) (Quit: Client closed) |
| 2021-10-15 14:06:34 | ← | qbt parts (~qbt@user/edun) () |
| 2021-10-15 14:33:06 | → | banc joins (banc@gateway/vpn/airvpn/banc) |
| 2021-10-15 15:08:06 | × | cfricke quits (~cfricke@user/cfricke) (Ping timeout: 268 seconds) |
| 2021-10-15 15:23:05 | → | catman joins (~catman@user/catman) |
| 2021-10-15 15:35:07 | → | werneta joins (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2021-10-15 16:00:28 | × | M0x604[m] quits (~M0x604mat@2001:470:69fc:105::e21c) (Quit: You have been kicked for being idle) |
| 2021-10-15 16:00:28 | × | nihilipster[m]1 quits (~nihilipst@2001:470:69fc:105::720) (Quit: You have been kicked for being idle) |
| 2021-10-15 16:16:42 | → | alternat` joins (~user@staticline-31-183-147-179.toya.net.pl) |
| 2021-10-15 16:18:34 | × | alternateved quits (~user@staticline-31-183-147-179.toya.net.pl) (Ping timeout: 252 seconds) |
| 2021-10-15 16:21:34 | × | catman quits (~catman@user/catman) (Ping timeout: 265 seconds) |
| 2021-10-15 16:22:05 | → | catman joins (~catman@user/catman) |
| 2021-10-15 16:24:32 | → | wonko joins (~wjc@62.115.229.50) |
| 2021-10-15 16:55:04 | × | catman quits (~catman@user/catman) (Ping timeout: 265 seconds) |
| 2021-10-15 16:55:32 | → | catman joins (~catman@user/catman) |
| 2021-10-15 17:33:35 | × | benin quits (~benin@183.82.206.194) (Ping timeout: 265 seconds) |
| 2021-10-15 17:47:06 | <jakefromstatefar> | Using some python, bash, and an xmobarrc + boxes, I made a vertical volume bar |
| 2021-10-15 17:47:08 | jakefromstatefar | uploaded an image: (1KiB) < https://libera.ems.host/_matrix/media/r0/download/jupiterbroadcasting.com/wqvIpZmjQUnjaNNQkvSiyINE/image.png > |
| 2021-10-15 17:59:47 | <liskin> | jakefromstatefar: doesn't xmobar support vertical bars out of the box? |
| 2021-10-15 18:00:36 | <liskin> | "Variables that can be used with the -t/--template argument: volume, volumebar, volumevbar, volumeipat, dB, status, volumestatus" |
| 2021-10-15 18:00:41 | <liskin> | > volumevbar |
| 2021-10-15 18:00:43 | <lambdabot> | error: Variable not in scope: volumevbar |
| 2021-10-15 18:11:14 | <liskin> | mc47[m]: just noticed that pprWindowSetXinerama is included in "Internal formatting functions" in X.H.S.PP, but it's really only used in dynamicLogXinerama and completely unrelated to the PP datatype and stuff, maybe it's worth moving it back there and then waiting whether people come screaming that we've deprecated something they use (as dynamicLogXinerama doesn't really have an equivalent in the |
| 2021-10-15 18:11:16 | <liskin> | new framework) |
| 2021-10-15 18:11:56 | <liskin> | not that I expect anyone to come, as dynamicLogXinerama only works if one actually pipes (as in literally having "xmonad | xmobar" in .xsession) it to xmobar |
| 2021-10-15 18:15:37 | × | thunderrd quits (~thunderrd@183.182.110.52) (Remote host closed the connection) |
| 2021-10-15 18:16:37 | → | thunderrd joins (~thunderrd@183.182.110.52) |
| 2021-10-15 18:43:16 | <mc47> | liskin: yes let's move it to X.H.DynamicLog |
| 2021-10-15 18:45:38 | → | cfricke joins (~cfricke@user/cfricke) |
| 2021-10-15 18:50:26 | <alternat`> | Is there any way to debug xmonad crashes? |
| 2021-10-15 18:52:26 | <geekosaur> | check its stdout which should be the session log, wherever your distro puts that (on the original vt if you use startx); if there's a core dump prepare for some fun time with gdb and the bug is almost certainly in the X11 bindings |
| 2021-10-15 18:55:57 | Hash | is now known as LordOfThePings |
| 2021-10-15 19:11:25 | <jakefromstatefar> | <liskin> "jakefromstatefarm: doesn't..." <- No, its bars are horizontal. |
| 2021-10-15 19:15:11 | <geekosaur> | (tracing back the crash will only work up to a point and gdb might become very confused after the first few stack frames. might also have to install some debug symbols for X11 packages and potentially rebuild xmonad-contrib and its dependencies with -g/--debug) |
| 2021-10-15 19:15:43 | <alternat`> | It might be the issue with the QueueReader |
| 2021-10-15 19:16:27 | <geekosaur> | anyway I would be surprised if a crash originates within xmonad, all user code paths should trap exceptions and core dumps in Haskell code not involving FFI calls are almost always ghc bugs |
| 2021-10-15 19:17:01 | <geekosaur> | FFI calls are much more likely |
| 2021-10-15 19:17:30 | jakefromstatefar | uploaded an image: (0KiB) < https://libera.ems.host/_matrix/media/r0/download/jupiterbroadcasting.com/hUyMiyigVhsfrnrwiVzoUoha/image.png > |
| 2021-10-15 19:17:49 | <jakefromstatefar> | There we go, I inverted it, using `[`, and the bg color as the bar, but from the top instead. |
| 2021-10-15 19:18:56 | <alternat`> | Thanks geekosaur - my friend has some random crashes after incorporating xmobar into xmonad with QueueReader. I'll pass your advice. |
| 2021-10-15 19:20:03 | <geekosaur> | and it's xmonad that's crashing, not xmobar? |
| 2021-10-15 19:26:39 | <alternat`> | Yeah, it's seems that it's xmonad. |
| 2021-10-15 19:27:18 | <alternat`> | One of his xmobars also seems to not refresh the time, so the TQueue setup might not be working. |
| 2021-10-15 19:29:00 | <mc47> | Solid, liskin: since the DynamicLog seems to be taken care of, anything else I should take a look at? |
| 2021-10-15 19:29:15 | <mc47> | (btw, I think we shouldn't include the prompt refactor in 0.17) |
| 2021-10-15 19:30:00 | <mc47> | (we should hold off any big changes right now, and only accept bug fixes or new independent modules) |
| 2021-10-15 19:30:51 | × | alternat` quits (~user@staticline-31-183-147-179.toya.net.pl) (Quit: Fading out...) |
| 2021-10-15 19:31:08 | <mc47> | If nothing is pressing, I'll direct my efforts into coming up with a governance proposal |
| 2021-10-15 19:31:49 | → | alternateved joins (~user@staticline-31-183-147-179.toya.net.pl) |
| 2021-10-15 19:32:26 | <mc47> | (I'm gonna be bored to death this weekend since I have an oral project management exam next week after spending a whole week just studying project management each day... so yeah, I'll do something fun like working on xmonad when I want to take a break) |
| 2021-10-15 19:38:47 | × | cfricke quits (~cfricke@user/cfricke) (Ping timeout: 264 seconds) |
| 2021-10-15 19:43:36 | <liskin> | mc47: I'm going to post my review on #605 in the next hour or so |
| 2021-10-15 19:44:09 | <liskin> | that might need your attention then, for another hour or something :-) |
| 2021-10-15 19:45:54 | <liskin> | geekosaur: re these xmonad/xmobar crashes, some context you probably don't have: what these folks are doing is running xmobar as a thread in the xmonad process, passing data via STM instead of pipes/props |
| 2021-10-15 19:46:29 | <mc47> | alrighty then |
| 2021-10-15 19:47:14 | <liskin> | (I find it quite cool that it's technically possible to do something like that, and I know better than to comment on whether it's sane to do or not, it's probably just people having fun exploring what's possible) |
| 2021-10-15 19:47:46 | <alternateved> | Yeah, pretty much. |
| 2021-10-15 19:48:28 | <liskin> | mc47: what we possibly need a bit more than the governance docs is some update of README.md and CONTRIBUTING.md across our repos, if you need more ideas to choose from |
| 2021-10-15 19:48:56 | <liskin> | and if everything goes well, I should start a very intense EWMH hackathon tomorrow :-) |
| 2021-10-15 19:49:36 | <mc47> | Hmm, what about slashing `X.D.Developing` and just relying on CONTRIBUTING.md? |
| 2021-10-15 19:50:32 | <liskin> | X.D.Developing has stuff that doesn't usually go into CONTRIBUTING.md |
| 2021-10-15 19:50:47 | <liskin> | so if anything, you'd need to move half of it into ARCHITECTURE.md or something |
| 2021-10-15 19:51:07 | <liskin> | CONTRIBUTING needs to be short enough for people to actually read it |
| 2021-10-15 19:51:12 | → | cfricke joins (~cfricke@user/cfricke) |
| 2021-10-15 19:51:42 | <mc47[m]> | Alright, convinced |
| 2021-10-15 19:53:24 | <liskin> | (:-) |
| 2021-10-15 19:53:33 | <liskin> | s/^\(// |
| 2021-10-15 20:03:25 | <geekosaur> | ok, that makes a fairly big difference and indeed I'm not sure now whether we're uncovering bugs in STM or the crash is just in non-exception-managed code throwing an STM exception |
| 2021-10-15 20:03:45 | <geekosaur> | gdb won't be helpful there, probably. profiling + -RTS -xc might |
| 2021-10-15 20:09:15 | <geekosaur> | (have to admit I was wondering wtf QueueReader was, and was trying to search xmobar docs. which are now annoying because the README is no longer the whole manual and the only obvious replacement is now a quickstart doc) |
| 2021-10-15 20:12:15 | <Solid> | plugins.org is where the plugins are documented now |
| 2021-10-15 20:13:39 | <liskin> | hm, yeah, I also often swear when I need to look up something in xmobar docs :-/ |
| 2021-10-15 20:14:06 | <liskin> | a table of contents at the top of readme.org would probably help me a lot |
| 2021-10-15 20:14:49 | <alternateved> | There is some table of contents on xmobar page |
| 2021-10-15 20:15:00 | <alternateved> | *a table |
| 2021-10-15 20:15:15 | <geekosaur> | yeh, it's there, somewhat down from the top and not entirely clear that gets you the whole old manual |
| 2021-10-15 20:15:16 | <liskin> | xmobar.org is just showing an outdated readme I think |
| 2021-10-15 20:15:42 | <alternateved> | Yeah, it is. |
| 2021-10-15 20:21:13 | → | electr0n joins (~electr0n@about/security/founder/electr0n) |
| 2021-10-15 20:24:49 | <Solid> | adding TOCs to the necessary files sounds reasonable though |
| 2021-10-15 20:26:39 | → | kdecay joins (~user@2a02:8070:9991:bb00:1229:c2c4:1938:701a) |
| 2021-10-15 20:27:39 | <kdecay> | Hello there |
| 2021-10-15 20:27:45 | <geekosaur> | œ |
| 2021-10-15 20:28:12 | <kdecay> | let me start by thanking you @geekosaur :D |
| 2021-10-15 20:29:26 | <geekosaur> | you're welcome |
| 2021-10-15 20:30:34 | <alternateved> | small disclaimer: kdecay is a friend that had a problem with the crashes |
| 2021-10-15 20:31:14 | <geekosaur> | I'd wonder if there's some code path that needs a userdef around it to catch STM exceptions |
| 2021-10-15 20:33:20 | <geekosaur> | even though, strictly speaking, it's not user-defined code |
| 2021-10-15 20:33:26 | LordOfThePings | is now known as Hash |
| 2021-10-15 20:35:16 | <liskin> | I don't think there are that many code paths to think about |
| 2021-10-15 20:35:38 | <liskin> | it's probably just logHook, unless they're doing something more interesting |
All times are in UTC.