Logs on 2022-10-31 (liberachat/#kmonad)
| 08:31:47 | → | b50d joins (~b50d@62.96.54.30) |
| 08:32:32 | → | Guest16 joins (~Guest16@78.193.181.23) |
| 08:32:41 | × | Guest16 quits (~Guest16@78.193.181.23) (Client Quit) |
| 10:32:57 | → | b50d_ joins (~b50d@62.96.54.30) |
| 10:35:19 | × | b50d quits (~b50d@62.96.54.30) (Ping timeout: 252 seconds) |
| 12:49:01 | × | b50d_ quits (~b50d@62.96.54.30) (Remote host closed the connection) |
| 12:52:11 | <Diablo-D3> | kmonad doesnt have the ability to temporarily stop grabbing if a certain app is running, right? |
| 12:52:42 | <Diablo-D3> | for some reason moonlight wont respond to any keyboard input at all, not just mapped keys, if kmonad is doing its thing |
| 12:53:40 | <Diablo-D3> | moonlight does low level interception like kmonad does (so it can capture more system keys), but even when that function is off moonlight still uses the same api the same way |
| 12:54:17 | <Solid> | Diablo-D3: I don't believe so |
| 13:05:20 | → | b50d joins (~b50d@62.96.54.30) |
| 13:06:05 | <Diablo-D3> | slightly irritating |
| 13:06:16 | <Diablo-D3> | I assume also I cant bind an action to do that |
| 13:17:04 | <Solid> | You could bind an action to kill kmonad... :> |
| 13:19:08 | <Diablo-D3> | not quite what I meant :P |
| 13:21:30 | × | b50d quits (~b50d@62.96.54.30) (Remote host closed the connection) |
| 17:58:40 | <purity-gearD[m]> | I love kmonad |
| 17:59:22 | <purity-gearD[m]> | Having space cadet like parenthesis and esc mapped to a quick tap of ctrl is awesome |
| 20:08:30 | × | grnmtn quits (~grnmtn@c-24-16-55-46.hsd1.wa.comcast.net) (Quit: leaving) |
All times are in UTC on 2022-10-31.