| 2023-11-02 00:40:29 +0100 | Groumf | (~Groumf@2a01:e0a:582:bb40:e5c6:f484:7015:1722) |
| 2023-11-02 02:20:44 +0100 | Groumf | (~Groumf@2a01:e0a:582:bb40:e5c6:f484:7015:1722) (Quit: Client closed) |
| 2023-11-02 02:21:04 +0100 | Groumf | (~Groumf@2a01:e0a:582:bb40:e5c6:f484:7015:1722) |
| 2023-11-02 03:40:18 +0100 | skarma | (~user@102.219.208.74) |
| 2023-11-02 04:53:05 +0100 | derpyxdhs | (~Thunderbi@user/derpyxdhs) |
| 2023-11-02 04:58:23 +0100 | thunderrd | (~thunderrd@183.182.114.97) |
| 2023-11-02 04:59:22 +0100 | thunderrd | (~thunderrd@183.182.114.97) (Remote host closed the connection) |
| 2023-11-02 05:01:04 +0100 | thunderrd | (~thunderrd@183.182.114.97) |
| 2023-11-02 05:01:53 +0100 | td_ | (~td@i5387092B.versanet.de) (Ping timeout: 260 seconds) |
| 2023-11-02 05:02:11 +0100 | thunderrd | (~thunderrd@183.182.114.97) (Remote host closed the connection) |
| 2023-11-02 05:03:16 +0100 | td_ | (~td@i5387090E.versanet.de) |
| 2023-11-02 05:08:57 +0100 | thunderrd | (~thunderrd@183.182.114.97) |
| 2023-11-02 05:19:02 +0100 | thunderrd | (~thunderrd@183.182.114.97) (Remote host closed the connection) |
| 2023-11-02 05:23:36 +0100 | <skarma> | this is my first time trying out `xmonad` as a `wm`, and I must say it is as frustrating as it is fun leaning haskell by configuring `xmonad` |
| 2023-11-02 06:08:21 +0100 | [Leary] | (~Leary]@user/Leary/x-0910699) (Remote host closed the connection) |
| 2023-11-02 06:08:37 +0100 | [Leary] | (~Leary]@user/Leary/x-0910699) |
| 2023-11-02 06:10:51 +0100 | <Groumf> | skarma it really isn't the best way... tbh, I did the same back in the days.... |
| 2023-11-02 06:11:34 +0100 | <Groumf> | I really learned ML after taking a course in OCaml. |
| 2023-11-02 06:12:07 +0100 | <Groumf> | But hey, if you just want some features of xmonad, go ahead. It's just that you are probably missing on a lot of things. |
| 2023-11-02 06:48:29 +0100 | skarma | (~user@102.219.208.74) (Ping timeout: 248 seconds) |
| 2023-11-02 07:36:40 +0100 | chomwitt | (~chomwitt@2a02:587:7a2d:bc00:1ac0:4dff:fedb:a3f1) |
| 2023-11-02 08:53:07 +0100 | derpyxdhs | (~Thunderbi@user/derpyxdhs) (Quit: derpyxdhs) |
| 2023-11-02 09:12:01 +0100 | td_ | (~td@i5387090E.versanet.de) (Ping timeout: 260 seconds) |
| 2023-11-02 09:13:30 +0100 | td_ | (~td@i5387092B.versanet.de) |
| 2023-11-02 10:45:31 +0100 | ft | (~ft@p4fc2a529.dip0.t-ipconnect.de) (Quit: leaving) |
| 2023-11-02 10:58:06 +0100 | cfricke | (~cfricke@user/cfricke) |
| 2023-11-02 11:43:08 +0100 | <Solid> | I know that there are people who've been using XMonad much longer than myself (not that that's an achievement) and still don't know any Haskell |
| 2023-11-02 11:43:51 +0100 | <Solid> | so it'll probably be fine :) |
| 2023-11-02 12:14:04 +0100 | ml| | (~ml|@user/ml/x-5298235) (Ping timeout: 258 seconds) |
| 2023-11-02 13:05:09 +0100 | cfricke | (~cfricke@user/cfricke) (Quit: WeeChat 4.0.5) |
| 2023-11-02 13:40:30 +0100 | ml| | (~ml|@user/ml/x-5298235) |
| 2023-11-02 14:50:14 +0100 | xmonadtrack | (~xmonadtra@user/geekosaur/bot/xmonadtrack) (Remote host closed the connection) |
| 2023-11-02 15:01:24 +0100 | chomwitt | (~chomwitt@2a02:587:7a2d:bc00:1ac0:4dff:fedb:a3f1) (Ping timeout: 240 seconds) |
| 2023-11-02 15:01:37 +0100 | haskellbridge | (~haskellbr@069-135-003-034.biz.spectrum.com) (Remote host closed the connection) |
| 2023-11-02 15:05:08 +0100 | haskellbridge | (~haskellbr@069-135-003-034.biz.spectrum.com) |
| 2023-11-02 15:05:10 +0100 | xmonadtrack | (~xmonadtra@069-135-003-034.biz.spectrum.com) |
| 2023-11-02 15:05:10 +0100 | xmonadtrack | (~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host) |
| 2023-11-02 15:05:10 +0100 | xmonadtrack | (~xmonadtra@user/geekosaur/bot/xmonadtrack) |
| 2023-11-02 15:58:22 +0100 | mc47 | (~mc47@xmonad/TheMC47) |
| 2023-11-02 16:15:30 +0100 | chomwitt | (~chomwitt@2a02:587:7a2d:bc00:1ac0:4dff:fedb:a3f1) |
| 2023-11-02 16:30:48 +0100 | Manu38 | (~Manu38@2a01:e0a:96:a450:3b24:599f:8c6f:357d) |
| 2023-11-02 16:32:10 +0100 | <Manu38> | Hi there |
| 2023-11-02 16:32:31 +0100 | <Manu38> | Question of the day, I just added the `Alsa` plugin to my `xmobar`. |
| 2023-11-02 16:33:03 +0100 | <Manu38> | It works perfectly fine as long I am using the built-in speakers (I am on a dell laptop). |
| 2023-11-02 16:33:52 +0100 | <Manu38> | But when I plugin some speakers and switch the sound output to it, the xmobar is no more updated when I switch the volume. |
| 2023-11-02 16:36:28 +0100 | <Manu38> | Any idea where I should look ? (I guess in understanding linux sound architecure :)) |
| 2023-11-02 16:41:03 +0100 | Manu38 | (~Manu38@2a01:e0a:96:a450:3b24:599f:8c6f:357d) (Ping timeout: 248 seconds) |
| 2023-11-02 16:47:10 +0100 | tremon | (~tremon@83.80.159.219) |
| 2023-11-02 16:56:17 +0100 | todi | (~todi@p4fd1a3e6.dip0.t-ipconnect.de) |
| 2023-11-02 17:08:33 +0100 | diep | (~diep@172-104-137-130.ip.linodeusercontent.com) |
| 2023-11-02 17:19:52 +0100 | <haskellbridge> | <HAL> video |
| 2023-11-02 17:34:29 +0100 | <geekosaur> | Manu38, I don't know xmobar very well but make sure you're specifying Master instead of a specific output |
| 2023-11-02 17:34:54 +0100 | <geekosaur> | (yes, I know they're gone, but I also know they check the logs) |
| 2023-11-02 17:44:05 +0100 | haskellbridge | (~haskellbr@069-135-003-034.biz.spectrum.com) (Remote host closed the connection) |
| 2023-11-02 17:44:38 +0100 | haskellbridge | (~haskellbr@069-135-003-034.biz.spectrum.com) |
| 2023-11-02 17:44:38 +0100 | haskellbridge | (~haskellbr@069-135-003-034.biz.spectrum.com) (Read error: Connection reset by peer) |
| 2023-11-02 17:44:58 +0100 | haskellbridge | (~haskellbr@069-135-003-034.biz.spectrum.com) |
| 2023-11-02 17:58:12 +0100 | diep | (~diep@172-104-137-130.ip.linodeusercontent.com) (Remote host closed the connection) |
| 2023-11-02 18:00:14 +0100 | diep | (~diep@172-104-137-130.ip.linodeusercontent.com) |
| 2023-11-02 18:10:07 +0100 | diep | (~diep@172-104-137-130.ip.linodeusercontent.com) (Remote host closed the connection) |
| 2023-11-02 18:16:57 +0100 | diep | (~diep@172-104-137-130.ip.linodeusercontent.com) |
| 2023-11-02 18:22:51 +0100 | derpyxdhs | (~Thunderbi@user/derpyxdhs) |
| 2023-11-02 18:23:45 +0100 | diep | (~diep@172-104-137-130.ip.linodeusercontent.com) (Remote host closed the connection) |
| 2023-11-02 18:30:01 +0100 | haskellbridge | (~haskellbr@069-135-003-034.biz.spectrum.com) (Remote host closed the connection) |
| 2023-11-02 18:30:38 +0100 | haskellbridge | (~haskellbr@069-135-003-034.biz.spectrum.com) |
| 2023-11-02 18:37:23 +0100 | derpyxdhs | (~Thunderbi@user/derpyxdhs) (Quit: derpyxdhs) |
| 2023-11-02 19:43:08 +0100 | Mion | (~Urist@archlinux/op/MrElendig) (Quit: Brb, going to the moon) |
| 2023-11-02 19:48:20 +0100 | todi | (~todi@p4fd1a3e6.dip0.t-ipconnect.de) (Quit: ZNC - https://znc.in) |
| 2023-11-02 19:55:54 +0100 | MrElendig | (~Urist@archlinux/op/MrElendig) |
| 2023-11-02 20:51:52 +0100 | Manu38 | (~Manu38@2a01:e0a:96:a450:90b3:37ae:5ead:2d6f) |
| 2023-11-02 20:53:43 +0100 | <Manu38> | geekosaur yes I did specified `Master` with the following command in my `xmobar` config file : `Run Alsa "default" "Master" []` |
| 2023-11-02 20:54:48 +0100 | <geekosaur> | I guess you'll have to find someone who knows xmobar then, sorry |
| 2023-11-02 20:55:17 +0100 | <geekosaur> | (I use xmonad as the window manager for MATE so I have a couple of mate-panels) |
| 2023-11-02 21:42:00 +0100 | <Manu38> | Thank you geekosaur Anyone @here using the `Alsa` plugin of `xmobar` ? |
| 2023-11-02 21:52:10 +0100 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2023-11-02 22:17:26 +0100 | <Manu38> | liskin maybe ? Since looking at that on the web I reached your "Linux, media keys and multiple players" blog post :) |
| 2023-11-02 22:17:58 +0100 | <liskin> | Manu38: I don't really use xmobar's plugins tbh |
| 2023-11-02 22:18:10 +0100 | <Manu38> | Shit :) |
| 2023-11-02 22:18:20 +0100 | <liskin> | as much as I love Haskell, xmobar is best kept minimal |
| 2023-11-02 22:18:43 +0100 | <liskin> | so all the actually interesting stuff in my xmobar is bash/python scripts setting X root window properties |
| 2023-11-02 22:18:46 +0100 | <Manu38> | Probably the best solution for me is to remove this sound plugin. |
| 2023-11-02 22:18:59 +0100 | ft | (~ft@p4fc2a529.dip0.t-ipconnect.de) |
| 2023-11-02 22:19:37 +0100 | <liskin> | that being said, perhaps you can follow my lead and put together a script or something that watches the volume and then sets a property for xmobar to display |
| 2023-11-02 22:20:02 +0100 | <liskin> | this way you don't need to limit yourself to weird unmtained buggy impls in xmobar and just use whatever works :-) |
| 2023-11-02 22:21:16 +0100 | <Manu38> | Yep. But my Haskell skills are way to weak for now to jump into that. So I'm adding it to my todo list for a later time and will remove the sound indicator in my `xmobar` for now. |
| 2023-11-02 22:21:56 +0100 | <Manu38> | The most important thing for now, is to have my shortcuts operational. |
| 2023-11-02 22:22:20 +0100 | <liskin> | pactl get-sink-volume @DEFAULT_SINK@ | grep -Po '\d+(?=%)' | head -n 1 |
| 2023-11-02 22:22:34 +0100 | <liskin> | you can just put thin into a Run and have it refresh every couple seconds… :-D |
| 2023-11-02 22:22:39 +0100 | <liskin> | s/thin/this/ |
| 2023-11-02 22:23:04 +0100 | <liskin> | hm, not Run, the other thing, what was it called |
| 2023-11-02 22:23:57 +0100 | <Manu38> | I was not aware that one could run arbitrary commands in `xmobar`. |
| 2023-11-02 22:24:05 +0100 | <Manu38> | Let's check that right now ! |
| 2023-11-02 22:24:25 +0100 | <liskin> | Run Com "bash" ["-c", "pactl get-sink-volume @DEFAULT_SINK@ | grep -Po '\d+(?=%)' | head -n 1"] "volume" 10 |
| 2023-11-02 22:24:27 +0100 | <liskin> | that sort of thing |
| 2023-11-02 22:24:52 +0100 | <liskin> | not exactly power efficient though, wouldn't want to have this on a laptop |
| 2023-11-02 22:25:17 +0100 | <liskin> | although with modern hardware, doesn't really make much difference any more |
| 2023-11-02 22:25:24 +0100 | <Manu38> | Because of polling instead of event base you mean ? |
| 2023-11-02 22:25:47 +0100 | <liskin> | that, and also because it's launching a shell and three subprocesses every second |
| 2023-11-02 22:26:31 +0100 | <Manu38> | I don't think this could be noticeable in terms of battery autonomy. Do you think so ? |
| 2023-11-02 22:28:50 +0100 | <liskin> | who knows, it could be a 0.1 watt more or something on this old crap I have |
| 2023-11-02 22:29:14 +0100 | <liskin> | I've shaved a couple deciwatts off by making xmobar refresh only once a second instead of like 5 times |
| 2023-11-02 22:29:36 +0100 | <liskin> | (was it worth the time? probably not, lol) |
| 2023-11-02 22:30:52 +0100 | <Manu38> | (lol) |
| 2023-11-02 22:31:27 +0100 | <Manu38> | Anyway, thank you for the tips of running external process in Xmobar, but I will stay without sound indicator for now :) |
| 2023-11-02 22:32:17 +0100 | <liskin> | sensible choice |
| 2023-11-02 22:32:53 +0100 | liskin | never had one anyway; headphones battery level is much more useful these days |
| 2023-11-02 22:34:31 +0100 | <Manu38> | I don't have battery powered headphones but I am using old style ones and speakers since I'am most of the time alone in my working environment. |
| 2023-11-02 22:53:00 +0100 | chomwitt | (~chomwitt@2a02:587:7a2d:bc00:1ac0:4dff:fedb:a3f1) (Ping timeout: 240 seconds) |
| 2023-11-02 23:14:57 +0100 | todi | (~todi@p4fd1a3e6.dip0.t-ipconnect.de) |
| 2023-11-02 23:18:11 +0100 | sundbry | (~quassel@2600:1700:38c6:180:a1da:9e07:832c:1349) |
| 2023-11-02 23:32:19 +0100 | <Manu38> | liskin if you are still, here I am trying to understand how you implemented communication between `xmonad` and `xmobar` through X11 properties (since not for the volume stuff, but for a keyboard indicator I'll need to do it soon). |
| 2023-11-02 23:32:45 +0100 | <Manu38> | In your `xmobar.hs` file, you use for example a property called `_XMOBAR_DND` |
| 2023-11-02 23:33:20 +0100 | <Manu38> | To display it's content in your status bar, is that correct ? |
| 2023-11-02 23:34:18 +0100 | <liskin> | yeah |
| 2023-11-02 23:34:48 +0100 | <liskin> | it's set this way: xprop -root -f _XMOBAR_DND 8u -set _XMOBAR_DND "blah blah whatever" |
| 2023-11-02 23:36:02 +0100 | <Manu38> | Where is that thing set ? I was not able to see it, and how your `xmonad.hs` file links to that ? |
| 2023-11-02 23:38:17 +0100 | <liskin> | it's not set by xmonad itself |
| 2023-11-02 23:38:35 +0100 | <liskin> | https://github.com/search?q=repo%3Aliskin%2Fdotfiles%20_xmobar_dnd&type=code |
| 2023-11-02 23:38:38 +0100 | <Manu38> | By a deamon launched at startup by `xmonad` or by your system ? |
| 2023-11-02 23:40:30 +0100 | <Manu38> | Ok thanks, the answer is "by a script called at login time AND by a deamon". |
| 2023-11-02 23:44:23 +0100 | <liskin> | yeah something like that :-) |
| 2023-11-02 23:51:16 +0100 | <geekosaur> | argh |
| 2023-11-02 23:52:05 +0100 | <geekosaur> | I think I'm going to let this latest sit until tomorrow and hope another night's sleep makes me feel better (I'm ill) |
| 2023-11-02 23:52:33 +0100 | <geekosaur> | probably best not to respond to someone when I feel lousy and am tempted to take it out on someone else |
| 2023-11-02 23:53:18 +0100 | <Manu38> | geekosaur nothing related to me, do you confirm ? |
| 2023-11-02 23:53:27 +0100 | <geekosaur> | I confirm |
| 2023-11-02 23:54:09 +0100 | <geekosaur> | we have someone who seems to think (a) xmonad for wayland can be written with just an additional xmonad module or two, and thinks xwayland will somehow help after being told it won't |
| 2023-11-02 23:57:17 +0100 | <geekosaur> | oh, and linked me to something written by someone who clearly didn't know what they were doing (wait, put xmonad in the background and then loop on xhost to keep the session open? what?) and thinks it's xmonad's job to "do this better" |
| 2023-11-02 23:57:40 +0100 | <geekosaur> | no, it's the job of whoever wrote that idiotic script to _write it properly_ |
| 2023-11-02 23:57:45 +0100 | <liskin> | I agree it'd be better to get some rest |
| 2023-11-02 23:58:32 +0100 | <liskin> | as far as I understand it, that linked thing actually might work, so creating additional misunderstandings by not trying it and telling everyone else that it doesn't isn't really the best way forward |
| 2023-11-02 23:59:06 +0100 | <geekosaur> | oh, it'll work |
| 2023-11-02 23:59:13 +0100 | <liskin> | (what I think it does is it starts a wayland compositor with rootful Xwayland, and then running xmonad inside of it) |
| 2023-11-02 23:59:42 +0100 | <geekosaur> | yes, but it forks xmonad into the background and then loops on xhost to keep the session open. what happened to `exec xmonad`? |
| 2023-11-02 23:59:54 +0100 | <geekosaur> | should work just as well with xwayland |