Logs: liberachat/#xmonad
| 2023-03-28 11:02:15 | → | murchadha[m] joins (~murdchadh@2001:470:69fc:105::3:3103) |
| 2023-03-28 11:02:38 | → | sibi joins (~sibi@2001:470:69fc:105::8ab) |
| 2023-03-28 11:04:51 | → | nexilva[m] joins (~nexilvama@2001:470:69fc:105::2:cf52) |
| 2023-03-28 11:05:28 | → | qbit_m joins (~qbittapen@2001:470:69fc:105::194) |
| 2023-03-28 11:06:33 | → | Etxeberrialex[m] joins (~etxeberri@2001:470:69fc:105::1:5ae6) |
| 2023-03-28 14:22:15 | × | derfflinger quits (~derffling@user/derfflinger) (Read error: Connection reset by peer) |
| 2023-03-28 14:29:23 | × | werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Remote host closed the connection) |
| 2023-03-28 14:44:05 | → | diep joins (~diep@2a01:cb11:2d7:4a00:a13f:e40c:c4e8:736c) |
| 2023-03-28 14:44:15 | × | diep quits (~diep@2a01:cb11:2d7:4a00:a13f:e40c:c4e8:736c) (Remote host closed the connection) |
| 2023-03-28 15:00:21 | ← | L29Ah parts (~L29Ah@wikipedia/L29Ah) () |
| 2023-03-28 15:48:50 | → | thunderrd joins (~thunderrd@183.182.114.86) |
| 2023-03-28 15:52:40 | × | xmonadtrack quits (~xmonadtra@xmonad/geekosaur) (Remote host closed the connection) |
| 2023-03-28 15:53:24 | × | geekosaur quits (~geekosaur@xmonad/geekosaur) (Quit: Leaving) |
| 2023-03-28 15:57:05 | → | L29Ah joins (~L29Ah@wikipedia/L29Ah) |
| 2023-03-28 16:04:50 | → | geekosaur joins (~geekosaur@xmonad/geekosaur) |
| 2023-03-28 16:06:42 | → | xmonadtrack joins (~xmonadtra@069-135-003-034.biz.spectrum.com) |
| 2023-03-28 16:06:42 | × | xmonadtrack quits (~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host) |
| 2023-03-28 16:06:42 | → | xmonadtrack joins (~xmonadtra@xmonad/geekosaur) |
| 2023-03-28 17:42:35 | <xmonadtrack> | New branch created: v0.17.2 (2 commits) https://github.com/xmonad/xmonad/tree/v0.17.2 |
| 2023-03-28 17:42:49 | → | liskin[m] joins (~liskinmat@2001:470:69fc:105::768) |
| 2023-03-28 17:44:31 | Solid | just created ^ |
| 2023-03-28 17:44:50 | <Solid> | I wonder whether we'll also need all of the CI commits, in order to make that not have a stroke |
| 2023-03-28 17:45:04 | <Solid> | but other than that we should be good to do a release on the weekend or so |
| 2023-03-28 19:18:38 | → | malook joins (~Thunderbi@2a02:9b0:4029:41a8:a570:c303:c5b7:c26f) |
| 2023-03-28 19:18:46 | × | malook quits (~Thunderbi@2a02:9b0:4029:41a8:a570:c303:c5b7:c26f) (Client Quit) |
| 2023-03-28 20:06:23 | → | ft joins (~ft@p3e9bc443.dip0.t-ipconnect.de) |
| 2023-03-28 20:16:10 | <liskin> | A bit silly naming the branch the same you're gonna name the tag... |
| 2023-03-28 20:16:33 | <liskin> | I'll check the CI commits later |
| 2023-03-28 21:19:52 | × | L29Ah quits (~L29Ah@wikipedia/L29Ah) (Ping timeout: 265 seconds) |
| 2023-03-28 22:16:04 | → | L29Ah joins (~L29Ah@wikipedia/L29Ah) |
| 2023-03-28 23:02:38 | → | werneta joins (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2023-03-28 23:24:40 | → | catman joins (~catman@user/catman) |
| 2023-03-28 23:27:28 | × | chomwitt quits (~chomwitt@athedsl-346372.home.otenet.gr) (Ping timeout: 265 seconds) |
| 2023-03-29 00:17:15 | × | catman quits (~catman@user/catman) (Ping timeout: 248 seconds) |
| 2023-03-29 01:50:02 | → | rekahsoft joins (~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-142.dsl.bell.ca) |
| 2023-03-29 01:50:41 | × | rekahsoft quits (~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-142.dsl.bell.ca) (Remote host closed the connection) |
| 2023-03-29 01:51:19 | → | rekahsoft joins (~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-142.dsl.bell.ca) |
| 2023-03-29 02:12:29 | → | catman joins (~catman@user/catman) |
| 2023-03-29 02:29:54 | × | td_ quits (~td@i5387093D.versanet.de) (Ping timeout: 255 seconds) |
| 2023-03-29 02:31:41 | → | td_ joins (~td@i53870923.versanet.de) |
| 2023-03-29 02:58:12 | × | catman quits (~catman@user/catman) (Ping timeout: 265 seconds) |
| 2023-03-29 04:15:32 | × | rekahsoft quits (~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-142.dsl.bell.ca) (Ping timeout: 265 seconds) |
| 2023-03-29 05:45:12 | → | chomwitt joins (~chomwitt@2a02:587:7a0f:e00:1ac0:4dff:fedb:a3f1) |
| 2023-03-29 05:50:16 | × | thunderrd quits (~thunderrd@183.182.114.86) (Ping timeout: 265 seconds) |
| 2023-03-29 06:11:44 | <Solid> | oh, right :) |
| 2023-03-29 06:17:13 | <Solid> | guess we can always rename the branch when its time |
| 2023-03-29 06:29:57 | × | ft quits (~ft@p3e9bc443.dip0.t-ipconnect.de) (Quit: leaving) |
| 2023-03-29 06:31:34 | × | werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 255 seconds) |
| 2023-03-29 06:33:15 | → | werneta joins (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2023-03-29 06:41:21 | → | mncheck joins (~mncheck@193.224.205.254) |
| 2023-03-29 07:41:09 | <liskin> | Solid: yeah you'll need to cherry-pick enough of the CI commits to make github show a green tick for the head commit in that branch |
| 2023-03-29 07:41:34 | <liskin> | I mean, getting the haskell-ci workflow green *should* be enough for the release, but… |
| 2023-03-29 07:43:31 | <liskin> | (If we wanted to be super robust we'd need a release branch naming scheme and change the packdeps and generatemanpage workflows to run on release branches as well but in this case we can run packdeps manually and generatemanpage isn't needed.) |
| 2023-03-29 08:06:37 | <xmonadtrack> | xmonad-contrib Tony Zorman * v0.17.1-143-gfb63987a: X.Prompt: Factor out how to accept the current selection (2 hours ago, 1 file, 11+ 7-) https://github.com/xmonad/xmonad-contrib/commit/fb63987ac89c |
| 2023-03-29 08:06:39 | <xmonadtrack> | xmonad-contrib Tony Zorman * v0.17.1-144-gf127f71c: X.Prompt: Alias C-m to RET in Emacs/Vim bindings (2 hours ago, 2 files, 9+ 0-) https://github.com/xmonad/xmonad-contrib/commit/f127f71c914a |
| 2023-03-29 08:17:17 | <wz1000> | can xmonad handle REL_WHEEL_HI_RES events? https://www.kernel.org/doc/html/latest/input/event-codes.html#ev-rel |
| 2023-03-29 08:17:40 | <wz1000> | It doesn't seem so after adding tracing to the event hook |
| 2023-03-29 08:17:48 | × | shinjipf quits (~shinjipf@159.65.131.14) (Quit: Shinji leaves) |
| 2023-03-29 08:19:59 | <wz1000> | I'm trying to fix a bug where if I have a device that advertises these events, and also have regular mouse wheel scroll events bound in xmonad, the hi res versions are not grabbed by xmonad and instead passed through to the underlying window (so the xmonad action is triggered but firefox also scrolls) |
| 2023-03-29 08:20:29 | <wz1000> | I guess that xmonad doesn't use xinput2 or evdev so doesn't know about these events |
| 2023-03-29 08:31:40 | <geekosaur> | correct |
| 2023-03-29 08:38:48 | <geekosaur> | you could conceivably mask for those events in startupHook but you'd have to modify the X11 library to recognize them the same way liskin had to modify it to recognize XRandR events. conceivably we could crash without that, since if we received an XI2 event the X11 lib wouldn't know what to do with it |
| 2023-03-29 08:42:19 | <geekosaur> | and it might even use more memory than is reserved for a received event which would corrupt the heap |
| 2023-03-29 08:43:25 | <geekosaur> | (I don't really like how X11 lib deals with events, but that ship sailed in xmonad 0.1) |
| 2023-03-29 08:44:16 | × | L29Ah quits (~L29Ah@wikipedia/L29Ah) (Ping timeout: 252 seconds) |
| 2023-03-29 08:44:17 | <geekosaur> | or even whenever the original X11 bindings were written because it's that that expect an `alloca`d buffer for `nextEvent` |
| 2023-03-29 08:49:29 | → | shinjipf joins (~shinjipf@137.184.4.49) |
| 2023-03-29 08:50:10 | × | shinjipf quits (~shinjipf@137.184.4.49) (Client Quit) |
| 2023-03-29 08:50:38 | → | shinjipf joins (~shinjipf@137.184.4.49) |
| 2023-03-29 09:00:06 | × | deip[m] quits (~deipmatri@2001:470:69fc:105::2:679e) (Quit: You have been kicked for being idle) |
| 2023-03-29 09:00:37 | × | liskin[m] quits (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2023-03-29 09:22:10 | → | real-fht[m] joins (~real-fhtm@2001:470:69fc:105::2:d597) |
| 2023-03-29 09:27:15 | <real-fht[m]> | is it possible to combine different actions in a single manageHook match? |
| 2023-03-29 09:27:22 | <real-fht[m]> | (for example, run doShift and doFloat) |
| 2023-03-29 09:42:05 | <geekosaur> | use <+> or >> |
| 2023-03-29 09:42:22 | → | liskin[m] joins (~liskinmat@2001:470:69fc:105::768) |
| 2023-03-29 09:42:42 | <geekosaur> | or <> which is the new spelling for <+> |
| 2023-03-29 09:43:15 | <geekosaur> | some things need to happen in a particular order (https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs#L281-L282) |
| 2023-03-29 09:44:31 | <geekosaur> | https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs#L162-L163 is an example within a manageHook |
| 2023-03-29 10:39:00 | → | Ou42 joins (~Ou4242a@2600:1700:e930:41b0:65bd:94a:d3f4:d966) |
| 2023-03-29 10:41:12 | <Ou42> | Hello! ( XY prob(s) will abound... ) I think what I want is to be able to change to a dark theme and increase the font size in xmessage, is this possible? and/or can it be replaced w/ something that has those features? |
| 2023-03-29 10:46:51 | <Ou42> | OK I just now found this: <https://gist.github.com/SilverSoldier/739433e99b291f2f818bc556b00780a3> but how to use it w/ xmonad? |
| 2023-03-29 10:50:10 | <geekosaur> | I use https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmessage (warning: perl) which accepts xmessage options and translates to zenity, which will use your gtk theme |
| 2023-03-29 10:52:17 | <Ou42> | geekosaur: TYVM! That said, I'm only familiar w/ perl in name only. ( I'm running xmonad ATM so I'm a bit slow flipping back / forth ) |
| 2023-03-29 10:52:47 | <Ou42> | I'm basically in "Couch OS" ATM -- laptop connected to TV |
| 2023-03-29 10:52:50 | <Solid> | Ou42: you can, in principle specify any executable via $XMONAD_XMESSAGE (see https://github.com/xmonad/xmonad/blob/master/src/XMonad/Core.hs#L457 ) |
| 2023-03-29 10:53:07 | <Solid> | you'd just need to take care of either doing something with, or ignoring the xmessage-specific arguments that we give it |
| 2023-03-29 10:54:00 | <Ou42> | Solid: there it is! I think! the link I found -- right after joining the chan of course! -- states that the fg/bg color args aren't in the man page. |
| 2023-03-29 10:54:09 | <Ou42> | ... so that might be the easiest way. |
| 2023-03-29 10:55:10 | <geekosaur> | a lot of standard (for old-style X programs) options are in X(7) instead of every program's manpage |
| 2023-03-29 10:55:20 | <geekosaur> | (which kinda sucks) |
| 2023-03-29 10:57:52 | <Ou42> | one moment |
| 2023-03-29 11:00:08 | <Ou42> | OK, I'm learning... maybe?! so that would be "man 7 X" ? |
| 2023-03-29 11:00:18 | <geekosaur> | yes |
| 2023-03-29 11:00:24 | <Ou42> | I didn't find mention of xmessage, but did find -fg |
| 2023-03-29 11:00:36 | <Ou42> | cool beans. |
| 2023-03-29 11:00:48 | <geekosaur> | look for OPTIONS |
| 2023-03-29 11:01:18 | <geekosaur> | it won't mention individual programs; it lists the options that all old-style X11 programs take |
| 2023-03-29 11:02:07 | <geekosaur> | (so it doesn't include things like -fn because not all programs use fonts) |
| 2023-03-29 11:03:52 | <Ou42> | interesting |
All times are in UTC.