Logs: liberachat/#xmonad
| 2024-03-22 06:50:25 | → | defjam joins (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) |
| 2024-03-22 07:02:46 | × | defjam quits (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) (Ping timeout: 268 seconds) |
| 2024-03-22 07:16:07 | → | defjam joins (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) |
| 2024-03-22 07:21:08 | × | defjam quits (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) (Ping timeout: 256 seconds) |
| 2024-03-22 07:33:27 | → | defjam joins (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) |
| 2024-03-22 07:39:46 | × | defjam quits (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) (Ping timeout: 268 seconds) |
| 2024-03-22 07:51:33 | → | defjam joins (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) |
| 2024-03-22 07:53:08 | <haskellbridge> | <ventrace> Hey guys, I've copied "The Whole Thing" (config) from https://xmonad.org/TUTORIAL.html and recompiled xmonad. It sets my terminal to the one I want and my keys, but it doesn't start xmobar for some reason? Does the first argument to "statusBarProp" look in path or how does it work? |
| 2024-03-22 08:03:47 | × | defjam quits (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) (Ping timeout: 272 seconds) |
| 2024-03-22 08:17:42 | → | defjam joins (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) |
| 2024-03-22 08:22:46 | × | defjam quits (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) (Ping timeout: 246 seconds) |
| 2024-03-22 08:28:32 | <haskellbridge> | <mc47> ventrace: you run the same command in your terminal? |
| 2024-03-22 08:29:09 | <haskellbridge> | <ventrace> Hi mc47 if I run xmobar from the terminal it runs fine, although if I run xmobar & it suspends itself if I hit enter. |
| 2024-03-22 08:29:19 | <haskellbridge> | <ventrace> But I checked htop and xmobar doesn't spawn |
| 2024-03-22 08:31:28 | <haskellbridge> | <ventrace> I've changed the String to "xmobar -x0" now, and the screen seems to flash as if it draws something but is instantly removed |
| 2024-03-22 08:33:16 | <haskellbridge> | <Solid> Perhaps try giving it an absolute path to make absolutely sure it's not that kind of issue (also check `~/.xsession-errors` or something related) |
| 2024-03-22 08:35:11 | <haskellbridge> | <ventrace> Providing the full path doesn't change the behavior. It almost seems as if xmobar is run and immediately killed. my .xsession-errors is empty |
| 2024-03-22 08:36:06 | → | defjam joins (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) |
| 2024-03-22 08:37:46 | <haskellbridge> | <Solid> What's your xmobar config? |
| 2024-03-22 08:39:47 | <haskellbridge> | <ventrace> I'm not using one at the moment, I just wanted to see it run first before I configured it |
| 2024-03-22 08:41:51 | <haskellbridge> | <ventrace> I can see it draw on my screen a bar for a few miliseconds before it's removed x) |
| 2024-03-22 08:42:10 | × | defjam quits (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) (Ping timeout: 256 seconds) |
| 2024-03-22 08:44:30 | <haskellbridge> | <ventrace> Hang on I'm getting this in my journal |
| 2024-03-22 08:44:31 | <haskellbridge> | <ventrace> Mar 21 13:23:25 nixos xmonad[2263]: xmobar: Caught signal 15; exiting... |
| 2024-03-22 08:44:32 | <haskellbridge> | <ventrace> Mar 21 14:47:16 nixos xmonad[228139]: /bin/sh: line 1: xmobar: command not found |
| 2024-03-22 08:45:57 | <haskellbridge> | <ventrace> if I try to run /bin/sh and then write xmobar it runs though |
| 2024-03-22 08:46:01 | → | yaslam joins (~yaslam@user/yaslam) |
| 2024-03-22 08:46:56 | <haskellbridge> | <Solid> It might be that xmonad is started with a different environment than your shell (and then shell you just now used to execute `/bin/sh`) |
| 2024-03-22 08:47:02 | <haskellbridge> | <Solid> This can happen with display managers |
| 2024-03-22 08:47:47 | <haskellbridge> | <Solid> (Personally, I use `displayManager.startx.enable = true` so I don't have to fuss around with that kind of stuff :)) |
| 2024-03-22 08:48:07 | <haskellbridge> | <ventrace> I do that too |
| 2024-03-22 08:48:18 | <haskellbridge> | <Solid> It might be that xmonad is started with a different environment than your shell (and the shell you just now used to execute `/bin/sh`) |
| 2024-03-22 08:48:25 | <haskellbridge> | <ventrace> in my configuration.nix |
| 2024-03-22 08:48:42 | <haskellbridge> | <Solid> Huh, that's surprising |
| 2024-03-22 08:48:47 | <haskellbridge> | <Solid> What does `which xmobar` return? |
| 2024-03-22 08:48:49 | <haskellbridge> | <ventrace> ^^ |
| 2024-03-22 08:49:02 | <haskellbridge> | <ventrace> /run/current-system/dw/bin/xmobar |
| 2024-03-22 08:50:24 | <haskellbridge> | <Solid> And giving `statusBarProp` this path really also does not work? |
| 2024-03-22 08:51:04 | <haskellbridge> | <ventrace> Well the behaviour I'm noticing is a flashing on my screen 0. There seems to be an outline that looks like xmobar but it's there for less than a scond and it's only the border if I make sense |
| 2024-03-22 08:51:48 | <haskellbridge> | <ventrace> And the windows I have open there sort of rearrange a bit |
| 2024-03-22 08:53:14 | <haskellbridge> | <ventrace> https://unix.stackexchange.com/questions/145786/xmonad-not-launching-xmobar |
| 2024-03-22 08:53:14 | <haskellbridge> | <ventrace> Suggests that xmobar isn't being launched because nothing is sent to it? Not sure what that means. |
| 2024-03-22 08:53:34 | <haskellbridge> | <ventrace> But I assume statusBarProp handles this? |
| 2024-03-22 08:54:15 | <haskellbridge> | <Solid> Yes, and this is only a problem when using unix pipes (which `statusBarProp` does not do) |
| 2024-03-22 08:54:43 | <haskellbridge> | <ventrace> I see.. So this might be the issue. |
| 2024-03-22 08:54:58 | → | defjam joins (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) |
| 2024-03-22 08:55:06 | <haskellbridge> | <ventrace> I don't know these functions though, is there any chance you could assist me here? ^^ |
| 2024-03-22 08:55:23 | <haskellbridge> | <ventrace> 22 ~ │ main :: IO () |
| 2024-03-22 08:55:23 | <haskellbridge> | <ventrace> 23 ~ │ main = xmonad |
| 2024-03-22 08:55:24 | <haskellbridge> | <ventrace> 24 ~ │ . ewmhFullscreen |
| 2024-03-22 08:55:26 | <haskellbridge> | <ventrace> 25 ~ │ . ewmh |
| 2024-03-22 08:55:27 | <haskellbridge> | <ventrace> 26 ~ │ . withEasySB (statusBarProp "/run/current-system/sw/bin/xmobar /home/lambda/.config/nixos/hosts/default/xmobar-config/xmobarrc" |
| 2024-03-22 08:55:28 | <haskellbridge> | <ventrace> │ (pure myXmobarPP)) defToggleStrutsKey |
| 2024-03-22 08:55:30 | <haskellbridge> | <ventrace> 27 ~ │ $ myConfig |
| 2024-03-22 08:55:36 | <haskellbridge> | <Solid> No; as I said, `statusBarProp` should be doing the right thing already |
| 2024-03-22 08:55:44 | <haskellbridge> | <ventrace> Oh! |
| 2024-03-22 08:55:57 | <haskellbridge> | <ventrace> Sorry I misunderstood |
| 2024-03-22 08:56:24 | <haskellbridge> | <Solid> Now I see that you do have an xmobar config! :) |
| 2024-03-22 08:56:34 | <haskellbridge> | <ventrace> Oh haha well I made one quickly |
| 2024-03-22 08:57:08 | <haskellbridge> | <ventrace> https://hastebin.com/share/aqoloyotuc.perl |
| 2024-03-22 08:59:21 | <haskellbridge> | <Solid> I would switch the `StdinReader` with `XMonadLog`, although I guess xmobar shouldn't crash if it's not being send anything via stdin (as seen by it running fine in a terminal…) |
| 2024-03-22 09:00:07 | <haskellbridge> | <ventrace> And now it works |
| 2024-03-22 09:00:11 | <haskellbridge> | <ventrace> What the heck! |
| 2024-03-22 09:03:13 | <haskellbridge> | <Solid> Curious! |
| 2024-03-22 09:03:29 | <haskellbridge> | <ventrace> So the plugin stdinreader isn't working because things aren't being read from stdin |
| 2024-03-22 09:03:52 | <haskellbridge> | <ventrace> but xmonadlog reads from something withing x11 and doesn't require things to be read? |
| 2024-03-22 09:04:04 | × | defjam quits (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) (Ping timeout: 255 seconds) |
| 2024-03-22 09:05:28 | <haskellbridge> | <Solid> Yes, `XmonadLog` reads from a special "property" (as they are called) of the root window |
| 2024-03-22 09:05:39 | <haskellbridge> | <Solid> You can list these with `xprop -root` |
| 2024-03-22 09:05:53 | <haskellbridge> | <Solid> There should be one called `XMONAD_LOG` |
| 2024-03-22 09:06:05 | <haskellbridge> | <ventrace> Solid: Is it correct to assume (at least on my system) that xmonad launches xmobar via /bin/sh? Because I'd like to use some relative paths (exports) to make my config more modular |
| 2024-03-22 09:07:00 | <haskellbridge> | <Solid> Yes, down the line `statusBarProp "xmobar" …` essentially executes `/bin/sh -c "xmobar"` |
| 2024-03-22 09:07:01 | <haskellbridge> | <ventrace> I define these exports in home-manager, so maybe it needs to be on system level |
| 2024-03-22 09:07:13 | <haskellbridge> | <ventrace> Right okay I need to reconfigure my nix config then xD |
| 2024-03-22 09:08:35 | × | hightower3 quits (~hightower@213-202-93-53.dsl.iskon.hr) (Ping timeout: 255 seconds) |
| 2024-03-22 09:17:11 | × | yaslam quits (~yaslam@user/yaslam) (Quit: beans r nice) |
| 2024-03-22 09:17:24 | → | defjam joins (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) |
| 2024-03-22 09:17:35 | → | yaslam joins (~yaslam@user/yaslam) |
| 2024-03-22 09:17:39 | × | yaslam quits (~yaslam@user/yaslam) (Remote host closed the connection) |
| 2024-03-22 09:18:03 | → | yaslam joins (~yaslam@user/yaslam) |
| 2024-03-22 09:19:06 | × | yaslam quits (~yaslam@user/yaslam) (Client Quit) |
| 2024-03-22 09:19:30 | → | yaslam joins (~yaslam@user/yaslam) |
| 2024-03-22 09:23:36 | × | yaslam quits (~yaslam@user/yaslam) (Client Quit) |
| 2024-03-22 09:23:39 | × | defjam quits (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) (Ping timeout: 256 seconds) |
| 2024-03-22 09:24:00 | → | yaslam joins (~yaslam@user/yaslam) |
| 2024-03-22 09:28:04 | × | yaslam quits (~yaslam@user/yaslam) (Client Quit) |
| 2024-03-22 09:28:28 | → | yaslam joins (~yaslam@user/yaslam) |
| 2024-03-22 09:28:58 | × | ft quits (~ft@p508db238.dip0.t-ipconnect.de) (Quit: leaving) |
| 2024-03-22 09:36:50 | → | defjam joins (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) |
| 2024-03-22 09:40:11 | × | yaslam quits (~yaslam@user/yaslam) (Quit: beans r nice) |
| 2024-03-22 09:40:34 | → | yaslam joins (~yaslam@user/yaslam) |
| 2024-03-22 09:41:12 | → | L29Ah joins (~L29Ah@wikipedia/L29Ah) |
| 2024-03-22 09:41:13 | × | yaslam quits (~yaslam@user/yaslam) (Client Quit) |
| 2024-03-22 09:42:45 | × | defjam quits (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) (Ping timeout: 255 seconds) |
| 2024-03-22 09:44:03 | → | defjam joins (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) |
| 2024-03-22 10:21:54 | → | tremon joins (~tremon@83.80.159.219) |
| 2024-03-22 11:08:15 | × | defjam quits (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) (Ping timeout: 260 seconds) |
| 2024-03-22 11:09:18 | → | defjam joins (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) |
| 2024-03-22 12:09:34 | × | defjam quits (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) (Ping timeout: 246 seconds) |
| 2024-03-22 12:21:29 | → | defjam joins (~defjam@2a02:c7e:2807:b900:48b6:7b6b:b969:cb) |
All times are in UTC.