Logs: liberachat/#xmonad
| 2021-10-03 18:08:53 | STEVEOSSAS[m] | is now known as TORRENTER[m] |
| 2021-10-03 18:14:32 | <Solid> | I suppose your only options are to either hack this into the config file format or to use haskell to configure xmobar then :) |
| 2021-10-03 18:14:55 | <TORRENTER[m]> | K np, thanks for the help anyway :)) |
| 2021-10-03 18:29:22 | → | jokleinn joins (~jokleinn@user/jokleinn) |
| 2021-10-03 19:29:14 | <TORRENTER[m]> | Hey guys, I have an issue with 2 XMobars: One is at the top of the screen, one is at the bottom. I have an issue where one bar (e.g: top bar) doesn't kill itself on recompile, but the other bar (the bottom one) kills itself and then restarts, why is one bar not restarting, while the other one restarts as normal? Is it maybe because I configured ppOutput wrong?? What is going on? (Also mentioning that the CPU skyrockets on recompile to 99%, |
| 2021-10-03 19:29:14 | <TORRENTER[m]> | after recompile it sits at 19-30% usage, this is because of the duplicate bars spawning on top of each other probably). |
| 2021-10-03 19:29:22 | <TORRENTER[m]> | s/XMobars/XMobar instances/ |
| 2021-10-03 19:29:49 | <TORRENTER[m]> | s/Hey guys, I have an issue with 2 XMobars: One is at the top of the screen, one is at the bottom. I have an issue where one bar (e.g: top bar) doesn't kill itself on recompile, but the other bar (the bottom one) kills itself and then restarts, why is one bar not restarting, while the other one restarts as normal? Is it maybe because I configured ppOutput wrong?? What is going on? (Also mentioning that the CPU skyrockets on recompile to |
| 2021-10-03 19:29:49 | <TORRENTER[m]> | 99%, after recompile it sits at 19-30% usage, this is because of the duplicate bars spawning on top of each other probably)./Hey guys, I have an issue with 2 XMobar instances: One is at the top of the screen, one is at the bottom. I have an issue where one bar (e.g: top bar) doesn't kill itself on recompile, but the other bar (the bottom one) kills itself and then restarts, why is one bar not restarting (but respawning on itself, while the |
| 2021-10-03 19:29:49 | <TORRENTER[m]> | previous process isn't killed), while the other one restarts as normal? Is it maybe because I configured ppOutput wrong?? What is going on? (Also mentioning that the CPU skyrockets on recompile to 99%, after recompile it sits at 19-30% usage, this is because of the duplicate bars spawning on top of each other probably)./ |
| 2021-10-03 19:33:28 | TORRENTER[m] | uploaded an image: (20KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/vBHDSSZxROSwIDYtqEBOVTum/Screenshot%20from%202021-10-03%2020-32-47.png > |
| 2021-10-03 19:33:48 | <TORRENTER[m]> | TORRENTER[m]: Main bit of config |
| 2021-10-03 19:35:32 | TORRENTER[m] | uploaded an image: (91KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/eJqfVwahXjywFisRBRAPMwjm/Screenshot%20from%202021-10-03%2020-34-59.png > |
| 2021-10-03 19:35:33 | <TORRENTER[m]> | TORRENTER[m]: The rest of main |
| 2021-10-03 19:36:45 | <TORRENTER[m]> | TORRENTER[m]: xmproc is the top bar on the main screen, xmprocbtmscr1 is the bottom bar on the main screen |
| 2021-10-03 19:37:20 | <TORRENTER[m]> | StdinReader is only running on the bottom bar BTW |
| 2021-10-03 19:39:12 | <TORRENTER[m]> | I have to do `killall xmobar` in the terminal, this kills all instances of the top bar and the one instance of the bottom bar. |
| 2021-10-03 19:39:30 | <TORRENTER[m]> | * the terminal to actually kill the bar instances, this |
| 2021-10-03 19:39:37 | <TORRENTER[m]> | * the terminal to actually instances, this |
| 2021-10-03 19:39:59 | <TORRENTER[m]> | s/I have to do `killall xmobar` in the terminal, this kills all instances of the top bar and the one instance of the bottom bar./I have to do `killall xmobar` in the terminal to actually kill all the instances of the top bar./ |
| 2021-10-03 19:40:49 | <TORRENTER[m]> | s/I have to do `killall xmobar` in the terminal, this kills all instances of the top bar and the one instance of the bottom bar./I have to do `killall xmobar` in the terminal to actually kill all the instances of the top bar. / |
| 2021-10-03 19:41:44 | <TORRENTER[m]> | But hitting the recompile keybind for XMonad (alt-q) restarts the top bar & bottom bar as normal. When hitting this keybind again, the top bar doesn't kill and then restart itself, it just restarts an makes a new instance on top of itself; The bottom bar acts normally though.. |
| 2021-10-03 19:41:55 | <TORRENTER[m]> | s/an/and/ |
| 2021-10-03 19:44:49 | × | rekahsoft quits (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection) |
| 2021-10-03 19:45:16 | → | rekahsoft joins (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
| 2021-10-03 19:46:19 | <TORRENTER[m]> | This screenshot is proof that the top bar doesn't restart properly: |
| 2021-10-03 19:46:33 | TORRENTER[m] | uploaded an image: (15KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/DSkAAMdFmifpcgpedVMbhwIq/Screenshot%20from%202021-10-03%2020-45-49.png > |
| 2021-10-03 19:47:57 | <TORRENTER[m]> | I'm on the stable version of XMonad, 0.15 BTW |
| 2021-10-03 19:48:01 | <TORRENTER[m]> | Not the git version |
| 2021-10-03 19:48:37 | <TORRENTER[m]> | s/Hey guys, I have an issue with 2 XMobars: One is at the top of the screen, one is at the bottom. I have an issue where one bar (e.g: top bar) doesn't kill itself on recompile, but the other bar (the bottom one) kills itself and then restarts, why is one bar not restarting, while the other one restarts as normal? Is it maybe because I configured ppOutput wrong?? What is going on? (Also mentioning that the CPU skyrockets on recompile to |
| 2021-10-03 19:48:37 | <TORRENTER[m]> | 99%, after recompile it sits at 19-30% usage, this is because of the duplicate bars spawning on top of each other probably)./Hey guys, I have an issue with 2 XMobar instances: One is at the top of the screen, one is at the bottom. I have an issue where one bar (top bar) doesn't kill itself on recompile, but the other bar (the bottom one) kills itself and then restarts, why is one bar not restarting (but respawning on itself, while the |
| 2021-10-03 19:48:37 | <TORRENTER[m]> | previous process isn't killed), while the other one restarts as normal? Is it maybe because I configured ppOutput wrong?? What is going on? (Also mentioning that the CPU skyrockets on recompile to 99%, after recompile it sits at 19-30% usage, this is because of the duplicate bars spawning on top of each other probably)./ |
| 2021-10-03 19:49:05 | × | rekahsoft quits (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection) |
| 2021-10-03 19:49:28 | → | rekahsoft joins (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
| 2021-10-03 19:54:31 | <mc47[m]> | Since StdinReader isn't running on the top bar, there's no way to kill it |
| 2021-10-03 19:54:40 | × | rekahsoft quits (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection) |
| 2021-10-03 19:55:03 | → | rekahsoft joins (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
| 2021-10-03 19:56:26 | <mc47[m]> | Either use spawnOnce for the top bar so you don't restart it, add some logic to kill bars in your startupHook, or use XMonad.Hooks.StatusBar from the git version of contrib for a clean solution |
| 2021-10-03 19:57:53 | <mc47[m]> | For the last option, you might want to check https://xmonad.org/INSTALL.html and https://xmonad.github.io/xmonad-docs/xmonad-contrib-0.16.999/XMonad-Hooks-StatusBar.html |
| 2021-10-03 19:58:27 | <TORRENTER[m]> | Thanks! So you're saying either update or use a janky fix? |
| 2021-10-03 19:58:45 | <TORRENTER[m]> | I'll stick with the janky fix for now, might switch to the git version later I guess.. |
| 2021-10-03 20:02:07 | <TORRENTER[m]> | s/?/../ |
| 2021-10-03 20:02:27 | <TORRENTER[m]> | s/a/the/, s/janky fix?/startupHook/ |
| 2021-10-03 20:02:37 | <TORRENTER[m]> | s/janky/startupHook/ |
| 2021-10-03 20:03:17 | <TORRENTER[m]> | s/I'm on the stable version of XMonad, 0.15 BTW/I'm on the stable version of XMonad, 0.15, and on the stable version of XMonad-Contrib too../ |
| 2021-10-03 20:06:21 | <TORRENTER[m]> | Anyway I would go about doing the startupHook fix you mentioned (I am a beginner sry..) |
| 2021-10-03 20:06:27 | <TORRENTER[m]> | s/Anyway I would go about doing the startupHook fix you mentioned (I am a beginner sry..)/Any way I would go about doing the startupHook fix you mentioned (I am a beginner sry..)/ |
| 2021-10-03 20:09:13 | <mc47[m]> | Not sure if calling killall xmobar at the start of the hook would work (because of race conditions), so you're stuck with playing around with persistent states for now, which sadly isn't beginner friendly |
| 2021-10-03 20:09:36 | <mc47[m]> | (no access to a computer right now, sorry) |
| 2021-10-03 20:10:30 | <mc47[m]> | One thing you could do is use StdinReader in xmobar and send nothing to it from xmonad |
| 2021-10-03 20:10:33 | <mc47[m]> | Might work |
| 2021-10-03 20:11:27 | <TORRENTER[m]> | mc47[m]: Tried this a few mins ago, same thing happens unfortunately lol |
| 2021-10-03 20:12:13 | × | rekahsoft quits (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection) |
| 2021-10-03 20:13:06 | → | rekahsoft joins (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
| 2021-10-03 20:13:45 | <TORRENTER[m]> | I'll just wait until tmrw I guess, in the meantime I'll just use spawnOnce and just manually kill the bar if anything happens, thanks though :)) |
| 2021-10-03 20:15:01 | <TORRENTER[m]> | * use spawnOnce in the startupHook and just |
| 2021-10-03 20:19:17 | × | rekahsoft quits (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection) |
| 2021-10-03 20:21:06 | → | rekahsoft joins (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
| 2021-10-03 20:22:34 | <TORRENTER[m]> | s/I'll just wait until tmrw I guess, in the meantime I'll just use spawnOnce and just manually kill the bar if anything happens, thanks though :))/I'll just do this tmrw I guess, in the meantime I'll just use spawnOnce in the startupHook and just manually kill the bar if anything happens, thanks though :))/ |
| 2021-10-03 20:22:47 | <TORRENTER[m]> | s/I'll just wait until tmrw I guess, in the meantime I'll just use spawnOnce and just manually kill the bar if anything happens, thanks though :))/I'll just do this tmrw (or another day) I guess, in the meantime I'll just use spawnOnce in the startupHook and just manually kill the bar if anything happens, thanks though :))/ |
| 2021-10-03 21:12:28 | × | rekahsoft quits (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection) |
| 2021-10-03 21:12:52 | → | rekahsoft joins (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
| 2021-10-03 21:13:07 | × | rekahsoft quits (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection) |
| 2021-10-03 21:14:08 | → | rekahsoft joins (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
| 2021-10-03 21:23:46 | × | rekahsoft quits (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection) |
| 2021-10-03 21:24:15 | → | rekahsoft joins (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
| 2021-10-03 21:24:31 | × | rekahsoft quits (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection) |
| 2021-10-03 21:25:11 | → | rekahsoft joins (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
| 2021-10-03 21:27:01 | × | rekahsoft quits (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection) |
| 2021-10-03 21:27:19 | <TORRENTER[m]> | Anyone know if the git version of XMonad is usable currently? Does it crash alot?? |
| 2021-10-03 21:27:24 | → | rekahsoft joins (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
| 2021-10-03 21:28:12 | <geekosaur> | it should be pretty stable; a number of people are running it currently, because we haven't had a release in so long and it has some major improvements |
| 2021-10-03 21:28:23 | <byorgey> | TORRENTER[m]: the git version of XMonad is always rock-solid in my experience |
| 2021-10-03 21:28:55 | × | rekahsoft quits (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection) |
| 2021-10-03 21:29:17 | <geekosaur> | last time we had a significant issue with crashing was because the Arch packager for the git version decided to ignore the bounds on X11 |
| 2021-10-03 21:29:23 | → | rekahsoft joins (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
| 2021-10-03 21:29:56 | <byorgey> | I have been running xmonad for many years (10+?), I pretty much just randomly do a 'git pull' occasionally and rebuild whenever I feel like it. It has never crashed. |
| 2021-10-03 21:34:19 | × | rekahsoft quits (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection) |
| 2021-10-03 21:34:43 | → | rekahsoft joins (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
| 2021-10-03 21:35:07 | <geekosaur> | in general, when we have bugs they don't show up as crashes. (in xmonad or -contrib at least. every so often a bug is uncovered in the X11 bindings which affects xmonad, like aforementioned Arch issue) |
| 2021-10-03 21:35:53 | <TORRENTER[m]> | Very nice! I think I will switch to the git version tmrw, I'm excited!! |
| 2021-10-03 21:36:07 | <geekosaur> | most commonly they're backward compatibility issues which require xmonad.hs to be updated before it will compile againb |
| 2021-10-03 21:37:11 | <TORRENTER[m]> | * version tmrw (or some other day soon), I'm |
| 2021-10-03 21:44:51 | → | cjb joins (~cjb@user/cjb) |
| 2021-10-03 21:46:38 | × | rekahsoft quits (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection) |
| 2021-10-03 21:47:01 | → | rekahsoft joins (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
| 2021-10-03 21:47:55 | × | rekahsoft quits (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection) |
| 2021-10-03 21:48:30 | → | rekahsoft joins (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
| 2021-10-03 21:59:41 | <TORRENTER[m]> | <geekosaur> "most commonly they're backward..." <- Does this mean I have to update my config before installing the git version? If so I dont mind anyway... |
| 2021-10-03 22:01:38 | <geekosaur> | you might. check the changelog, it will say any backward compat issues: https://github.com/xmonad/xmonad-contrib/blob/master/CHANGES.md https://github.com/xmonad/xmonad/blob/master/CHANGES.md |
| 2021-10-03 22:02:05 | <geekosaur> | actually we should list the XDG changes in the latter as potentially breaking, I think |
| 2021-10-03 22:03:30 | <geekosaur> | since some corner cases behave differently now |
| 2021-10-03 22:04:43 | <geekosaur> | we mostly try to avoid breaking older configs because people still pass around configs from the 0.9 days and expect them to work :) |
| 2021-10-03 22:05:20 | <geekosaur> | and folks like byorgey who mostly have used the same xmonad.hs for many versions |
| 2021-10-03 22:06:22 | <geekosaur> | (heck, I tweak things every few weeks but my basic xmonad.hs is unchanged since 2008 or thenabouts) |
| 2021-10-03 22:13:34 | <cjb> | reading those changes, why is the binary going into XDG_CACHE_DIR? the temporary files make sense because if they are deleted it doesn't matter |
| 2021-10-03 22:14:11 | <geekosaur> | the binary is also regenerated if it's not there |
| 2021-10-03 22:14:45 | <geekosaur> | the only file that is really required is xmonad.hs (and any lib files it might use) |
| 2021-10-03 22:15:12 | <cjb> | fair enough, just means login will take longer for people how have XDG_CACHE_DIR pointed to a tmpfs |
| 2021-10-03 22:15:20 | <cjb> | s/how/who/ |
All times are in UTC.