Logs: liberachat/#xmonad
| 2022-10-24 00:17:57 | <jabuxas> | or how is the change |
| 2022-10-24 00:18:29 | <geekosaur> | not a huge change, you get back all the space wasted by marco's borders and such though |
| 2022-10-24 00:18:37 | <geekosaur> | (marco being the standard mate wm) |
| 2022-10-24 00:21:17 | <geekosaur> | also xmonad is distinctly more keyboard-friendly |
| 2022-10-24 00:22:04 | <geekosaur> | especially if you configure FloatKeys which lets you replace the main use of the mouse |
| 2022-10-24 00:22:45 | <geekosaur> | so I kinda get the best of both worlds, I have a desktop for apps which want one, but also the advantages of xmonad |
| 2022-10-24 00:23:52 | <jabuxas> | interesting |
| 2022-10-24 00:24:16 | <jabuxas> | FloatKeys are for moving float windows arounbd? |
| 2022-10-24 00:26:04 | <geekosaur> | yes. by default that's pretty much the only thing in xmonad that requires the mouse (mod-mouse1 or mod-mouse3, plus dragging) |
| 2022-10-24 00:26:23 | <geekosaur> | mouse1 for move, mouse3 for resize |
| 2022-10-24 00:26:35 | <geekosaur> | but FloatKeys provides keyboard equivalents for both |
| 2022-10-24 00:27:08 | <jabuxas> | that's very efficient |
| 2022-10-24 00:27:32 | <jabuxas> | I don't like forcing myself to much on the keyboard, so mod + m1/m3 for moving and resizing for me is very interesting |
| 2022-10-24 00:27:59 | <jabuxas> | but while it took some time for me to get xmonad running, it is a very good wm and im glad i didnt give up this time |
| 2022-10-24 00:29:04 | <geekosaur> | there are also mouse equivalents available for some of the keyboard operations (for example DragPane in place of the usual keyboard adjustment of master vs. slave window space) |
| 2022-10-24 00:29:25 | <geekosaur> | we're all about the flexibility 🙂 |
| 2022-10-24 00:43:34 | <jabuxas> | https://imgur.com/a/jOiExkb |
| 2022-10-24 00:43:39 | <jabuxas> | looking good, the trayer |
| 2022-10-24 00:43:52 | <jabuxas> | jsut need to fix some scripts and coloring |
| 2022-10-24 01:36:05 | × | jabuxas quits (~jabuxas@user/jabuxas) (Remote host closed the connection) |
| 2022-10-24 01:39:31 | × | vanvik1 quits (~vanvik@188.113.111.129) (Ping timeout: 252 seconds) |
| 2022-10-24 01:43:26 | × | jao quits (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection) |
| 2022-10-24 01:48:49 | → | jao joins (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-10-24 02:04:38 | × | banc quits (banc@gateway/vpn/airvpn/banc) (Ping timeout: 276 seconds) |
| 2022-10-24 02:13:34 | × | td_ quits (~td@83.135.9.27) (Ping timeout: 250 seconds) |
| 2022-10-24 02:15:33 | → | td_ joins (~td@83.135.9.20) |
| 2022-10-24 02:23:48 | → | banc joins (banc@gateway/vpn/airvpn/banc) |
| 2022-10-24 02:49:23 | × | terrorjack quits (~terrorjac@2a01:4f8:1c1e:509a::1) (Quit: The Lounge - https://thelounge.chat) |
| 2022-10-24 02:51:58 | → | terrorjack joins (~terrorjac@2a01:4f8:1c1e:509a::1) |
| 2022-10-24 04:43:24 | → | vanvik1 joins (~vanvik@78.156.8.93) |
| 2022-10-24 05:26:06 | → | chomwitt joins (~chomwitt@2a02:587:dc10:8200:1ac0:4dff:fedb:a3f1) |
| 2022-10-24 05:38:59 | × | Maeda quits (~Maeda@91-161-10-149.subs.proxad.net) (Quit: BRB) |
| 2022-10-24 05:40:43 | → | Maeda joins (~Maeda@91-161-10-149.subs.proxad.net) |
| 2022-10-24 06:10:52 | × | chomwitt quits (~chomwitt@2a02:587:dc10:8200:1ac0:4dff:fedb:a3f1) (Remote host closed the connection) |
| 2022-10-24 06:11:16 | → | chomwitt joins (~chomwitt@2a02:587:dc10:8200:1ac0:4dff:fedb:a3f1) |
| 2022-10-24 06:29:11 | × | jao quits (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 276 seconds) |
| 2022-10-24 06:46:05 | → | mncheck joins (~mncheck@193.224.205.254) |
| 2022-10-24 07:17:48 | → | susanjessy[m] joins (~susanjess@2001:470:69fc:105::2:a8e8) |
| 2022-10-24 08:51:41 | → | thyriaen joins (~thyriaen@2a01:aea0:dd4:470d:6245:cbff:fe9f:48b1) |
| 2022-10-24 08:54:53 | <[Leary]> | The event loops in the repeatable actions block the main xmonad event loop, right? What hoppens to the events generated in the meantime---are they lost, queued up, somehow handled? |
| 2022-10-24 09:00:16 | × | floweynt[m] quits (~floweyyag@2001:470:69fc:105::2:86b7) (Quit: You have been kicked for being idle) |
| 2022-10-24 09:00:16 | × | uj[m] quits (~ujmatrixo@2001:470:69fc:105::2:888f) (Quit: You have been kicked for being idle) |
| 2022-10-24 09:04:57 | <liskin> | [Leary]: they stay in the queue |
| 2022-10-24 09:05:07 | <liskin> | man XMaskEvent |
| 2022-10-24 09:07:05 | <[Leary]> | liskin: I see, thanks. |
| 2022-10-24 09:13:20 | <[Leary]> | I wonder what X.A.CycleRecentWS is doing with its `unView` then. It shouldn't need to worry about mangling intermediate changes, and could just grab a copy of the windowset at the start to base each preview off of. |
| 2022-10-24 09:15:45 | <[Leary]> | Perhaps the non-mangling is just an incidental bonus, and I've misunderstood its purpose. |
| 2022-10-24 09:15:52 | <liskin> | that code seems familiar |
| 2022-10-24 09:16:05 | <liskin> | I'm pretty sure you'll find an entire essay full of answers in its git blame :-) |
| 2022-10-24 09:17:44 | <liskin> | hm, it's not there |
| 2022-10-24 09:18:24 | <liskin> | https://github.com/xmonad/xmonad-contrib/pull/543#discussion_r630279325 |
| 2022-10-24 09:18:30 | <liskin> | there may be more in that PR |
| 2022-10-24 09:20:56 | <liskin> | in unrelated news, 0.17.1 in debian unstable \o/ |
| 2022-10-24 09:22:36 | <liskin> | looks like not bumping the 0.17 is the key, so we must never ever do breaking changes again :-D |
| 2022-10-24 09:23:23 | <liskin> | (too late it seems :-)) |
| 2022-10-24 09:24:25 | <Solid> | very much too late :] |
| 2022-10-24 09:24:51 | <Solid> | we could, of course, ride the 0.17.x wave from now on, not like we follow PVP anyways :> |
| 2022-10-24 09:32:07 | <[Leary]> | Okay, so it comes down to the fact the just running the layouts can change layout state, and discarding those changes can create bugs. That's kinda awkward. |
| 2022-10-24 09:33:06 | → | wonko joins (~wjc@2a0e:1c80:2:0:45:15:19:130) |
| 2022-10-24 09:37:24 | × | ft quits (~ft@p3e9bc845.dip0.t-ipconnect.de) (Quit: leaving) |
| 2022-10-24 09:46:56 | <liskin> | real word code tends to be hairy :-) |
| 2022-10-24 10:38:24 | × | Maeda quits (~Maeda@91-161-10-149.subs.proxad.net) (Ping timeout: 250 seconds) |
| 2022-10-24 10:44:30 | → | Maeda joins (~Maeda@91-161-10-149.subs.proxad.net) |
| 2022-10-24 12:05:59 | × | wonko quits (~wjc@2a0e:1c80:2:0:45:15:19:130) (Ping timeout: 272 seconds) |
| 2022-10-24 12:50:11 | → | stackdroid18 joins (14094@user/stackdroid) |
| 2022-10-24 13:00:31 | → | alternateved joins (~user@staticline-31-183-175-205.toya.net.pl) |
| 2022-10-24 13:02:48 | × | alternateved quits (~user@staticline-31-183-175-205.toya.net.pl) (Remote host closed the connection) |
| 2022-10-24 13:26:55 | × | susanjessy[m] quits (~susanjess@2001:470:69fc:105::2:a8e8) (Quit: User was banned) |
| 2022-10-24 13:31:06 | × | chomwitt quits (~chomwitt@2a02:587:dc10:8200:1ac0:4dff:fedb:a3f1) (Remote host closed the connection) |
| 2022-10-24 13:31:30 | → | chomwitt joins (~chomwitt@2a02:587:dc10:8200:1ac0:4dff:fedb:a3f1) |
| 2022-10-24 14:38:20 | → | jao joins (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-10-24 15:22:56 | → | mvk joins (~mvk@2607:fea8:5ce3:8500::a80f) |
| 2022-10-24 15:51:58 | → | wonko joins (~wjc@2a0e:1c80:2:0:45:15:19:130) |
| 2022-10-24 15:56:28 | × | darkstardevx quits (~darkstard@50.126.124.156) (Ping timeout: 250 seconds) |
| 2022-10-24 16:36:56 | × | wonko quits (~wjc@2a0e:1c80:2:0:45:15:19:130) (Ping timeout: 276 seconds) |
| 2022-10-24 16:39:49 | → | jabuxas joins (~klein@user/jabuxas) |
| 2022-10-24 16:40:50 | <jabuxas> | my xmonad is tiling every window by default after I booted my pc today, yesterday everything was fine. Is there any setting that could possibly be doing that? |
| 2022-10-24 16:43:24 | <jabuxas> | actually, figured it out. yesterday I was playing with some windows that needed doFloat and doShift. I guess I can't put both at the same time (even though it compiles just fine) |
| 2022-10-24 16:44:01 | × | qbit_m quits (~qbittapen@2001:470:69fc:105::194) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:01 | × | RosarioPulella[m quits (~rosariopu@2001:470:69fc:105::a57) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:01 | × | mekeor[m] quits (~mekeormat@2001:470:69fc:105::17e4) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:02 | × | Tisoxin quits (~ikosit@user/ikosit) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:02 | × | yuu[m] quits (~yuum]@2001:470:69fc:105::8a6) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:02 | × | sibi quits (~sibi@2001:470:69fc:105::8ab) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:02 | × | VarikValefor[m] quits (~varikvale@2001:470:69fc:105::a5d) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:02 | × | unclechu quits (~unclechu@2001:470:69fc:105::354) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:02 | × | geekosaur[m] quits (~geekosaur@xmonad/geekosaur) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:03 | × | SridharRatnakuma quits (~sridmatri@2001:470:69fc:105::1c2) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:03 | × | aaronv quits (~aaronv@user/aaronv) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:03 | × | Balrog[m] quits (~M0x62616c@2001:470:69fc:105::2:9152) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:03 | × | uhoreg quits (~uhoreg@2001:470:69fc:105::35f) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:03 | × | alternateved[m] quits (~alternate@2001:470:69fc:105::2:894a) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:04 | × | quarkQuark[m] quits (~quarkquar@2001:470:69fc:105::2:46e2) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:04 | × | NONstope[m] quits (~nonstopem@2001:470:69fc:105::2:8d1c) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:04 | × | valarMorghulis[m quits (~lladeebll@2001:470:69fc:105::2:72) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:04 | × | lions[m] quits (~lionsmatr@2001:470:69fc:105::d1fe) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:04 | × | ChaoticMist[m] quits (~gilganixm@2001:470:69fc:105::3d09) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:04 | × | ChristianGrey[m] quits (~jacques16@2001:470:69fc:105::2:a40c) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:04 | × | Industrial[m] quits (~industria@2001:470:69fc:105::eb9) (Quit: Bridge terminating on SIGTERM) |
| 2022-10-24 16:44:04 | × | AskYourself[m] quits (~ask-yours@2001:470:69fc:105::2:9793) (Quit: Bridge terminating on SIGTERM) |
All times are in UTC.