2023-05-11 00:25:26 +0200 | <liskin> | geekosaur: I won't be able to look at it until the weekend I'm afraid :-( |
2023-05-11 00:25:35 +0200 | <geekosaur> | ok |
2023-05-11 00:54:56 +0200 | stellacy | (~stellacy@gateway/tor-sasl/stellacy) (Ping timeout: 240 seconds) |
2023-05-11 00:57:25 +0200 | stellacy | (~stellacy@gateway/tor-sasl/stellacy) |
2023-05-11 00:58:49 +0200 | xmonadtrack | (~xmonadtra@xmonad/geekosaur) (Ping timeout: 265 seconds) |
2023-05-11 01:00:01 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) (Ping timeout: 240 seconds) |
2023-05-11 01:01:22 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) |
2023-05-11 01:23:01 +0200 | mncheckm | (~mncheck@193.224.205.254) (Ping timeout: 268 seconds) |
2023-05-11 01:23:28 +0200 | xmonadtrack | (~xmonadtra@069-135-003-034.biz.spectrum.com) |
2023-05-11 01:23:28 +0200 | xmonadtrack | (~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host) |
2023-05-11 01:23:28 +0200 | xmonadtrack | (~xmonadtra@xmonad/geekosaur) |
2023-05-11 01:53:18 +0200 | diep | (~diep@172-104-137-130.ip.linodeusercontent.com) (Remote host closed the connection) |
2023-05-11 02:33:33 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 265 seconds) |
2023-05-11 02:33:54 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
2023-05-11 03:24:36 +0200 | luffy[m]1 | (~luffychat@2001:470:69fc:105::3:5644) |
2023-05-11 04:20:27 +0200 | td_ | (~td@i53870904.versanet.de) (Ping timeout: 256 seconds) |
2023-05-11 04:22:06 +0200 | td_ | (~td@i53870913.versanet.de) |
2023-05-11 08:16:59 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 264 seconds) |
2023-05-11 08:18:48 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
2023-05-11 08:48:23 +0200 | mncheck | (~mncheck@193.224.205.254) |
2023-05-11 09:01:23 +0200 | mc47 | (~mc47@xmonad/TheMC47) |
2023-05-11 09:50:48 +0200 | m5zs7k | (aquares@web10.mydevil.net) (Ping timeout: 240 seconds) |
2023-05-11 09:55:31 +0200 | m5zs7k | (aquares@web10.mydevil.net) |
2023-05-11 10:24:06 +0200 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
2023-05-11 10:24:51 +0200 | mc47 | (~mc47@xmonad/TheMC47) |
2023-05-11 10:41:14 +0200 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
2023-05-11 10:43:11 +0200 | mc47 | (~mc47@xmonad/TheMC47) |
2023-05-11 11:19:23 +0200 | vistefan | (~stefan@176.120.176.183) |
2023-05-11 11:20:31 +0200 | <vistefan> | Hi! I'mm new to xmonad and haskell. I have free linux installation with xdm as display manager that runs xmonad with ~/.xsession |
2023-05-11 11:20:52 +0200 | <vistefan> | I want xmobar to start too, but I DONT want to write haskell config for xmobar yet |
2023-05-11 11:21:05 +0200 | <vistefan> | Where should I put xmobar start line? |
2023-05-11 11:23:57 +0200 | <geekosaur> | you don't need to write a config for it straight out |
2023-05-11 11:24:05 +0200 | <geekosaur> | `main = xmonad . ewmhFullscreen . ewmh . xmobarProp $ myConfig` |
2023-05-11 11:24:32 +0200 | <geekosaur> | for whatever your `myConfig` is |
2023-05-11 11:25:00 +0200 | <geekosaur> | see https://xmonad.org/TUTORIAL.html |
2023-05-11 11:25:20 +0200 | <geekosaur> | (at "Make XMonad and Xmobar Talk to Each Other") |
2023-05-11 11:30:37 +0200 | <vistefan> | I don't have ewmh, can I omit it? And I also don't have xmobarProps, I just want the defaults from dotfile in home dir |
2023-05-11 11:30:45 +0200 | ft | (~ft@p4fc2a88b.dip0.t-ipconnect.de) (Quit: leaving) |
2023-05-11 11:31:19 +0200 | redgloboli | (~redglobol@user/redgloboli) (Quit: ...enter the matrix...) |
2023-05-11 11:32:29 +0200 | redgloboli | (~redglobol@user/redgloboli) |
2023-05-11 11:38:02 +0200 | <geekosaur> | xmobar won't behave correctly if you don't have xmonad-contrib installed and use at minimum XMonad.Hooks.ManageDocks but preferably that plus EwmhDesktops |
2023-05-11 11:39:20 +0200 | <geekosaur> | if you really want to try it without (expect windows to overlap it) you can simply start xmobar from `main` |
2023-05-11 11:39:45 +0200 | <geekosaur> | `main = spawn "xmobar" >> xmonad myConfig` |
2023-05-11 11:40:24 +0200 | <geekosaur> | xmonad is only ICCCM compliant out of the box, you need EWMH support for docks (and many modern programs) to behave as you expect |
2023-05-11 11:41:43 +0200 | <vistefan> | geekosaur: got it, thanks |
2023-05-11 11:42:08 +0200 | <vistefan> | so, I need import something that will provide xmobarProp for me, or I should write my own props in xmonad.hs? |
2023-05-11 11:42:42 +0200 | <geekosaur> | `xmobarProp` comes from `XMonad.Hooks.StatusBar` |
2023-05-11 11:43:10 +0200 | <geekosaur> | you can write your own stuff later if you feel like it |
2023-05-11 11:43:24 +0200 | <vistefan> | thanks. You rock |
2023-05-11 11:46:32 +0200 | vistefan | (~stefan@176.120.176.183) (Quit: Lost terminal) |
2023-05-11 11:48:12 +0200 | stefan_ | (~stefan@176.120.176.183) |
2023-05-11 11:55:17 +0200 | joshproehl | (~quassel@user/joshproehl) (Remote host closed the connection) |
2023-05-11 11:56:05 +0200 | stefan_ | (~stefan@176.120.176.183) (Quit: Lost terminal) |
2023-05-11 11:56:41 +0200 | joshproehl | (~quassel@user/joshproehl) |
2023-05-11 12:07:20 +0200 | pharonix71 | (~pharonix7@user/pharonix71) (Ping timeout: 240 seconds) |
2023-05-11 12:09:48 +0200 | pharonix71 | (~pharonix7@user/pharonix71) |
2023-05-11 12:14:42 +0200 | stefan_ | (~stefan@176.120.176.183) |
2023-05-11 12:16:04 +0200 | <stefan_> | I've done my first configuration as it is said in https://xmonad.org/TUTORIAL.html (actually I just copied tutorial config and changed some AdditionalKeysP statements), but when I recompile and restart xmonad (and whole X11), there is no xmobar on my screen. |
2023-05-11 12:24:46 +0200 | <geekosaur> | is `xmobar` in your PATH? beware that the `PATH` in your terminal is usually not the one X11 will use and pass to `xmonad`! usually things must be in `/usr/bin` |
2023-05-11 12:27:47 +0200 | <stefan_> | xmobar is in parth, I can run it manually by just the name |
2023-05-11 12:28:15 +0200 | <stefan_> | xmobar is in /usr/bin |
2023-05-11 12:29:29 +0200 | <stefan_> | that config has something about logging, maybe I can watch the log of xmonad start? xsession-errors doesn't give anything about xmobar |
2023-05-11 12:30:35 +0200 | <stefan_> | xmobar and xmonad are both in /usr/bin |
2023-05-11 12:31:45 +0200 | <geekosaur> | the "logging" it talks about is about formatting and sending xmonad state to xmobar |
2023-05-11 12:33:17 +0200 | <geekosaur> | there isn't really a way to log the way the combinators fit together or what they're doing, without copying their definitions locally and modifying them to use `XMonad.trace` |
2023-05-11 12:34:22 +0200 | <stefan_> | when I run xmonad with xinitrc it starts with xmobar (but without some of my other configs). As I see xmobar omits only when I start with xdm login screen (.xsession) |
2023-05-11 12:34:57 +0200 | <stefan_> | my .xsession contains only xrdb -merge ~/.Xresources && xmonad |
2023-05-11 12:40:51 +0200 | <stefan_> | https://termbin.com/mr3w |
2023-05-11 12:41:17 +0200 | <stefan_> | Here are some error from .xsession-errors which may be talkative |
2023-05-11 12:41:33 +0200 | stellacy | (~stellacy@gateway/tor-sasl/stellacy) (Remote host closed the connection) |
2023-05-11 12:43:08 +0200 | <geekosaur> | the only one of those of any interest is the BadAtom error, but it's from xmonad not xmobar |
2023-05-11 12:43:23 +0200 | <geekosaur> | unless it's somehow aborting the xmobar startup sequence |
2023-05-11 12:44:28 +0200 | stellacy | (~stellacy@gateway/tor-sasl/stellacy) |
2023-05-11 12:46:55 +0200 | stefan_ | (~stefan@176.120.176.183) (Quit: Lost terminal) |
2023-05-11 12:50:53 +0200 | stefan_ | (~stefan@176.120.176.183) |
2023-05-11 12:51:45 +0200 | <stefan_> | It all worked for me, I've just forget to put .xmobarrc with some reasonable config. Sorry for bothering you, thank you very much for response. |
2023-05-11 12:51:59 +0200 | <geekosaur> | hm, it should use a default |
2023-05-11 12:52:15 +0200 | <geekosaur> | whether you consider that default reasonable is another question, of course |
2023-05-11 12:52:58 +0200 | <stefan_> | it didn't started xmobar without .xmobarrc neither with startx nor xdm |
2023-05-11 12:53:56 +0200 | <stefan_> | it is my local trouble i think. I started xmobar without .xmobarrc manually, and it draws the bar, but always waits with "Updating...". Probably I don't have some packages for default subset of sensors. |
2023-05-11 12:54:48 +0200 | <geekosaur> | no, that indicates that it has `StdinReader` configured and is waiting for xmonad to write something to it |
2023-05-11 12:55:09 +0200 | <geekosaur> | you probably want `XMonadPropRead` these days |
2023-05-11 12:56:39 +0200 | <stefan_> | you mean to list workspaces etc? |
2023-05-11 12:56:47 +0200 | <geekosaur> | yes |
2023-05-11 12:57:14 +0200 | <stefan_> | yes, will look for some further configuration tutorial |
2023-05-11 12:57:26 +0200 | <geekosaur> | xmobar probably has one |
2023-05-11 12:58:32 +0200 | <geekosaur> | actually the arch wiki entry for xmobar is pretty good: https://wiki.archlinux.org/title/Xmobar |
2023-05-11 12:58:46 +0200 | stefan_ | uses arch mtw |
2023-05-11 12:58:52 +0200 | <stefan_> | btw* |
2023-05-11 12:59:13 +0200 | <geekosaur> | the arch wiki is an absolute goldmine of useful information |
2023-05-11 13:00:01 +0200 | <geekosaur> | I get frustrated at the way they manage their haskell packages (go read the entry for xmonad to see how to avoid getting locked out of it after an upgrade) but their documentation is just fabulous |
2023-05-11 13:00:18 +0200 | <stefan_> | I agree, it is awesome. Because otherwise arch wouldn't work at all :) |
2023-05-11 13:02:13 +0200 | <stefan_> | hm, to be true there's nothing about integration with xmonad workspaces in archwiki entry on xmobar |
2023-05-11 13:03:47 +0200 | <geekosaur> | that part you'll want to read on through the tutorial on: "Changing What XMonad Sends to Xmobar" |
2023-05-11 13:24:25 +0200 | <stefan_> | Well, now my xmobar is not rulable from xmonad.hs, it only takes properties from .xmobarrc, as I think. And xmonad doesn't sends info to xmobar |
2023-05-11 13:26:09 +0200 | <geekosaur> | what's in your .xmobarrc and xmonad.hs? |
2023-05-11 13:27:29 +0200 | <stefan_> | xmobarrc is the default config from arch wiki https://termbin.com/7lfr |
2023-05-11 13:28:07 +0200 | <stefan_> | xmonad.hs is a bit changed config from tutorial https://termbin.com/27yo |
2023-05-11 13:28:23 +0200 | <geekosaur> | okay, that one has nothing to handle xmonad config |
2023-05-11 13:28:54 +0200 | <geekosaur> | you want to add a `Run XMonadPropLog` to `commands`, and add `%XMonadPropLog%` somewhere in `template` |
2023-05-11 13:31:57 +0200 | <geekosaur> | sorry, apparently both of those are just `XMonadLog` |
2023-05-11 13:32:31 +0200 | <geekosaur> | (I don't use xmobar, I never remember the details of this) |
2023-05-11 14:20:08 +0200 | <stefan_> | Can't send data from xmonad to xmobar. I've changed template and command as it is said in documentation. But first, I don't know what parameters should I send to `Run XMonadLog`. Anyway, is is stuck with 'Updating...'. |
2023-05-11 14:21:04 +0200 | <stefan_> | As I see, xmobar doesn't need some special pipe routines in xmonad.hs as it can read XPROPS of main window? |
2023-05-11 14:21:35 +0200 | <stefan_> | logHook = xmonadPropLog =<< dynamicLogString myXmobarP |
2023-05-11 14:21:42 +0200 | <stefan_> | this hook doesn't work for me |
2023-05-11 14:22:29 +0200 | <geekosaur> | XMonadLog doesn't take parameters |
2023-05-11 14:23:17 +0200 | <stefan_> | well, then should work with just empty list [] |
2023-05-11 14:23:22 +0200 | <stefan_> | but it doesn't |
2023-05-11 14:27:43 +0200 | <geekosaur> | it doesn't even take the list |
2023-05-11 14:27:51 +0200 | <geekosaur> | just `Run XMonadLog` |
2023-05-11 14:29:22 +0200 | <stefan_> | Awww, yes, it didn't need empty list ) |
2023-05-11 14:30:14 +0200 | <stefan_> | geekosaur: Could I bind just pressing of modkey alone with no other keys? I want to have all the hotkeys like M-a, M-b, M-c, ... and just Modkey to start dmenu |
2023-05-11 14:30:58 +0200 | <geekosaur> | by binding it directly, yes, but it will trigger when you try to press those other hotkeys as well which is not what you want |
2023-05-11 14:32:22 +0200 | <geekosaur> | you would need a custom handleEventHook to catch keydown/keyup with no additional keypresses for it to work |
2023-05-11 14:32:33 +0200 | <geekosaur> | it's doable but not for beginners |
2023-05-11 14:33:00 +0200 | <stefan_> | ok, will live with win+p some time ) |
2023-05-11 14:33:29 +0200 | <stefan_> | need to reboot, see you soon |
2023-05-11 14:33:33 +0200 | stefan_ | (~stefan@176.120.176.183) (Quit: Lost terminal) |
2023-05-11 14:50:55 +0200 | mncheck | (~mncheck@193.224.205.254) (Remote host closed the connection) |
2023-05-11 14:51:12 +0200 | mncheck | (~mncheck@193.224.205.254) |
2023-05-11 14:56:35 +0200 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
2023-05-11 15:10:28 +0200 | deip[m] | (~deipmatri@2001:470:69fc:105::2:679e) |
2023-05-11 17:20:54 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Remote host closed the connection) |
2023-05-11 17:30:12 +0200 | sagax | (~sagax_nb@user/sagax) |
2023-05-11 17:38:55 +0200 | slide | (~slide@ip68-11-221-86.br.br.cox.net) |
2023-05-11 21:29:41 +0200 | ft | (~ft@p4fc2a88b.dip0.t-ipconnect.de) |
2023-05-11 22:31:36 +0200 | jade[m] | jadeOld[m] |