| 2022-08-06 00:09:59 +0200 | <sogens> | bit of a n00b question but but how do i set my cursor theme in xmonad |
| 2022-08-06 00:10:13 +0200 | <sogens> | ive set it in my xresources but it doesnt completely change it |
| 2022-08-06 00:11:07 +0200 | <geekosaur> | cursor theme is a toolkit attribute, you need something that can edit gtk2 and/or gtk3 config files and set the theme there |
| 2022-08-06 00:11:16 +0200 | <geekosaur> | lxappearance might work? |
| 2022-08-06 00:11:24 +0200 | <sogens> | ok ill try that |
| 2022-08-06 00:14:38 +0200 | <sogens> | worked like a charm thanks |
| 2022-08-06 00:18:22 +0200 | catman | (~catman@user/catman) (Quit: WeeChat 3.6) |
| 2022-08-06 00:34:25 +0200 | sogens | (~sogens@211.30.173.20) (Ping timeout: 268 seconds) |
| 2022-08-06 00:35:47 +0200 | sogens | (~sogens@gateway/vpn/pia/sogens) |
| 2022-08-06 01:35:39 +0200 | mvk | (~mvk@2607:fea8:5ce3:8500::d5f2) (Ping timeout: 244 seconds) |
| 2022-08-06 01:56:28 +0200 | thyriaen | (~thyriaen@2a02:8109:8340:686c:3cdc:1de0:eddb:5de6) |
| 2022-08-06 02:01:18 +0200 | <Hash> | May I inquire |
| 2022-08-06 02:01:24 +0200 | <Hash> | What distros do you guys use for your daily use? |
| 2022-08-06 02:02:21 +0200 | mvk | (~mvk@2607:fea8:5ce3:8500::d5f2) |
| 2022-08-06 02:03:04 +0200 | <geekosaur[m]> | Ubuntu |
| 2022-08-06 02:03:09 +0200 | <thyriaen> | fedora and pop os |
| 2022-08-06 02:03:20 +0200 | <Hash> | geekosaur[m]: lts or normal? |
| 2022-08-06 02:03:54 +0200 | <Hash> | I'm thinking of switching to a rolling release maybe... |
| 2022-08-06 02:05:19 +0200 | thyriaen | (~thyriaen@2a02:8109:8340:686c:3cdc:1de0:eddb:5de6) (Quit: Leaving) |
| 2022-08-06 02:06:04 +0200 | <geekosaur> | lts |
| 2022-08-06 02:06:22 +0200 | <Hash> | What browser do you use daily? |
| 2022-08-06 02:06:33 +0200 | <Hash> | chrome/chromium/firefox/something else? |
| 2022-08-06 02:06:52 +0200 | <geekosaur> | chrome |
| 2022-08-06 02:07:01 +0200 | <Hash> | Same. |
| 2022-08-06 02:07:29 +0200 | <Hash> | system ssd is 12 year old, going bad, got new 2tb nvme, trying to decide what to do now. |
| 2022-08-06 02:15:28 +0200 | sogens | (~sogens@gateway/vpn/pia/sogens) (Quit: WeeChat 3.5) |
| 2022-08-06 02:15:39 +0200 | sogens | (~sogens@gateway/vpn/pia/sogens) |
| 2022-08-06 02:17:26 +0200 | logzet | (~quassel@2001:9e8:e51f:8d00:dabb:c1ff:fed3:a1b9) (Ping timeout: 240 seconds) |
| 2022-08-06 02:17:52 +0200 | logzet | (~quassel@2001:9e8:e531:b700:dabb:c1ff:fed3:a1b9) |
| 2022-08-06 02:17:55 +0200 | <geekosaur> | I'd stick with ubuntu lts, but I don't promise what works for me works for anyone else |
| 2022-08-06 02:18:11 +0200 | sogens | (~sogens@gateway/vpn/pia/sogens) (Client Quit) |
| 2022-08-06 02:18:22 +0200 | sogens | (~sogens@gateway/vpn/pia/sogens) |
| 2022-08-06 02:23:43 +0200 | mvk | (~mvk@2607:fea8:5ce3:8500::d5f2) (Ping timeout: 244 seconds) |
| 2022-08-06 04:03:33 +0200 | banc | (banc@gateway/vpn/airvpn/banc) (Ping timeout: 252 seconds) |
| 2022-08-06 04:20:03 +0200 | doppo | (~doppo@2604:180::e0fc:a07f) (Remote host closed the connection) |
| 2022-08-06 04:20:37 +0200 | doppo | (~doppo@2604:180::e0fc:a07f) |
| 2022-08-06 04:23:08 +0200 | banc | (banc@gateway/vpn/airvpn/banc) |
| 2022-08-06 04:36:42 +0200 | td_ | (~td@muedsl-82-207-238-171.citykom.de) (Ping timeout: 245 seconds) |
| 2022-08-06 04:38:46 +0200 | td_ | (~td@94.134.91.51) |
| 2022-08-06 05:22:14 +0200 | sogens | (~sogens@gateway/vpn/pia/sogens) (Quit: WeeChat 3.5) |
| 2022-08-06 05:24:03 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 05:57:36 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 244 seconds) |
| 2022-08-06 06:00:31 +0200 | sogens | (~sogens@211.30.173.20) (Quit: WeeChat 3.5) |
| 2022-08-06 06:00:49 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 06:17:50 +0200 | Guest51 | (~Guest51@223.235.202.254) |
| 2022-08-06 06:18:13 +0200 | Guest51 | (~Guest51@223.235.202.254) (Client Quit) |
| 2022-08-06 06:30:38 +0200 | logzet | (~quassel@2001:9e8:e531:b700:dabb:c1ff:fed3:a1b9) (Ping timeout: 240 seconds) |
| 2022-08-06 06:54:46 +0200 | sogens | (~sogens@211.30.173.20) (Quit: WeeChat 3.5) |
| 2022-08-06 07:06:45 +0200 | qbt | (~qbt@user/edun) |
| 2022-08-06 07:18:01 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 07:45:00 +0200 | [Leary] | (~Leary]@122-58-224-198-vdsl.sparkbb.co.nz) (Ping timeout: 268 seconds) |
| 2022-08-06 07:50:07 +0200 | sogens | (~sogens@211.30.173.20) (Quit: WeeChat 3.5) |
| 2022-08-06 07:50:23 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 08:41:08 +0200 | sogens | (~sogens@211.30.173.20) (Quit: WeeChat 3.5) |
| 2022-08-06 08:42:26 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 10:32:09 +0200 | liskin | uses the rolling Debian testing and wouldn't ever want to go back to a non-rolling distro |
| 2022-08-06 10:43:47 +0200 | sogens | (~sogens@211.30.173.20) (Quit: WeeChat 3.5) |
| 2022-08-06 10:45:09 +0200 | logzet | (~quassel@2001:9e8:e531:b700:dabb:c1ff:fed3:a1b9) |
| 2022-08-06 10:45:38 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 11:01:11 +0200 | sogens | (~sogens@211.30.173.20) (Ping timeout: 252 seconds) |
| 2022-08-06 11:03:12 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 11:36:10 +0200 | [Leary] | (~Leary]@122-58-224-198-vdsl.sparkbb.co.nz) |
| 2022-08-06 11:37:57 +0200 | benin0 | (~benin@183.82.25.162) |
| 2022-08-06 11:52:57 +0200 | qbt | (~qbt@user/edun) (Ping timeout: 245 seconds) |
| 2022-08-06 12:11:06 +0200 | zim0369 | (~zim0369@42.108.230.29) |
| 2022-08-06 12:12:32 +0200 | sogens | (~sogens@211.30.173.20) (Ping timeout: 245 seconds) |
| 2022-08-06 12:13:01 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 12:20:00 +0200 | <zim0369> | I'm unable to configure xmobar |
| 2022-08-06 12:20:19 +0200 | <zim0369> | I have followed the instructions in the documentation |
| 2022-08-06 12:20:36 +0200 | <zim0369> | https://paste.tomsmeding.com/Wu6a9cBc |
| 2022-08-06 12:20:40 +0200 | <zim0369> | current config |
| 2022-08-06 12:32:10 +0200 | sogens | (~sogens@211.30.173.20) (Quit: WeeChat 3.5) |
| 2022-08-06 12:33:33 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 12:48:21 +0200 | sogens | (~sogens@211.30.173.20) (Quit: WeeChat 3.5) |
| 2022-08-06 12:54:45 +0200 | zim0369[m] | (~zim0369ma@2001:470:69fc:105::2:5d43) |
| 2022-08-06 12:55:59 +0200 | <zim0369[m]> | 🧱 checking matrix/irc sync |
| 2022-08-06 12:59:51 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 13:00:27 +0200 | zim0369 | (~zim0369@42.108.230.29) (Quit: Client closed) |
| 2022-08-06 13:01:01 +0200 | sogens | (~sogens@211.30.173.20) (Client Quit) |
| 2022-08-06 13:02:19 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 13:12:31 +0200 | zim0369 | (~zim0369@42.108.235.251) |
| 2022-08-06 13:18:59 +0200 | sogens | (~sogens@211.30.173.20) (Quit: WeeChat 3.5) |
| 2022-08-06 13:25:20 +0200 | zim0369 | (~zim0369@42.108.235.251) (Ping timeout: 252 seconds) |
| 2022-08-06 13:45:23 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 13:59:44 +0200 | qbt | (~qbt@user/edun) |
| 2022-08-06 14:08:10 +0200 | zim0369 | (~zim0369@114.143.131.219) |
| 2022-08-06 14:16:37 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-08-06 14:47:50 +0200 | zim0369 | (~zim0369@114.143.131.219) (Ping timeout: 252 seconds) |
| 2022-08-06 14:56:39 +0200 | qbt | (~qbt@user/edun) (Quit: WeeChat 3.5) |
| 2022-08-06 15:48:00 +0200 | sogens | (~sogens@211.30.173.20) (Quit: WeeChat 3.5) |
| 2022-08-06 15:52:11 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 16:23:37 +0200 | qbt | (~qbt@user/edun) |
| 2022-08-06 16:24:11 +0200 | sogens | (~sogens@211.30.173.20) (Quit: WeeChat 3.5) |
| 2022-08-06 16:24:27 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 16:25:23 +0200 | <zim0369[m]> | I need help with xmobar |
| 2022-08-06 16:25:25 +0200 | <zim0369[m]> | my xmobar isn't working |
| 2022-08-06 16:25:30 +0200 | <zim0369[m]> | it doesn't appear on login |
| 2022-08-06 16:25:53 +0200 | <zim0369[m]> | pastebin: https://paste.tomsmeding.com/29D6HNKS |
| 2022-08-06 16:26:03 +0200 | <zim0369[m]> | I have configured everything according to the docs |
| 2022-08-06 17:08:06 +0200 | <geekosaur[m]> | Do any error messages show on the text console? (CTRL+ALT+F1) |
| 2022-08-06 17:12:31 +0200 | sogens | (~sogens@211.30.173.20) (Quit: WeeChat 3.5) |
| 2022-08-06 17:14:11 +0200 | benin0 | (~benin@183.82.25.162) (Quit: The Lounge - https://thelounge.chat) |
| 2022-08-06 17:25:55 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 17:27:19 +0200 | sogens | (~sogens@211.30.173.20) (Client Quit) |
| 2022-08-06 17:29:15 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 17:30:47 +0200 | <geekosaur[m]> | zim0369: ^^ |
| 2022-08-06 17:40:19 +0200 | sogens | (~sogens@211.30.173.20) (Quit: WeeChat 3.5) |
| 2022-08-06 17:55:57 +0200 | <zim0369[m]> | geekosaur: umm... my session is in the same tty |
| 2022-08-06 18:00:36 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2022-08-06 18:01:50 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 18:07:30 +0200 | <geekosaur> | you sure? startx usually runs the graphical session in tty7 and leaves the text session in place so you can see error messages |
| 2022-08-06 18:07:44 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) |
| 2022-08-06 18:23:02 +0200 | sogens | (~sogens@211.30.173.20) (Ping timeout: 240 seconds) |
| 2022-08-06 18:25:13 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 18:36:23 +0200 | sogens | (~sogens@211.30.173.20) (Quit: WeeChat 3.5) |
| 2022-08-06 18:36:57 +0200 | <geekosaur[m]> | (resending via matrix as IRC hasn't made it here yet) are you sure? starts usually puts the graphical display on tty7 so you can check the text console for error messages |
| 2022-08-06 18:40:32 +0200 | <geekosaur[m]> | s/starts/startx/ |
| 2022-08-06 18:42:53 +0200 | <zim0369[m]> | No |
| 2022-08-06 18:43:05 +0200 | <zim0369[m]> | I start my session with startx |
| 2022-08-06 18:43:17 +0200 | <zim0369[m]> | And it starts in tty1 |
| 2022-08-06 18:44:20 +0200 | <geekosaur> | then you have no way to swee errors and probably lose all the conmtents of the text console when the session ends |
| 2022-08-06 18:44:54 +0200 | <zim0369[m]> | prolly because i had once configured my machine to be very quiet |
| 2022-08-06 18:45:02 +0200 | <zim0369[m]> | no verbose stuff |
| 2022-08-06 18:45:39 +0200 | <zim0369[m]> | my xmonad session starts just fine but after login i see no xmobar. I'm able to launch xmobar through the console |
| 2022-08-06 18:46:18 +0200 | <geekosaur> | the point was to look for any error messages that might be showing up. you are saying you have no way to get at the error messages |
| 2022-08-06 18:47:08 +0200 | <zim0369[m]> | Umm.. i'll have to spend hours trying to reverse configure all the stuff i did |
| 2022-08-06 18:47:13 +0200 | <zim0369[m]> | i have a very quiet boot |
| 2022-08-06 18:47:15 +0200 | <zim0369[m]> | ughh... |
| 2022-08-06 18:47:18 +0200 | <zim0369[m]> | is there no other way? |
| 2022-08-06 18:47:26 +0200 | <zim0369[m]> | i have another laptop |
| 2022-08-06 18:47:33 +0200 | <zim0369[m]> | do i test my config on that? |
| 2022-08-06 18:47:36 +0200 | <geekosaur> | or redirect the output of startx into a file (startx >.xsession-errors 2>&1) |
| 2022-08-06 18:48:02 +0200 | <zim0369[m]> | oh |
| 2022-08-06 18:51:35 +0200 | <zim0369[m]> | okay, now i started my session with that |
| 2022-08-06 18:51:38 +0200 | qbt | (~qbt@user/edun) (Quit: WeeChat 3.5) |
| 2022-08-06 18:51:42 +0200 | <zim0369[m]> | where did it put the contents? |
| 2022-08-06 18:51:49 +0200 | <zim0369[m]> | found it |
| 2022-08-06 18:51:54 +0200 | <zim0369[m]> | ill pastebin |
| 2022-08-06 18:52:42 +0200 | <zim0369[m]> | geekosaur: here https://paste.tomsmeding.com/E5XBpnZk |
| 2022-08-06 18:54:02 +0200 | <geekosaur[m]> | Line 21 |
| 2022-08-06 18:54:52 +0200 | <Solid> | it's probably .cabal/bin/xmobar |
| 2022-08-06 18:55:25 +0200 | <geekosaur[m]> | Are you sure you didn't mean `/home/zim/.cabal/bin/xmobar`? |
| 2022-08-06 18:56:59 +0200 | <zim0369[m]> | changed the config to use the correct path |
| 2022-08-06 18:57:05 +0200 | <zim0369[m]> | startx again and here's: the output |
| 2022-08-06 18:57:06 +0200 | <zim0369[m]> | https://paste.tomsmeding.com/Gd6IatCw |
| 2022-08-06 18:58:45 +0200 | <geekosaur[m]> | Not sure why it's trying to use dbus |
| 2022-08-06 18:58:54 +0200 | <zim0369[m]> | I've made use of this redirecting so many times. this should've come to my mind before. im dumb |
| 2022-08-06 18:59:13 +0200 | <geekosaur[m]> | But it looks like xmobar should have started |
| 2022-08-06 18:59:23 +0200 | <zim0369[m]> | why is matrix's reply not working... anyways |
| 2022-08-06 18:59:45 +0200 | <geekosaur[m]> | What's your config again? |
| 2022-08-06 19:00:00 +0200 | <zim0369[m]> | geekosaur[m]: yes, actually before few hours ago i had correct full path to as you asked me to put but even then it wasn't starting |
| 2022-08-06 19:00:05 +0200 | <zim0369[m]> | geekosaur[m]: ill pastebin |
| 2022-08-06 19:00:48 +0200 | <geekosaur[m]> | Matrix replies don't play well with IRC |
| 2022-08-06 19:00:58 +0200 | <zim0369[m]> | https://paste.tomsmeding.com/AIc8csho |
| 2022-08-06 19:03:10 +0200 | <geekosaur[m]> | You don't have `avoidStruts` around your layout so it is probably being covered up |
| 2022-08-06 19:04:20 +0200 | <zim0369[m]> | I did not understand avoidStruts documentation so i thought it wasn't necessary |
| 2022-08-06 19:04:26 +0200 | <zim0369[m]> | ill use that |
| 2022-08-06 19:04:28 +0200 | <zim0369[m]> | brb |
| 2022-08-06 19:12:23 +0200 | <zim0369[m]> | still no luck |
| 2022-08-06 19:12:28 +0200 | <zim0369[m]> | https://pastebin.com/uTQP2YrC |
| 2022-08-06 19:12:38 +0200 | <zim0369[m]> | sorry for this pastebin geekosaur i'm being rate limite |
| 2022-08-06 19:12:41 +0200 | <zim0369[m]> | s/limite/limited/ |
| 2022-08-06 19:14:54 +0200 | <geekosaur> | the session log is no longer helpful, as far as I can tell from that it's being started |
| 2022-08-06 19:15:32 +0200 | <zim0369[m]> | xmobar process isn't present |
| 2022-08-06 19:15:47 +0200 | <geekosaur> | at this point I think I need Solid or someone else more familiar with the xmobar side of things |
| 2022-08-06 19:16:24 +0200 | <geekosaur> | hrrm. that implies xmobar is the one trying to register with dbus |
| 2022-08-06 19:16:49 +0200 | <geekosaur> | you may have to modify your .xinitrc or equivalent to start it |
| 2022-08-06 19:17:53 +0200 | <zim0369[m]> | does that have any downsides |
| 2022-08-06 19:18:27 +0200 | <geekosaur> | it would be a trifle wasteful if nothing were using it, but I guess recent xmobar does listen on dbus |
| 2022-08-06 19:18:40 +0200 | <geekosaur> | dbus-launch --exit-with-session xmonad |
| 2022-08-06 19:19:56 +0200 | <Solid> | xmobar can be compiled with dbus support, but afaik it's off by default |
| 2022-08-06 19:20:29 +0200 | <geekosaur> | something is failing to connect to dbus here: https://pastebin.com/uTQP2YrC |
| 2022-08-06 19:21:05 +0200 | <Solid> | sure that it's xmobar? |
| 2022-08-06 19:21:11 +0200 | <geekosaur> | no 😞 |
| 2022-08-06 19:21:22 +0200 | <zim0369[m]> | `dbus-launch --exit-with-session xmonad` |
| 2022-08-06 19:21:24 +0200 | <zim0369[m]> | https://pastebin.com/fHTdpSdk |
| 2022-08-06 19:21:27 +0200 | <Solid> | zim0369[m]: does xmobar appear when you start it inside of a terminal? |
| 2022-08-06 19:21:30 +0200 | <geekosaur> | but we no longer get the "xmobar command not found" |
| 2022-08-06 19:21:39 +0200 | <zim0369[m]> | Solid: yes |
| 2022-08-06 19:21:51 +0200 | <zim0369[m]> | geekosaur: because i entered the current path |
| 2022-08-06 19:22:12 +0200 | <Solid> | zim0369[m]: are you doing `xmobar` or `~/.cabal/bin/xmobar`? Perhaps you're starting a different one |
| 2022-08-06 19:22:17 +0200 | <geekosaur> | zim0369[m], you can't just runb xmonad when another one is running, you need to replace the xmonad invocation in your .cxinitrc with the dbus-launch thing |
| 2022-08-06 19:22:43 +0200 | <geekosaur> | (the error you got indicates that another xmonad is already registered as the window manager) |
| 2022-08-06 19:23:00 +0200 | <geekosaur> | .xinitrc sorry |
| 2022-08-06 19:23:03 +0200 | <zim0369[m]> | Solid: /home/zim/.cabal/bin/xmobar |
| 2022-08-06 19:23:34 +0200 | <zim0369[m]> | could it be because i installed xmond from cabal then from git |
| 2022-08-06 19:23:55 +0200 | <zim0369[m]> | i had 0.17.0 from cabal and then removed the binary and installed from git |
| 2022-08-06 19:24:07 +0200 | <zim0369[m]> | i didn't unregister it from ghc |
| 2022-08-06 19:24:41 +0200 | <Solid> | but xmonad works, no? |
| 2022-08-06 19:24:58 +0200 | <zim0369[m]> | yes xmonad works fine |
| 2022-08-06 19:25:03 +0200 | <zim0369[m]> | using 0.17.9 |
| 2022-08-06 20:00:41 +0200 | <zim0369[m]> | geekosaur: starting xmobar from xinitrc starts xmobar but doesn't execute anyfurther lines including xmonad |
| 2022-08-06 20:00:58 +0200 | <MrElendig> | post the xinitrc |
| 2022-08-06 20:01:08 +0200 | <geekosaur> | correct, you would have to run it in the background with & |
| 2022-08-06 20:02:02 +0200 | <zim0369[m]> | https://pastebin.com/SA0QjKAe |
| 2022-08-06 20:02:19 +0200 | <zim0369[m]> | oh yea |
| 2022-08-06 20:02:24 +0200 | <zim0369[m]> | forgot about that |
| 2022-08-06 20:05:57 +0200 | <zim0369[m]> | geekosaur: xmonad & |
| 2022-08-06 20:05:58 +0200 | <zim0369[m]> | doesn't work |
| 2022-08-06 20:06:00 +0200 | <zim0369[m]> | didn't* |
| 2022-08-06 20:07:14 +0200 | <MrElendig> | xmobar &\nexec xmonad |
| 2022-08-06 20:10:43 +0200 | <zim0369[m]> | umm |
| 2022-08-06 20:10:47 +0200 | <zim0369[m]> | didn't work |
| 2022-08-06 20:10:49 +0200 | zim0369 | (~zim0369@114.143.131.219) |
| 2022-08-06 20:10:50 +0200 | <zim0369[m]> | server crashes |
| 2022-08-06 20:10:58 +0200 | <zim0369> | MrElendig ill paste the error |
| 2022-08-06 20:11:27 +0200 | <zim0369> | https://pastebin.com/KkeZTdtQ |
| 2022-08-06 20:11:42 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 20:12:02 +0200 | <zim0369[m]> | oh the space |
| 2022-08-06 20:12:14 +0200 | zim0369 | (~zim0369@114.143.131.219) (Client Quit) |
| 2022-08-06 20:13:16 +0200 | <MrElendig> | zim0369[m]: \n == newline |
| 2022-08-06 20:13:39 +0200 | zim0369 | (~zim0369@114.143.131.219) |
| 2022-08-06 20:14:13 +0200 | <zim0369> | MrElendig https://pastebin.com/34j0AhRq |
| 2022-08-06 20:14:25 +0200 | <zim0369> | server again crashes |
| 2022-08-06 20:14:42 +0200 | <geekosaur> | you havent done the right thing |
| 2022-08-06 20:14:48 +0200 | zim0369 | (~zim0369@114.143.131.219) (Client Quit) |
| 2022-08-06 20:14:50 +0200 | <geekosaur> | there is ni literal n there |
| 2022-08-06 20:15:06 +0200 | <geekosaur> | the sequence "\n" that MrElendig typed represents a newline character |
| 2022-08-06 20:15:29 +0200 | zim0369 | (~zim0369@114.143.131.219) |
| 2022-08-06 20:16:36 +0200 | <geekosaur> | xmobar & |
| 2022-08-06 20:16:39 +0200 | <geekosaur> | exec xmonad |
| 2022-08-06 20:16:52 +0200 | <zim0369[m]> | server crashes with: |
| 2022-08-06 20:16:52 +0200 | <zim0369[m]> | `xmobar &\n exec xmonad` |
| 2022-08-06 20:16:52 +0200 | <zim0369[m]> | `xmobar &\nexec xmonad` |
| 2022-08-06 20:16:52 +0200 | <zim0369[m]> | `xmobar & xmonad` |
| 2022-08-06 20:17:08 +0200 | <zim0369[m]> | oh wait server starts with |
| 2022-08-06 20:17:16 +0200 | <zim0369[m]> | `xmobar & xmonad` |
| 2022-08-06 20:17:19 +0200 | <geekosaur> | the first two are completely wrong. the third should have worked |
| 2022-08-06 20:17:26 +0200 | <zim0369[m]> | but xmobar doesn't launch |
| 2022-08-06 20:22:45 +0200 | <zim0369[m]> | geekosaur: how big of a headache would it be to configure polybar for xmonad? |
| 2022-08-06 20:23:10 +0200 | <geekosaur> | I have no real idea |
| 2022-08-06 20:23:19 +0200 | <geekosaur> | I don't use either polybar or xmobar |
| 2022-08-06 20:23:33 +0200 | <zim0369[m]> | then what? |
| 2022-08-06 20:23:38 +0200 | <MrElendig> | was relatively easy when I used it before, using dbus for communication |
| 2022-08-06 20:23:48 +0200 | <MrElendig> | but that was a few years ago |
| 2022-08-06 20:24:01 +0200 | <geekosaur> | I run xmonad as the window manager for Mate, so I run mate-panel with xmonad-log-applet. this is not particularly easy to set up |
| 2022-08-06 20:24:51 +0200 | <zim0369[m]> | xmonad for mate? |
| 2022-08-06 20:24:58 +0200 | <zim0369[m]> | i didn't know you could do that |
| 2022-08-06 20:25:05 +0200 | <zim0369[m]> | i want something easy tho |
| 2022-08-06 20:25:10 +0200 | <zim0369[m]> | ill try polybar but |
| 2022-08-06 20:25:26 +0200 | <zim0369[m]> | there's no official documentation |
| 2022-08-06 20:25:35 +0200 | <zim0369[m]> | and youtube vids are a little old |
| 2022-08-06 20:25:45 +0200 | <zim0369[m]> | and all of their configs are different than mine |
| 2022-08-06 20:26:55 +0200 | <geekosaur> | https://wiki.haskell.org/Xmonad/Using_xmonad_in_MATE |
| 2022-08-06 20:27:25 +0200 | <geekosaur> | there are some instruction for various other desktop environments but I think they're all out of date. I keep the Mate instructions current |
| 2022-08-06 20:28:30 +0200 | <zim0369[m]> | geekosaur: is there a picture or a video of your setup? |
| 2022-08-06 20:30:53 +0200 | <geekosaur> | https://imgur.com/rexOYhY.png |
| 2022-08-06 20:32:05 +0200 | sogens | (~sogens@211.30.173.20) (Quit: WeeChat 3.5) |
| 2022-08-06 20:32:29 +0200 | <geekosaur> | the instructions for setting up mate intrgration are reasonably clear. the harder part is building and setting up xmonad-log-applet, which has to be custom built for whichever DE you use (it supports several) |
| 2022-08-06 20:33:01 +0200 | <zim0369[m]> | geekosaur: is there anything like xmonad on gnome |
| 2022-08-06 20:33:15 +0200 | <geekosaur> | only if gnome-flashback is supported on your system |
| 2022-08-06 20:33:36 +0200 | <zim0369[m]> | umm |
| 2022-08-06 20:33:38 +0200 | <geekosaur> | the window manager in gnome 3 can't be replaced, so gnome-flashback sets up an equivalent gnome 2 setup |
| 2022-08-06 20:33:42 +0200 | <zim0369[m]> | i don't like that setup |
| 2022-08-06 20:33:49 +0200 | <zim0369[m]> | xmonad and mate wouldn't be my thing |
| 2022-08-06 20:34:00 +0200 | <zim0369[m]> | my screen is really small |
| 2022-08-06 20:34:01 +0200 | <zim0369[m]> | 14in |
| 2022-08-06 20:34:05 +0200 | <MrElendig> | https://arch.har-ikkje.net/gfx/ss/2012-08-13-193731_2960x1050_scrot.png |
| 2022-08-06 20:34:07 +0200 | <zim0369[m]> | ill try polybar |
| 2022-08-06 20:35:14 +0200 | <zim0369> | MrElendig what bar are u using? |
| 2022-08-06 20:37:31 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection) |
| 2022-08-06 20:39:47 +0200 | <MrElendig> | xmobar in that case, but the image is from 2012 :p |
| 2022-08-06 20:40:20 +0200 | <zim0369[m]> | 🫥 |
| 2022-08-06 20:40:39 +0200 | <zim0369[m]> | ill bite the bullet |
| 2022-08-06 20:40:46 +0200 | <zim0369[m]> | starting to setup polybar |
| 2022-08-06 20:43:59 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-08-06 20:53:04 +0200 | zim0369 | (~zim0369@114.143.131.219) (Quit: Client closed) |
| 2022-08-06 20:54:20 +0200 | <zim0369[m]> | geekosaur: there's something wrong with my config |
| 2022-08-06 20:55:24 +0200 | <geekosaur> | what? |
| 2022-08-06 20:56:27 +0200 | <zim0369[m]> | xmobar starts fine with my old config |
| 2022-08-06 20:57:02 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 20:57:39 +0200 | zim0369 | (~zim0369@114.143.131.219) |
| 2022-08-06 20:59:09 +0200 | mc47 | (~mc47@xmonad/TheMC47) |
| 2022-08-06 20:59:09 +0200 | <zim0369[m]> | i suspect the decorations and the subtabbed layout |
| 2022-08-06 20:59:24 +0200 | <zim0369[m]> | does it have anything to do with that? |
| 2022-08-06 20:59:33 +0200 | zim0369 | (~zim0369@114.143.131.219) (Client Quit) |
| 2022-08-06 20:59:59 +0200 | <geekosaur> | it shouldn't unless you put the avoidStruts inside them when I said it has to be on the outside |
| 2022-08-06 21:01:55 +0200 | <zim0369[m]> | i put them on the outside |
| 2022-08-06 21:03:58 +0200 | <zim0369[m]> | https://paste.tomsmeding.com/GqFq3VmW |
| 2022-08-06 21:04:20 +0200 | <geekosaur> | that's correct |
| 2022-08-06 21:04:39 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection) |
| 2022-08-06 21:05:16 +0200 | mvk | (~mvk@2607:fea8:5ce3:8500::d5f2) |
| 2022-08-06 21:05:30 +0200 | <zim0369[m]> | btw my old layout doesn't have avoidstruts |
| 2022-08-06 21:05:31 +0200 | <zim0369[m]> | but xmobar still works |
| 2022-08-06 21:06:12 +0200 | <zim0369[m]> | do i have to put `bar = myBar` or something like that in my config? |
| 2022-08-06 21:06:17 +0200 | <zim0369[m]> | def* |
| 2022-08-06 21:06:20 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-08-06 21:07:08 +0200 | <geekosaur> | no |
| 2022-08-06 21:08:54 +0200 | <geekosaur> | line 74 of the last config I have from you (https://paste.tomsmeding.com/29D6HNKS) handles starting and tracking the bar; it just needs that avoidStruts to be complete |
| 2022-08-06 21:10:18 +0200 | <geekosaur> | it's nnot added for you because you may be doing special things with it (and you might in fact want to): see https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs#L142-L143 |
| 2022-08-06 21:11:27 +0200 | <geekosaur> | that setup means the bars are hidden on the Full workspace, but I can still toggle them on with mod-b |
| 2022-08-06 21:13:33 +0200 | sogens | (~sogens@211.30.173.20) (Quit: WeeChat 3.5) |
| 2022-08-06 21:13:55 +0200 | <zim0369[m]> | ill take a minute to comprehend |
| 2022-08-06 21:15:58 +0200 | <zim0369[m]> | still don't understand where i should look |
| 2022-08-06 21:16:00 +0200 | <geekosaur> | on the first line, I set the layout for the "windows" workspace to Full, but I also have `avoidStrutsOn []` which defaults bars to hidden but lets me toggle them on |
| 2022-08-06 21:16:16 +0200 | <geekosaur> | the second line then does a normal `avoidStruts` for all the other workspaces |
| 2022-08-06 21:16:33 +0200 | <geekosaur> | I still don't understand what the problem is |
| 2022-08-06 21:17:24 +0200 | <zim0369[m]> | https://pastebin.com/W5b59vR3 |
| 2022-08-06 21:17:35 +0200 | <zim0369[m]> | this is prolly all the stuff about xmobar in my old config |
| 2022-08-06 21:18:13 +0200 | <geekosaur> | that was the old style of config. it still works but is deprecated |
| 2022-08-06 21:20:24 +0200 | <geekosaur> | and I see you're back to using pastebin.com. I may stop helping you rather than put up with it |
| 2022-08-06 21:20:51 +0200 | <zim0369[m]> | https://paste.tomsmeding.com/YsUY3bfh |
| 2022-08-06 21:21:06 +0200 | <zim0369[m]> | sorry i forgot that i could be using your pastebin back again |
| 2022-08-06 21:21:54 +0200 | <geekosaur> | since I have to choose between unreadable strings and not having line numbers to refer to |
| 2022-08-06 21:22:32 +0200 | <geekosaur> | (I have visual problems, I really can't cope with the way pastebin.com syntax-colors strings) |
| 2022-08-06 21:22:45 +0200 | <zim0369[m]> | I'm sorry |
| 2022-08-06 21:23:08 +0200 | <zim0369[m]> | pastebin does look awful |
| 2022-08-06 21:26:34 +0200 | <geekosaur> | anyway I can go to /raw on pastebin but then I lose things like line numbers, which makes it harder to discuss various things |
| 2022-08-06 21:27:45 +0200 | <geekosaur> | anyway what exactly is wrong with your config? just that xmobar doesn't show up? |
| 2022-08-06 21:28:14 +0200 | <zim0369[m]> | yes |
| 2022-08-06 21:28:20 +0200 | <zim0369[m]> | everything else seems fine |
| 2022-08-06 21:28:38 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection) |
| 2022-08-06 21:28:54 +0200 | <geekosaur> | hm. I think we need Solid for that, since everything looks alright to me but I'm not an xmobar expert |
| 2022-08-06 21:29:19 +0200 | <geekosaur> | but Solid may be busy today, I noticed him poking in once or twice but not consistently |
| 2022-08-06 21:29:36 +0200 | <geekosaur> | (or juust got worse; getting over covid last I heard) |
| 2022-08-06 21:29:46 +0200 | <zim0369[m]> | umm.. okay |
| 2022-08-06 21:29:55 +0200 | <zim0369[m]> | ill wait until then |
| 2022-08-06 21:30:19 +0200 | <zim0369[m]> | I wonder how covid is still affecting people |
| 2022-08-06 21:30:25 +0200 | <zim0369[m]> | It's been more than 2yrs now |
| 2022-08-06 21:30:34 +0200 | <geekosaur> | it keeps changing |
| 2022-08-06 21:30:58 +0200 | <geekosaur> | the latest omicron variant isn't well handled by the existing vaccines and is starting to get nasty again |
| 2022-08-06 21:31:16 +0200 | <geekosaur> | after earlier omicron variants seemed to be on the way to becoming just another cold 😞 |
| 2022-08-06 21:32:02 +0200 | <zim0369[m]> | Covid is something I don't want to be troubled by |
| 2022-08-06 21:32:13 +0200 | <zim0369[m]> | but directly or indirectly people do get affected somehow |
| 2022-08-06 21:32:31 +0200 | <zim0369[m]> | i hope sooner or later there's a good outcome |
| 2022-08-06 21:32:42 +0200 | <geekosaur> | I've managed to avoid it so far but am fully vaccinated since I live among immune compromised folks and it'd just be bad to be an infection vector |
| 2022-08-06 21:32:43 +0200 | <zim0369[m]> | and people in power make better decisions everywhere |
| 2022-08-06 21:34:14 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-08-06 21:34:18 +0200 | <zim0369[m]> | ill sleep now |
| 2022-08-06 21:34:29 +0200 | <zim0369[m]> | ill try again tmrw |
| 2022-08-06 21:34:41 +0200 | <zim0369[m]> | night 🌃 |
| 2022-08-06 21:43:18 +0200 | <Solid> | geekosaur: didn't get worse, thankfully, just pretty busy this weekend |
| 2022-08-06 21:58:38 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 22:05:56 +0200 | sogens | (~sogens@211.30.173.20) (Quit: WeeChat 3.5) |
| 2022-08-06 22:15:15 +0200 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2022-08-06 22:17:49 +0200 | sogens | (~sogens@211.30.173.20) |
| 2022-08-06 22:22:56 +0200 | sogens | (~sogens@211.30.173.20) (Quit: WeeChat 3.5) |
| 2022-08-06 22:32:17 +0200 | diep | (~diep@2a01:cb11:2d7:4a00:a13f:e40c:c4e8:736c) |
| 2022-08-06 22:32:18 +0200 | diep | (~diep@2a01:cb11:2d7:4a00:a13f:e40c:c4e8:736c) (Remote host closed the connection) |
| 2022-08-06 22:58:45 +0200 | bla | (~bla@79.191.245.91.ipv4.supernova.orange.pl) (Ping timeout: 268 seconds) |
| 2022-08-06 22:59:10 +0200 | <ectospasm> | I'm getting an unexpected error compiling my xmonad.hs: https://git.eldon.me/trey/XMonad/src/branch/master/xmonad.hs, error: https://paste.rs/Tqe |
| 2022-08-06 22:59:52 +0200 | <ectospasm> | I'm running it on Arch Linux, with the Arch provided Haskell packages. I understand that might be part of my problem, but the "sc <- IS.countScreens" was working before. |
| 2022-08-06 23:01:39 +0200 | bla | (~bla@79.191.245.91.ipv4.supernova.orange.pl) |
| 2022-08-06 23:04:18 +0200 | <fizzie> | The error is claiming that line 137 of the file contains `sc <- countScreens`, not `sc <- IS.countScreens`. |
| 2022-08-06 23:04:41 +0200 | <fizzie> | (Well, the first of the two errors, anyway.) |
| 2022-08-06 23:05:30 +0200 | <[Leary]> | The second error looks to be one of do-block syntax. I'd start by indenting lines 295--308. |
| 2022-08-06 23:06:56 +0200 | <geekosaur> | did you happen to upgrade to ghc 9.2? GHC2021 is on by default and disables some formerly enabled simplifications to do indentation |
| 2022-08-06 23:07:30 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection) |
| 2022-08-06 23:08:32 +0200 | <geekosaur> | I think DoAndIfThenElse and NondecreasingIndentation got turned off by default in 9.2 |
| 2022-08-06 23:09:36 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-08-06 23:16:56 +0200 | <ectospasm> | my ghc --version reports 9.0.2, not 9.2 |
| 2022-08-06 23:18:36 +0200 | <ectospasm> | I'm actually trying to remove some default keybindings, when I ran into this error. Here's my current xmonad.hs: https://git.eldon.me/trey/XMonad/src/branch/remove-win+num/xmonad.hs. I fixed the sc <- countScreens error, but I'm still getting the other one. |
| 2022-08-06 23:21:20 +0200 | <[Leary]> | Looks like 306,7 still aren't indented enough. |
| 2022-08-06 23:23:59 +0200 | <geekosaur> | that error doesn't seem to follow from the code you linked, actually |
| 2022-08-06 23:24:50 +0200 | <ectospasm> | OK, I fixed the indentation, and it compiles now! |
| 2022-08-06 23:25:34 +0200 | <ectospasm> | geekosaur: sorry, I'm having to bounce between different tmux windows/panes, and it's getting hard to keep up with things. |
| 2022-08-06 23:59:50 +0200 | logzet | (~quassel@2001:9e8:e531:b700:dabb:c1ff:fed3:a1b9) (Ping timeout: 240 seconds) |
