Logs: liberachat/#xmonad
| 2021-11-12 13:09:49 | → | MatrixTravelerbo joins (~voyagert2@2001:470:69fc:105::22) |
| 2021-11-12 13:10:01 | → | Industrial[m] joins (~industria@2001:470:69fc:105::eb9) |
| 2021-11-12 13:10:01 | → | denbrahe[m] joins (~denbrahem@2001:470:69fc:105::19c0) |
| 2021-11-12 13:10:01 | → | peddie joins (~peddie@2001:470:69fc:105::25d) |
| 2021-11-12 13:10:01 | → | yuu[m] joins (~yuumatrix@2001:470:69fc:105::8a6) |
| 2021-11-12 13:10:02 | → | ms[m] joins (~msmatrixp@2001:470:69fc:105::2b48) |
| 2021-11-12 13:10:02 | → | VarikValefor[m] joins (~varikvale@2001:470:69fc:105::a5d) |
| 2021-11-12 13:10:02 | → | sdk joins (~sdk@user/sdk) |
| 2021-11-12 13:28:42 | <L29Ah> | 10:30:30]<Solid> One's own event hooks run before core's `handle` function, so it may well be done in contrib with extensible state |
| 2021-11-12 13:28:42 | <L29Ah> | but it is impossible to avoid running core's or push the read event to it afaik |
| 2021-11-12 13:29:23 | <L29Ah> | 14:09:10]<liskin> L29Ah: I have no idea what you're trying to achieve, but I agree with what Solid said |
| 2021-11-12 13:29:23 | <L29Ah> | computer start thrashing due to lack of ram, you ask xmonad to close a window, xmonad closes 10 windows due to xorg's autorepeat feature; this patch fixes this misconduct |
| 2021-11-12 13:30:50 | × | sagax quits (~sagax_nb@user/sagax) (Quit: Konversation terminated!) |
| 2021-11-12 13:36:06 | <geekosaur> | actually you can prevent the core handler from running by `pure (All False)` |
| 2021-11-12 13:36:25 | <geekosaur> | or use `pure (All True)` to pass it on to the core handler |
| 2021-11-12 13:36:28 | × | cfricke quits (~cfricke@user/cfricke) (Quit: WeeChat 3.3) |
| 2021-11-12 13:37:52 | <L29Ah> | geekosaur: i mean pass the key code |
| 2021-11-12 13:37:59 | → | noex joins (~noex@2600:8804:1280:aa0:5857:94a:25de:c513) |
| 2021-11-12 13:38:11 | <L29Ah> | it's not like i can or should tell X to do it for me, is it? |
| 2021-11-12 13:41:01 | <geekosaur> | there are ways to do that although they'd be a little weird because you would also have to emulate the switch to active keyboard grab |
| 2021-11-12 13:42:06 | <geekosaur> | this said, I'd argue that a large part of that particular problem is that we use a really inefficient structure to track windows and it might make more sense to fix that and thereby reduce the thrashing :) |
| 2021-11-12 13:42:14 | <geekosaur> | (not sure how much that would help though) |
| 2021-11-12 13:44:33 | <geekosaur> | also there's xset to control autorepeat directly |
| 2021-11-12 13:44:44 | <geekosaur> | and can be controlled by keycode, even |
| 2021-11-12 13:56:55 | × | noex quits (~noex@2600:8804:1280:aa0:5857:94a:25de:c513) (Read error: Connection reset by peer) |
| 2021-11-12 14:03:46 | × | desantra quits (~skykanin@user/skykanin) (Quit: WeeChat 3.3) |
| 2021-11-12 14:04:23 | <L29Ah> | and can't be controlled per application |
| 2021-11-12 14:05:26 | → | desantra joins (~skykanin@user/skykanin) |
| 2021-11-12 14:06:27 | <desantra> | Whenever I start my computer and my `i3-color-lock` is launched other applications are launched and their windows are rendered on top of the lock screen. Is it possible to tell my `i3-color-lock` to render on top? |
| 2021-11-12 14:07:53 | <L29Ah> | desantra: do you mean i3lock-color? |
| 2021-11-12 14:08:44 | <desantra> | yes |
| 2021-11-12 14:10:47 | <desantra> | L29Ah: is there a way to set the z-index or smth for an app? |
| 2021-11-12 14:10:54 | <L29Ah> | i recall similar thing when windows get popped up and stay on the screen until xmonad is asked to switch the workspace to the one the window is ordered to be at by the manage hook, but i3lock-color works fine here |
| 2021-11-12 14:10:59 | <L29Ah> | but i don't run it at startup... |
| 2021-11-12 14:12:12 | <L29Ah> | maybe you can isFullscreen -?> doFullFloat? |
| 2021-11-12 14:12:14 | <L29Ah> | https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Hooks-ManageHelpers.html |
| 2021-11-12 14:12:21 | <desantra> | It works fine otherwise, just not on startup unless I make it sleep for some seconds |
| 2021-11-12 14:12:32 | <desantra> | L29Ah: I'm already using that |
| 2021-11-12 14:13:25 | <desantra> | oh, nvm I'm using a different arrow, lemme try |
| 2021-11-12 14:18:56 | <liskin> | L29Ah: what geekosaur said about pure (All False), and then also: get yourself some earlyoomd or systemd-oomd, you're working around symptoms of an entirely preventable problem |
| 2021-11-12 14:19:28 | <desantra> | I'm using `isFullscreen --> doFullFloat` with `composeAll`, but that shouldn't matter. It has the same effect |
| 2021-11-12 14:19:31 | <L29Ah> | i already fixed this problem locally by upgrading my hardware |
| 2021-11-12 14:20:13 | <L29Ah> | or not, as i didn't run unpatched xmonad for long for 9-ish years already |
| 2021-11-12 14:20:40 | <liskin> | L29Ah: oh, I was just going to suggest that buying better HW might also be an option, but then I remembered that it's not really a solution - more RAM didn't help my wife one bit, she just kept more tabs open |
| 2021-11-12 14:20:44 | <L29Ah> | anyway, i doubt i need it anymore, but i still think that it's a good to ignore autorepeat in xmonad |
| 2021-11-12 14:21:13 | <L29Ah> | i also bought a nvme that makes thrashing much faster ;) |
| 2021-11-12 14:22:01 | × | desantra quits (~skykanin@user/skykanin) (Quit: WeeChat 3.3) |
| 2021-11-12 14:24:14 | → | desantra joins (~skykanin@user/skykanin) |
| 2021-11-12 14:26:15 | <liskin> | hm, but yeah, disabling autorepeat for xmonad key bindings might actually be somewhat desirable |
| 2021-11-12 14:26:31 | <liskin> | although probably not always - I like my volume buttons to autorepeat |
| 2021-11-12 14:26:56 | <liskin> | definitely do feel free to submit a proper pull request though |
| 2021-11-12 14:27:10 | <geekosaur> | alt-h/alt-l might also be candidates for autorepeat |
| 2021-11-12 14:27:34 | <geekosaur> | whereas alt-,/alt-. probably wouldn't |
| 2021-11-12 14:27:38 | <geekosaur> | s/alt/mod/g |
| 2021-11-12 14:27:56 | <liskin> | although I wonder if the duplicate keybinding detection can be done in -contrib somehow, as an action that one prepends to a keybinding or something |
| 2021-11-12 14:28:02 | <liskin> | that would be best UX imo |
| 2021-11-12 14:28:13 | <liskin> | so that one can decide which keybindings can autorepeat and which can't |
| 2021-11-12 14:28:19 | <liskin> | (afk, meeting now, sorry) |
| 2021-11-12 14:28:22 | × | diep quits (~diep@lfbn-ncy-1-110-197.w83-194.abo.wanadoo.fr) (Remote host closed the connection) |
| 2021-11-12 14:30:26 | <L29Ah> | i already submitted the patch 9 years ago to xmonad mailing list, so now i'm too lazy :P |
| 2021-11-12 14:30:51 | <L29Ah> | and i like my volume buttons to be handled by actkbd so it bypass Xorg's screen locking :] |
| 2021-11-12 14:31:09 | × | desantra quits (~skykanin@user/skykanin) (Quit: WeeChat 3.3) |
| 2021-11-12 14:32:25 | <L29Ah> | you could make a keypress handling hook instead of the current xmonad's hardcoded behavior if you want it configurable |
| 2021-11-12 14:35:58 | <Solid> | I mean, it really _is_ configurable since you can have an event like that in your own eventHook and then just not pass it through |
| 2021-11-12 14:36:21 | <Solid> | the only bad thing being that you need to replicate some logic from core (but you'd have to do that anyways, I think) |
| 2021-11-12 14:39:45 | <L29Ah> | ah so `handle` thing in Main.hs is just the fallback hook |
| 2021-11-12 14:40:19 | <L29Ah> | yeah then my patch could be made in contrib entirely |
| 2021-11-12 15:24:27 | × | geekosaur quits (~geekosaur@xmonad/geekosaur) (Remote host closed the connection) |
| 2021-11-12 15:24:33 | → | allbery_b joins (~geekosaur@xmonad/geekosaur) |
| 2021-11-12 15:24:36 | allbery_b | is now known as geekosaur |
| 2021-11-12 15:56:26 | → | dschrempf joins (~dominik@070-207.dynamic.dsl.fonira.net) |
| 2021-11-12 16:10:41 | → | seschwar joins (~seschwar@user/seschwar) |
| 2021-11-12 16:30:41 | × | qbt quits (~qbt@user/edun) (Quit: Leaving.) |
| 2021-11-12 16:33:27 | → | a6a45081-2b83 joins (~aditya@2601:249:4300:1296:88ec:cc73:84d4:1507) |
| 2021-11-12 16:33:27 | × | dschrempf quits (~dominik@070-207.dynamic.dsl.fonira.net) (Quit: WeeChat 3.3) |
| 2021-11-12 16:33:31 | × | a6a45081-2b83 quits (~aditya@2601:249:4300:1296:88ec:cc73:84d4:1507) (Remote host closed the connection) |
| 2021-11-12 16:37:55 | <Vermoot> | I'm struggling to find examples of people who use window decorations on xmonad |
| 2021-11-12 16:38:08 | <Vermoot> | Typically, the usual title bar, with buttons, etc |
| 2021-11-12 16:44:17 | <geekosaur> | I think most people don't, although there are a few layouts that include them and you can use Decoration to build your own |
| 2021-11-12 16:45:36 | <Vermoot> | I'm sure most people don't but I like to have a good mouse-only workflow as well as a good keyboard centric one. Sometimes I just want to do stuff with my mouse and having window decorations (sometimes, not always) would help with that |
| 2021-11-12 16:46:00 | <Vermoot> | I've tried using NoFrillsDeco, SimpleDecorations, etc, but I've never been able to make them work |
| 2021-11-12 17:09:47 | → | SenranKaguya joins (~weechat@c-73-15-19-170.hsd1.ca.comcast.net) |
| 2021-11-12 17:49:22 | → | desantra joins (~skykanin@user/skykanin) |
| 2021-11-12 18:05:49 | × | desantra quits (~skykanin@user/skykanin) (Quit: WeeChat 3.3) |
| 2021-11-12 18:08:35 | → | mc47 joins (~mc47@xmonad/TheMC47) |
| 2021-11-12 18:08:41 | <mc47> | what's up people |
| 2021-11-12 18:08:55 | <mc47> | liskin I'll check the link, but it's looking so crazy for me right now |
| 2021-11-12 18:16:07 | <geekosaur> | lots of logo submissions the past few days |
| 2021-11-12 18:20:30 | <liskin> | Logo submissions and sponsors, we're up in $600s now |
| 2021-11-12 18:21:19 | <liskin> | Other than that, I'm trying to avoid keyboards, to let my hands get back to normal |
| 2021-11-12 18:27:00 | <mc47> | the only thing I've been following is the logo contest, I think we have some very nice submissions |
| 2021-11-12 18:27:02 | <geekosaur> | hah, just found a small bug in the SimpleDecoration docs |
| 2021-11-12 18:27:15 | × | mc47 quits (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2021-11-12 18:27:35 | <geekosaur> | they mention dwmStyle instead of simpleDeco for the more advanced configuration example (3 guesses which module it was copied from) |
| 2021-11-12 18:28:33 | <geekosaur> | does this need to go through the whole PR + CHANGES thing or should I just patch it in place? |
| 2021-11-12 18:28:43 | × | werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 250 seconds) |
| 2021-11-12 18:30:03 | → | werneta joins (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2021-11-12 18:31:57 | <liskin> | Definitely need for changes entry for a docs fix, and PR only if you think you're likely to fuck it up and want another human to check for mistakes |
| 2021-11-12 18:32:05 | <liskin> | *no need for changes |
| 2021-11-12 18:34:41 | × | werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 245 seconds) |
All times are in UTC.