Logs: liberachat/#xmonad
| 2023-04-16 16:26:22 | → | unclechu joins (~unclechu@2001:470:69fc:105::354) |
| 2023-04-16 16:55:35 | × | malook quits (~Thunderbi@2a02:9b0:4029:5ee:e475:c696:b0e6:59f7) (Ping timeout: 260 seconds) |
| 2023-04-16 17:39:21 | × | werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 255 seconds) |
| 2023-04-16 17:40:06 | → | werneta joins (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2023-04-16 17:45:10 | → | catman joins (~catman@user/catman) |
| 2023-04-16 18:12:08 | × | catman quits (~catman@user/catman) (Quit: WeeChat 3.8) |
| 2023-04-16 18:34:31 | hopelessness[m] | is now known as jade[m] |
| 2023-04-16 19:21:29 | × | pharonix71 quits (~pharonix7@user/pharonix71) (Ping timeout: 255 seconds) |
| 2023-04-16 19:23:21 | × | mc47 quits (~mc47@xmonad/TheMC47) (Quit: Leaving) |
| 2023-04-16 19:23:58 | → | pharonix71 joins (~pharonix7@user/pharonix71) |
| 2023-04-16 20:22:39 | × | terrorjack quits (~terrorjac@2a01:4f8:c17:87f8::) (Quit: The Lounge - https://thelounge.chat) |
| 2023-04-16 20:25:08 | → | terrorjack joins (~terrorjac@2a01:4f8:c17:87f8::) |
| 2023-04-16 20:38:21 | → | catman joins (~catman@user/catman) |
| 2023-04-16 21:20:45 | × | catman quits (~catman@user/catman) (Ping timeout: 255 seconds) |
| 2023-04-16 21:59:01 | <jaspion[m]> | <mc47[m]> "Can you maybe send an exmaple..." <- Hi, thanks for your help! |
| 2023-04-16 21:59:01 | <jaspion[m]> | Here is my config: |
| 2023-04-16 21:59:01 | <jaspion[m]> | https://github.com/namoscagnm/dotfiles/blob/b58695dc97faa320f161a90b832d9fa9f70c7899/xmonad/.xmonad/xmonad.hs#L96 |
| 2023-04-16 22:05:43 | <jaspion[m]> | <mc47[m]> "Can you maybe send an exmaple..." <- import Control.Monad... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/abe50b3bd7460b3ee3798c6146d4b671accd5dcf>) |
| 2023-04-16 23:09:33 | → | JonathanWatson[m joins (~jjwmatrix@2001:470:69fc:105::2:a544) |
| 2023-04-16 23:12:14 | <JonathanWatson[m> | does anyone know where i can find old issues(?) for xmonad before it was on git? |
| 2023-04-16 23:12:40 | <JonathanWatson[m> | for example, #598 in this commit |
| 2023-04-16 23:12:41 | JonathanWatson[m | uploaded an image: (199KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/OOYThaNfLwQjsRPdscovbgyE/image.png > |
| 2023-04-16 23:13:27 | <vrs> | https://code.google.com/archive/p/xmonad/issues |
| 2023-04-16 23:13:50 | <JonathanWatson[m> | thank you! |
| 2023-04-16 23:18:09 | <vrs> | yw |
| 2023-04-16 23:18:21 | <vrs> | contains references to bugs such as the dreaded #4 |
| 2023-04-16 23:18:35 | <JonathanWatson[m> | by the way, what version control system was xmonad on before? i assume it was darcs but the google code archive page says "svn-based" |
| 2023-04-16 23:18:57 | <geekosaur> | we weren't in google code, we were on code.haskell.org which was darcs |
| 2023-04-16 23:19:19 | → | abhixec joins (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) |
| 2023-04-16 23:19:35 | <geekosaur> | https://archives.haskell.org/code.haskell.org/xmonad/ https://archives.haskell.org/code.haskell.org/XMonadContrib/ |
| 2023-04-16 23:20:08 | <geekosaur> | it had no bug tracker so we used google code for that |
| 2023-04-16 23:23:01 | <JonathanWatson[m> | i ask as my current dissertation task is to update between about 100 versions of xmonad with my dynamic software updating system and i have been using git commits as versions of the program |
| 2023-04-16 23:23:23 | <JonathanWatson[m> | but now i appear to be on the darcs equivalent of commits |
| 2023-04-16 23:23:56 | <geekosaur> | I converted the darcs repos to git when I transferred us to github because c.h.o was being shut down |
| 2023-04-16 23:24:11 | <geekosaur> | so we should have all the darcs commits as well |
| 2023-04-16 23:24:52 | <JonathanWatson[m> | are there any major differences from git commits? |
| 2023-04-16 23:26:18 | <geekosaur> | darcs has a fancy "patch theory" for its "commits"/patches |
| 2023-04-16 23:26:28 | <geekosaur> | but I don't know much in the way of details |
| 2023-04-16 23:27:21 | <JonathanWatson[m> | i suppose if its been converted to git i can continue to use git reasoning |
| 2023-04-16 23:27:28 | <geekosaur> | I think it's an algebra |
| 2023-04-16 23:27:44 | <geekosaur> | but yes, the converted stuff should behave like git |
| 2023-04-16 23:28:24 | <JonathanWatson[m> | ok that should be fine |
| 2023-04-16 23:29:30 | <geekosaur> | I would expect things like cherrypicking to behave oddly but as far as just checking out commits is concerned it shouldn't matter |
| 2023-04-16 23:34:10 | <JonathanWatson[m> | yeah i'm only extracting the state of repository at pairs of commits where one commit is an ancestor of another and comparing them |
| 2023-04-16 23:47:05 | → | hightower2 joins (~hightower@213.149.61.117) |
| 2023-04-17 00:41:39 | × | ft quits (~ft@87.122.10.136) (Ping timeout: 260 seconds) |
| 2023-04-17 00:43:04 | → | ft joins (~ft@i59F54987.versanet.de) |
| 2023-04-17 02:09:04 | × | td_ quits (~td@i53870922.versanet.de) (Ping timeout: 248 seconds) |
| 2023-04-17 02:10:47 | → | td_ joins (~td@i53870920.versanet.de) |
| 2023-04-17 02:46:29 | → | catman joins (~catman@user/catman) |
| 2023-04-17 05:00:25 | × | catman quits (~catman@user/catman) (Ping timeout: 240 seconds) |
| 2023-04-17 05:52:19 | × | werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 250 seconds) |
| 2023-04-17 05:54:20 | → | werneta joins (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2023-04-17 05:58:37 | → | catman joins (~catman@user/catman) |
| 2023-04-17 06:31:07 | × | catman quits (~catman@user/catman) (Quit: WeeChat 3.8) |
| 2023-04-17 06:45:37 | → | mncheckm joins (~mncheck@193.224.205.254) |
| 2023-04-17 07:14:52 | × | werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 252 seconds) |
| 2023-04-17 07:16:53 | → | werneta joins (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2023-04-17 07:35:27 | → | cfricke joins (~cfricke@user/cfricke) |
| 2023-04-17 07:47:40 | → | thyriaen joins (~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1) |
| 2023-04-17 09:00:06 | × | murchadha[m] quits (~murdchadh@2001:470:69fc:105::3:3103) (Quit: You have been kicked for being idle) |
| 2023-04-17 09:00:07 | × | liskin[m] quits (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2023-04-17 09:00:07 | × | unclechu quits (~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle) |
| 2023-04-17 09:30:36 | × | noze quits (~user@2001:41d0:a:21f1::1) (Quit: ERC 5.4 (IRC client for GNU Emacs 28.2)) |
| 2023-04-17 09:31:08 | → | noze joins (~user@2001:41d0:a:21f1::1) |
| 2023-04-17 10:00:50 | → | hightower3 joins (~hightower@213.149.61.95) |
| 2023-04-17 10:03:01 | × | hightower2 quits (~hightower@213.149.61.117) (Ping timeout: 240 seconds) |
| 2023-04-17 10:17:23 | × | noze quits (~user@2001:41d0:a:21f1::1) (Ping timeout: 256 seconds) |
| 2023-04-17 10:22:23 | → | noze joins (~user@2001:41d0:a:21f1::1) |
| 2023-04-17 10:28:53 | × | thyriaen quits (~thyriaen@2a01:aea0:dd4:555f:6245:cbff:fe9f:48b1) (Quit: Leaving) |
| 2023-04-17 12:04:48 | × | werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 248 seconds) |
| 2023-04-17 14:52:59 | × | amenonsen quits (~amenonsen@pitta.toroid.org) (Ping timeout: 264 seconds) |
| 2023-04-17 15:01:45 | → | sadmax joins (~user@64.130.91.66) |
| 2023-04-17 15:11:22 | × | cfricke quits (~cfricke@user/cfricke) (Quit: WeeChat 3.8) |
| 2023-04-17 15:15:30 | × | abhixec quits (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 260 seconds) |
| 2023-04-17 15:49:03 | <JonathanWatson[m> | does anyone know how i can benchmark xmonad? i would like to give xmonad many keypresses via xdotool and see how long it takes xmonad to execute them all, but i don't know how to find out when this is |
| 2023-04-17 15:50:18 | <JonathanWatson[m> | i changed the NextLayout event to take five seconds and xdotool finishes immediately rather than wait for the five seconds |
| 2023-04-17 15:50:51 | <geekosaur> | xdotool doesn't know how to wait for results of key actions; it just sends the event and exits |
| 2023-04-17 15:51:04 | → | liskin[m] joins (~liskinmat@2001:470:69fc:105::768) |
| 2023-04-17 15:51:19 | → | unclechu joins (~unclechu@2001:470:69fc:105::354) |
| 2023-04-17 15:51:23 | <geekosaur> | (it doesn't even know what the result would be and therefore what to wait for) |
| 2023-04-17 15:53:25 | <JonathanWatson[m> | is there anything that could work without modifying xmonad itself? |
| 2023-04-17 15:53:41 | <geekosaur> | nope |
| 2023-04-17 15:53:42 | <JonathanWatson[m> | since any change i make probably needs to also be made to 96 other versions of xmonad |
| 2023-04-17 15:55:05 | <geekosaur> | and you would also need to modify xdotool, since as I said it has no idea of what to wait for. worse, xmonad can't even tell that xdotool sent the event and that it should send some response back; the event will have the `send_event` flag set, but no indication of what sent it |
| 2023-04-17 15:55:14 | <mc47[m]> | You can probably create a function that takes a label and `X a` and prints the label with how much it took to execute the action to a file or to stderr |
| 2023-04-17 15:55:52 | <mc47[m]> | Oh and Haskell laziness should be considered as well |
| 2023-04-17 15:56:10 | <geekosaur> | very little in xmonad is lazy since everything does IO actions… |
| 2023-04-17 15:56:49 | <mc47[m]> | But you'd need to wrape every action |
| 2023-04-17 15:57:57 | <JonathanWatson[m> | i think the easiest method for my purposes it to send like 1000 keypresses and then wait for the screen to stop changing for five seconds |
| 2023-04-17 15:58:01 | <JonathanWatson[m> | and then subtract five |
| 2023-04-17 15:59:14 | <JonathanWatson[m> | but then i need to make sure that i am sending the keypresses faster than xmonad is handling them and i need to check that that many keypresses can be queued |
| 2023-04-17 15:59:33 | <JonathanWatson[m> | and i also need to figure out how to actually check that the screen hasn't changed for five seconds |
| 2023-04-17 16:00:03 | <geekosaur> | that's actually the easiest part: select expose events on the root window and all children |
| 2023-04-17 16:01:26 | <JonathanWatson[m> | can i do that from outside of xmonad? |
| 2023-04-17 16:01:42 | <geekosaur> | yes |
| 2023-04-17 16:01:51 | <geekosaur> | (and must, in fact) |
| 2023-04-17 16:03:42 | <JonathanWatson[m> | is xmonad an X client? |
| 2023-04-17 16:05:50 | <geekosaur> | yes |
| 2023-04-17 16:06:04 | <JonathanWatson[m> | i'm haven't been sure exactly where it comes into the x window manager pipeline since it doesn't seem to be the server but isn't a normal program |
All times are in UTC.