IRCBrowse

2022/07/12

2022-07-12 00:21:44 +0200 <liskin> xkbcomp isn't really necessary, you can define your own xkb options and then use them in setxkbmap
2022-07-12 00:22:16 +0200 <liskin> although you'll be writing the same language xkbcomp accepts so probably not that much of a difference really :-)
2022-07-12 00:31:59 +0200 <wusticality> as long as it's data-driven ya know
2022-07-12 01:09:15 +0200 <wusticality> this is working, thanks so much folks <3
2022-07-12 01:09:21 +0200wusticality(~wusticali@c-67-161-204-49.hsd1.co.comcast.net) (Quit: Client closed)
2022-07-12 01:51:59 +0200mvk(~mvk@2607:fea8:5ce3:8500::909a)
2022-07-12 02:16:19 +0200Solitary(~Solitary@user/solitary) (Ping timeout: 256 seconds)
2022-07-12 02:27:20 +0200Solitary(~Solitary@user/solitary)
2022-07-12 02:41:33 +0200jaklt[m](~jaklttchn@2001:470:69fc:105::a42) (Quit: Client limit exceeded: 20000)
2022-07-12 02:41:33 +0200Solitary(~Solitary@user/solitary) (Ping timeout: 260 seconds)
2022-07-12 02:44:03 +0200liskin[m](~liskinmat@2001:470:69fc:105::768) (Quit: Client limit exceeded: 20000)
2022-07-12 02:56:21 +0200Solitary(~Solitary@user/solitary)
2022-07-12 02:57:52 +0200wusticality(~wusticali@c-67-161-204-49.hsd1.co.comcast.net)
2022-07-12 03:00:30 +0200Solitary(~Solitary@user/solitary) (Ping timeout: 240 seconds)
2022-07-12 03:03:18 +0200 <wusticality> Hey folks, I was taking that `spawnOnce "setxkbmap -option altwin:swap_alt_win"` approach to fixing my issues with swapping the windows / alt keys and it worked well (I used to use xmodmap). However, I seem to be running into the same issue where eventually, the keybindings are reversed. Any ideas would could be going wrong here? Here's the
2022-07-12 03:03:19 +0200 <wusticality> relevant part of my config: https://gist.github.com/wusticality/480a62377b988ca5066f576413c95371
2022-07-12 03:03:30 +0200 <wusticality> specifically, line 86
2022-07-12 03:03:36 +0200liskin[m](~liskinmat@2001:470:69fc:105::768)
2022-07-12 03:03:48 +0200jaklt[m](~jaklttchn@2001:470:69fc:105::a42)
2022-07-12 03:04:46 +0200Yehoshua(~yehoshua@2001:470:69fc:105::1:593f) (Quit: Client limit exceeded: 20000)
2022-07-12 03:13:18 +0200 <geekosaur> as I said earlier, look for a program starting some kind of settings daemon (`ps -fu$USER | grep setting` should work) and then use the corresponding (probably gnome or kde) keyboard configurator to make the same change
2022-07-12 03:13:19 +0200Yehoshua(~yehoshua@2001:470:69fc:105::1:593f)
2022-07-12 03:14:12 +0200 <geekosaur> unfortunately there may not otherwise be a lot to be done about it, especially since the program is apparently ignoring the Xkb settings on the root window that setxkbmap will have registered
2022-07-12 03:17:32 +0200 <wusticality> I got around it by changing every single program to use windows as alt, but unfortunatly it won't work properly for jetbrains stuff :(
2022-07-12 03:18:45 +0200pjaml[m](~pjamlmatr@2001:470:69fc:105::2:41c4)
2022-07-12 03:22:52 +0200 <geekosaur> ugly hack might be to change the spawnOnce to spawn and hit mod-q (I guess alt-q for you) when it happens, but ick
2022-07-12 03:27:57 +0200 <wusticality> Wish there was a way to override this in xmonad itself
2022-07-12 03:28:22 +0200Solitary(~Solitary@user/solitary)
2022-07-12 03:28:33 +0200 <geekosaur> sadly keybindings are not part of xmonad's purview
2022-07-12 03:28:52 +0200 <wusticality> does setxkbmap spawn a process, or just change some setting?
2022-07-12 03:28:53 +0200 <geekosaur> you might be interested in kmonad, although you'll probably have to fight the same problem anyway
2022-07-12 03:29:02 +0200 <wusticality> aka, do I need to kill it first before calling spawn
2022-07-12 03:29:03 +0200 <geekosaur> it just tweaks a server setting
2022-07-12 03:29:13 +0200tjmciver(~tjmciver@cpe-172-101-32-70.maine.res.rr.com)
2022-07-12 03:29:55 +0200 <tjmciver> Hi. Anyone running xmonad using nix/nixos? I'm having some trouble with it trying to upgrade nixos to 22.05. At least I think it's an xmonad issue.
2022-07-12 03:31:07 +0200 <geekosaur> (kmonad manages keyboards the same way xmonad manages windows)
2022-07-12 03:33:10 +0200 <wusticality> unrelated to xmonad?
2022-07-12 03:33:38 +0200 <geekosaur> unrelated aside from using a similar configuration style
2022-07-12 03:34:43 +0200 <geekosaur> there's a #kmonad channel although it's small compared to this one
2022-07-12 03:36:10 +0200Solitary(~Solitary@user/solitary) (Ping timeout: 240 seconds)
2022-07-12 03:41:52 +0200Solitary(~Solitary@user/solitary)
2022-07-12 03:52:52 +0200Hashstoned
2022-07-12 03:53:27 +0200steve__(~steve@ool-182c2b80.dyn.optonline.net)
2022-07-12 04:03:59 +0200banc(banc@gateway/vpn/airvpn/banc) (Ping timeout: 256 seconds)
2022-07-12 04:22:49 +0200banc(banc@gateway/vpn/airvpn/banc)
2022-07-12 04:28:54 +0200td_(~td@muedsl-82-207-238-180.citykom.de) (Ping timeout: 276 seconds)
2022-07-12 04:30:15 +0200td_(~td@94.134.91.223)
2022-07-12 04:43:57 +0200ectospasm(~ectospasm@user/ectospasm) (Quit: WeeChat 3.5)
2022-07-12 04:44:55 +0200ectospasm(~ectospasm@user/ectospasm)
2022-07-12 04:54:21 +0200qther(~qther@165.225.230.105)
2022-07-12 05:02:13 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 272 seconds)
2022-07-12 05:13:15 +0200wusticality(~wusticali@c-67-161-204-49.hsd1.co.comcast.net) (Quit: Client closed)
2022-07-12 05:29:52 +0200tjmciver_(~tjmciver@cpe-172-101-32-70.maine.res.rr.com)
2022-07-12 05:29:52 +0200tjmciver(~tjmciver@cpe-172-101-32-70.maine.res.rr.com) (Read error: Connection reset by peer)
2022-07-12 05:35:24 +0200qther(~qther@165.225.230.105) (Quit: Client closed)
2022-07-12 05:40:16 +0200mvk(~mvk@2607:fea8:5ce3:8500::909a) (Ping timeout: 244 seconds)
2022-07-12 08:23:43 +0200gauge_(~gauge@user/gauge)
2022-07-12 08:23:51 +0200haskl[error](~haskl@user/haskl)
2022-07-12 08:24:01 +0200gauge(~gauge@user/gauge) (Quit: Quitting)
2022-07-12 08:24:04 +0200haskl(~haskl@user/haskl) (Quit: Uh oh... ZNC disconnected.)
2022-07-12 08:33:51 +0200banc(banc@gateway/vpn/airvpn/banc) (Ping timeout: 244 seconds)
2022-07-12 08:45:40 +0200safeguard-irc(~doctor-se@151.41.199.212)
2022-07-12 08:48:55 +0200 <safeguard-irc> hello, i've been trying to put my config together, and I wanted to do something like this user does: https://github.com/ivanbrennan/nixbox/blob/d5b54fe2c0b672273f053c31eaaee17c4b1e65e9/services/xserv… which is basically embedd the xmobar config in the xmonad one. now, he uses the dynStatusBarStartup function, which is deprecated. what would be a good way to do this with the new XMonad.Hooks.StatusBar instead? I get that the xmobar
2022-07-12 08:48:55 +0200 <safeguard-irc> configuration is basically equal, but the type of xmobar should be something else. this is how I currently start up my xmobar: https://termbin.com/c9k6 (still under work, so pardon me if it's messy)
2022-07-12 08:51:01 +0200gauge_gauge
2022-07-12 09:05:42 +0200Guest50(~Guest50@pd9ec2719.dip0.t-ipconnect.de)
2022-07-12 09:14:53 +0200benin0(~benin@183.82.29.162)
2022-07-12 09:15:00 +0200 <Solid> safeguard-irc: at the end of the day, this config is translating everything into strings and giving it to xmobar via its command line options; this should be doable in exactly the same way with X.H.StatusBar ( https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Hooks-StatusBar.html#g:4 )
2022-07-12 09:16:25 +0200alternateved(~alternate@staticline-31-183-144-54.toya.net.pl)
2022-07-12 09:19:11 +0200 <Guest50> Hi, I've been using Xmonad for a while now but still consider myself somewhat of a noob both with Xmonad and Haskell.
2022-07-12 09:19:11 +0200 <Guest50> As I currently have no idea whatsoever how to debug my problems further i would greatly appreciate any hints or pointers. I'll try to explain the Problem now:
2022-07-12 09:19:12 +0200 <Guest50> Yesterday I took the plunge and updated my arch system which also meant an update of Xmonad from 0.15 to 0.17. After consulting the breaking changes and the documentation for the now recommended functions I've rewritten parts of my configuration file and was able to get Xmonad running again.
2022-07-12 09:19:12 +0200 <Guest50> However, I now face somewhat of a weird issue sometimes after I first log in to my system Xmobar spawns only on my first monitor and the second monitor is seemingly unresponsive. If I then mouse over to my second monitor and switch to a workspace with a window through my keybindings nothing happens on the second monitor, on my first monitor my
2022-07-12 09:19:13 +0200 <Guest50> xmobar changes to indicate that i have just switched the workspace on my second monitor. If I now move back to my first monitor and switch my layout to full-screen through a keybinding the second monitor refreshes once, I can then repeat these steps to get a single new frame from my second monitor.
2022-07-12 09:19:13 +0200 <Guest50> If I then reboot my machine and log in again, most of the time, it works without problems and both monitors are responsive.
2022-07-12 09:19:14 +0200 <Guest50> Sorry for the long-ish Post, if anyone has an idea what's going on or if I should post excerpts of my Xmonad/Xmobar config somewhere please let me know
2022-07-12 09:25:51 +0200chomwitt(~chomwitt@2a02:587:dc0d:4a00:cff7:1232:6084:40)
2022-07-12 09:36:27 +0200chomwitt(~chomwitt@2a02:587:dc0d:4a00:cff7:1232:6084:40) (Ping timeout: 272 seconds)
2022-07-12 09:38:21 +0200 <safeguard-irc> Solid yeah I got it, the problem is that since I use tray it does not seem that xmobar parses a position via the cmdline, and I don't think I can pass that via template; any idea on that?
2022-07-12 09:40:22 +0200cfricke(~cfricke@user/cfricke)
2022-07-12 09:44:32 +0200mc47(~mc47@xmonad/TheMC47)
2022-07-12 09:49:40 +0200 <Guest50> safeguard-irc do you mean how to add some whitespace, so that the bar content does not overlap with your tray? I found a script for that some time back: https://github.com/jaor/xmobar/issues/239#issuecomment-233206552
2022-07-12 09:49:41 +0200 <Guest50> And then in your xmobar config something like:
2022-07-12 09:49:41 +0200 <Guest50> > Run Com "sh"       [ "-c"         , "~/scripts/trayer-padding-icon.sh"] "trayerpad" 100`
2022-07-12 09:49:42 +0200 <Guest50> and
2022-07-12 09:49:42 +0200 <Guest50> > template = " [...] %trayerpad% [...]"
2022-07-12 09:49:44 +0200 <lambdabot> <hint>:1:89: error:
2022-07-12 09:49:44 +0200 <lambdabot> parse error (possibly incorrect indentation or mismatched brackets)
2022-07-12 09:49:45 +0200 <lambdabot> <hint>:1:10: error: parse error on input ‘=’
2022-07-12 09:50:48 +0200Jade1(~Jade1@ip-178-201-128-039.um46.pools.vodafone-ip.de)
2022-07-12 09:50:53 +0200 <Jade1> Can you use Xmonad with Wayland?
2022-07-12 09:51:56 +0200 <safeguard-irc> Guest50: I already use that script
2022-07-12 10:05:30 +0200 <safeguard-irc> actually scratch that, I have fixed xmobar, now I just need to and implement it inside xmonad
2022-07-12 10:20:37 +0200 <alternateved> Jade1 yes, you can
2022-07-12 10:20:56 +0200 <alternateved> Ah, scratch that. I've read xmobar not xmonad
2022-07-12 10:21:23 +0200neopenk[m](~neopenkma@2001:470:69fc:105::1:6286) (Quit: Client limit exceeded: 20000)
2022-07-12 10:21:46 +0200 <alternateved> Check this page: https://github.com/sponsors/xmonad
2022-07-12 10:22:03 +0200neopenk[m](~neopenkma@2001:470:69fc:105::1:6286)
2022-07-12 10:22:47 +0200 <alternateved> There you could read about Wayland, X11 and state of things
2022-07-12 10:23:14 +0200 <safeguard-irc> okay so I have a question: as of now I use two StatusBarConfig, XmobarInt and xmobarExt with each XMONAD_LOG_0 and 1. if I wanted to use only one binding, say xmobarAll, which takes an argument s, how can I append that to the XMONAD_LOG_STRING? I've tried something like xmobarSin :: ScreenId -> StatusBarConfig, and then doing statusBarPropTo ("_XMONAD_LOG_" ++ s) [..] but it keep giving me a type error
2022-07-12 10:23:15 +0200 <alternateved> Not sure how up to date this paragraph is
2022-07-12 10:24:08 +0200 <alternateved> You would need first to `show s` to turn it into the string, I think
2022-07-12 10:24:26 +0200 <safeguard-irc> ooh let me try, did not think about that
2022-07-12 10:24:35 +0200 <alternateved> Not sure if ScreenId has an instance of Show
2022-07-12 10:25:37 +0200 <alternateved> Yeah, it does
2022-07-12 10:26:27 +0200 <safeguard-irc> sso I need to use Show or show?
2022-07-12 10:26:40 +0200 <alternateved> show
2022-07-12 10:26:45 +0200 <safeguard-irc> okay
2022-07-12 10:27:48 +0200 <alternateved> Oh, I think it won't work
2022-07-12 10:28:14 +0200 <alternateved> It would return something like `S 1`
2022-07-12 10:28:19 +0200 <safeguard-irc> indeed it does not, xmonad_log does not respond (it's frozen)
2022-07-12 10:29:13 +0200 <safeguard-irc> oh wait now it works
2022-07-12 10:29:26 +0200 <safeguard-irc> I used this s@(S i) and then show i
2022-07-12 10:29:49 +0200 <alternateved> Oh, right, good call
2022-07-12 10:30:22 +0200 <safeguard-irc> though it does not seem to work for xmobar0
2022-07-12 10:31:52 +0200 <safeguard-irc> this is how I use the function: I have barSpawner' :: ScreenId -> IO StatusBarConfig, and I have two instances with barSpawner' 0 = pure $ xmobarSin 0 and the same but with 1
2022-07-12 10:32:21 +0200Jade1(~Jade1@ip-178-201-128-039.um46.pools.vodafone-ip.de) (Quit: Client closed)
2022-07-12 10:33:25 +0200 <alternateved> How it does not work?
2022-07-12 10:33:53 +0200 <safeguard-irc> xmobar0's workspaces are just stuck
2022-07-12 10:34:29 +0200 <safeguard-irc> maybe I need to restart xmonad as a whole? sometimes it can get funky with the unsafeXProplog
2022-07-12 10:34:30 +0200 <safeguard-irc> brb
2022-07-12 10:34:32 +0200safeguard-irc(~doctor-se@151.41.199.212) (Remote host closed the connection)
2022-07-12 10:36:23 +0200Safeguard-IRC(~doctor-se@151.41.199.212)
2022-07-12 10:36:53 +0200 <Safeguard-IRC> nope, xmobar1 works perfectly, xmobar0 does not. maybe the i variable does not start to count from 0? I find that odd tho
2022-07-12 10:39:36 +0200 <alternateved> Well, that wouldn't be hard to check
2022-07-12 10:42:49 +0200 <alternateved> It seems it starts from 0
2022-07-12 10:48:13 +0200 <Safeguard-IRC> hmm
2022-07-12 10:48:30 +0200 <Safeguard-IRC> let me try putting toghter the xmobar config with unsafestindreader insinde the xmonad config
2022-07-12 10:48:55 +0200 <Safeguard-IRC> actually scratch that, I'm gonna still use unsafeXproplog so I can see if it works
2022-07-12 11:30:41 +0200Jazzah(~jazz@user/jazzah) (Ping timeout: 244 seconds)
2022-07-12 11:35:29 +0200Jazzah(~jazz@stolen.plutonium.dk)
2022-07-12 11:35:29 +0200Jazzah(~jazz@stolen.plutonium.dk) (Changing host)
2022-07-12 11:35:29 +0200Jazzah(~jazz@user/jazzah)
2022-07-12 12:01:51 +0200dschrempf(~dominik@mobiledyn-62-240-134-33.mrsn.at)
2022-07-12 12:02:14 +0200dschrempf(~dominik@mobiledyn-62-240-134-33.mrsn.at) (Client Quit)
2022-07-12 12:28:26 +0200Lears(~Leary]@122-58-224-198-vdsl.sparkbb.co.nz) (Ping timeout: 255 seconds)
2022-07-12 12:46:41 +0200Guest50(~Guest50@pd9ec2719.dip0.t-ipconnect.de) (Quit: Client closed)
2022-07-12 13:09:27 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Killed (NickServ (GHOST command used by allbery_b)))
2022-07-12 13:09:28 +0200allbery_b(~geekosaur@xmonad/geekosaur)
2022-07-12 13:09:31 +0200allbery_bgeekosaur
2022-07-12 13:21:04 +0200banc(banc@gateway/vpn/airvpn/banc)
2022-07-12 13:23:14 +0200mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2022-07-12 13:38:30 +0200tjmciver_tjmciver
2022-07-12 13:45:39 +0200Guest50(~Guest50@pd9ec2719.dip0.t-ipconnect.de)
2022-07-12 14:02:21 +0200[Leary](~Leary]@122-58-224-198-vdsl.sparkbb.co.nz)
2022-07-12 14:06:15 +0200Guest50(~Guest50@pd9ec2719.dip0.t-ipconnect.de) (Quit: Client closed)
2022-07-12 14:47:00 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-07-12 16:51:10 +0200benin09(~benin@156.146.51.131)
2022-07-12 16:52:49 +0200benin0(~benin@183.82.29.162) (Ping timeout: 272 seconds)
2022-07-12 16:52:49 +0200benin09benin0
2022-07-12 16:55:12 +0200 <Safeguard-IRC> ok i've been trying to tackle that xmobar problem for a while now, but I simply don't know how to make it work correctly; any tip on that?
2022-07-12 17:01:51 +0200benin09(~benin@183.82.29.162)
2022-07-12 17:04:13 +0200benin0(~benin@156.146.51.131) (Ping timeout: 272 seconds)
2022-07-12 17:04:13 +0200benin09benin0
2022-07-12 17:20:57 +0200Guest50(~Guest50@pd9ec2719.dip0.t-ipconnect.de)
2022-07-12 17:34:53 +0200cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.5)
2022-07-12 18:11:49 +0200Guest50(~Guest50@pd9ec2719.dip0.t-ipconnect.de) (Quit: Client closed)
2022-07-12 18:49:12 +0200 <Safeguard-IRC> I did it! https://termbin.com/j2jq i'm very happy with the result. the only missing part is xmobar's border, but that is due it not having a cmdline option
2022-07-12 19:05:03 +0200benin0(~benin@183.82.29.162) (Quit: The Lounge - https://thelounge.chat)
2022-07-12 19:30:49 +0200abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net)
2022-07-12 19:46:28 +0200abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 260 seconds)
2022-07-12 19:47:43 +0200abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net)
2022-07-12 20:12:07 +0200 <abhixec> Hello! how do people handle sticky notes in xmonad?
2022-07-12 20:12:20 +0200 <abhixec> is there an app or what workflow do people use?
2022-07-12 20:12:28 +0200 <ectospasm> I've been running XMonad on Arch Linux for quite some time without any issues. Today, I upgraded quite a few Haskell packages, and now my xmonad.hs won't compile. A lot of default variables appear to now be undefined (defaultTheme, defaultPP, defaultXPConfig, etc.). Here's the full error output: https://paste.rs/PMv, and here's my xmonad.hs:
2022-07-12 20:12:31 +0200 <ectospasm> https://git.eldon.me/trey/XMonad/src/branch/master/xmonad.hs
2022-07-12 20:13:13 +0200 <ectospasm> It's like I need at least a few imports now, but I'm at a loss as what I need.
2022-07-12 20:13:21 +0200 <geekosaur> abhixec, I used to use leafpad with NamedScratchpads
2022-07-12 20:13:56 +0200 <geekosaur> ectospasm, most of those should still be defined, just deprecated in favor of simply using `def`
2022-07-12 20:14:21 +0200 <ectospasm> geekosaur: so replace each one it's complaining about with 'def'?
2022-07-12 20:15:44 +0200 <geekosaur> I think so? it is for example hard to see how you'd have `dynamicLogWithPP` but not `defaultPP` otherwise
2022-07-12 20:16:21 +0200 <geekosaur> I wonder if Arch simply removed the deprecated names for some reason; they should still be around since most of them haven't been deprecated for long enough to be removed
2022-07-12 20:16:43 +0200 <geekosaur> (iirc we follow the three-release deprecation cycle)
2022-07-12 20:17:57 +0200 <abhixec> geekosaur: I used use to? (do you use something else now? or you dont have that workflow requirement anymore :P )
2022-07-12 20:18:50 +0200 <geekosaur> hm, no, apparently we did remove them (or at least we removed `defaultGSConfig`, haven't checked the others yet)
2022-07-12 20:19:27 +0200 <geekosaur> you still need to specify something, but `def` is a polymorphic default instead of having a different default for every type
2022-07-12 20:19:46 +0200 <geekosaur> `defaultConfig` is also slated to be removed in favor of `def` at some point
2022-07-12 20:20:19 +0200 <geekosaur> (I… don't like this and we've already had one weird bug surface because of it. but everyone else thoinks it's a good idea despite that, sp.)
2022-07-12 20:21:17 +0200 <geekosaur> basically `def` is too polymorphic and leads to weird runtime issues if used in the wrong place, because you no longer get compile time errors
2022-07-12 20:26:55 +0200 <ectospasm> geekosaur: I replaced every variable it was complaining about with `def`, then I ran into other deprecation-related issues. A hint said to add '{-# OPTIONS_GHC -Wno-deprecations #-}', which has at least gotten me back into X.org.
2022-07-12 20:27:27 +0200 <geekosaur> yes, probably including `defaultConfig`. you'll want to change those at some point
2022-07-12 20:27:40 +0200 <geekosaur> not all of them change to `def` though
2022-07-12 20:27:56 +0200 <geekosaur> the deprecation warnings should tell you what to change
2022-07-12 20:30:04 +0200 <ectospasm> Unfortunately I don't know Haskell well enough to understand *how* to change what they suggest. The one that got me before I noticed the no deprecations hint was a suggestion to replace `docksEventHook` with `docks`, but that isn't enough because the type of the expression changes when I do that.
2022-07-12 20:31:19 +0200 <geekosaur> right, `docks` goes somewhere else
2022-07-12 20:31:38 +0200 <geekosaur> instead of using all the separate hooks, you wrap your whole config in `docks`
2022-07-12 20:31:57 +0200 <geekosaur> xmonad $ docks def { … }
2022-07-12 20:32:44 +0200 <ectospasm> Looks like I'll be checking out a new branch of my xmonad.hs (-;
2022-07-12 20:35:41 +0200 <geekosaur> I've got 5 🙂
2022-07-12 20:38:04 +0200 <geekosaur> we're generally changing to that combinator style instead of individual hooks, because people keep omitting hooks or putting them in the wrong place (some of them must come first or last in a chain of hooks)
2022-07-12 20:54:16 +0200Safeguard-IRC(~doctor-se@151.41.199.212) (Remote host closed the connection)
2022-07-12 21:10:54 +0200 <ectospasm> It was actually a lot easier to fix than I thought it would be, just remove `docksOldHook <+>` in each of those expressions and it worked. At least my xmonad.hs now compiles.
2022-07-12 21:11:18 +0200 <ectospasm> Well, I did remove a keybinding, because I was never using it.
2022-07-12 21:12:10 +0200 <geekosaur> if it was the toggle keybinding, I think we have a better way to do that as well now
2022-07-12 21:12:28 +0200 <ectospasm> it was using `windowPromptBring dXPConfig`, and the hint said to use `windowPrompt` instead. I couldn't figure out the proper way to fix it, so I removed it since I never used that key.
2022-07-12 21:20:12 +0200 <ectospasm> It looks like that just brought up a prompt where I could bring a named window to the front. I have some other things which do that better.
2022-07-12 21:20:37 +0200 <ectospasm> Or at least, which my brain maps better.
2022-07-12 21:26:24 +0200wusticality(~wusticali@c-67-161-204-49.hsd1.co.comcast.net)
2022-07-12 21:27:53 +0200 <wusticality> Hey folks, I open applications in xmonad via jr-dmenu-desktop (a dmenu clone). I'm running into an issue where ("M-p", spawn "j4-dmenu-desktop") doesn't pick up environment variables properly. I'm guessing this is because xmonad doesn't start from bash, and I don't use .profile, but instead .bash_profile. What's the correct way to fix this on the
2022-07-12 21:27:53 +0200 <wusticality> xmonad side? None of my environment variables are getting picked up properly as a result. :)
2022-07-12 21:29:22 +0200 <geekosaur> I wrap xmonad in a script that sources my .profile (you would presumably use .bash_profile) and .bashrc
2022-07-12 21:29:43 +0200 <geekosaur> if you use a .xsession file then source them in that
2022-07-12 21:31:33 +0200 <wusticality> It's not clear to me how xmonad gets launched when you login I guess
2022-07-12 21:32:10 +0200 <geekosaur> how it gets launched depends on what display manager you're using and how the session is defined
2022-07-12 21:32:58 +0200 <wusticality> looks like in /etc/passwd my default shell is bash as expected
2022-07-12 21:33:08 +0200 <wusticality> i'm using x, not wayland atm
2022-07-12 21:33:30 +0200 <geekosaur> right, that isn;t being used here
2022-07-12 21:33:43 +0200 <geekosaur> what display manager are you running, and on what kind of system
2022-07-12 21:33:47 +0200 <geekosaur> ?
2022-07-12 21:34:06 +0200 <wusticality> I'm afraid my knowledge is limited here, but I'm on PopOS
2022-07-12 21:34:16 +0200 <wusticality> As far as display manager, I'm not sure :/
2022-07-12 21:35:02 +0200 <geekosaur> is there anything in /usr/share/xsessions?
2022-07-12 21:35:42 +0200 <wusticality> yeah, the various window managers I'm using - xmonad, awesome, gnome, etc.
2022-07-12 21:35:59 +0200 <geekosaur> okay, so you want to look at xmonad.desktop
2022-07-12 21:36:18 +0200 <wusticality> Exec=xmonad-session
2022-07-12 21:36:19 +0200 <wusticality> Icon=xmonad.png
2022-07-12 21:36:19 +0200 <wusticality> Type=XSession
2022-07-12 21:36:50 +0200 <wusticality> apologies btw, I'm learning as I go here :)
2022-07-12 21:36:59 +0200 <geekosaur> is there a /usr/share/applications/xmonad-session.desktop?
2022-07-12 21:37:44 +0200 <wusticality> no, but there's a /usr/share/applications/xmonad.desktop
2022-07-12 21:38:12 +0200 <geekosaur> okay, so there is probably a /usr/bin/xmonad-session script
2022-07-12 21:38:31 +0200 <geekosaur> you'll have to look at that to see what can be done to configure the session
2022-07-12 21:38:48 +0200 <wusticality> not that I see
2022-07-12 21:39:06 +0200 <wusticality> I guess this is happening because I'm not using .profile eh
2022-07-12 21:39:11 +0200 <geekosaur> (whether the Exec line in a session desktop file points to an actual program or another desktop file seems to depend on the OS)
2022-07-12 21:39:12 +0200 <geekosaur> no
2022-07-12 21:39:18 +0200 <geekosaur> it won't read either of them
2022-07-12 21:39:38 +0200 <geekosaur> only fedora bothers to read your startup files
2022-07-12 21:39:54 +0200 <wusticality> so env vars are just ignored by default?
2022-07-12 21:39:57 +0200 <geekosaur> yes
2022-07-12 21:39:59 +0200 <wusticality> I guess it's shell-dependent though eh
2022-07-12 21:40:14 +0200 <geekosaur> no, it doesn't read any shell's startup files
2022-07-12 21:40:15 +0200 <wusticality> i guess the other (icky) option would be to launch everything wrapped in a bash shell or something
2022-07-12 21:40:23 +0200 <wusticality> (for programs like dmenu)
2022-07-12 21:40:35 +0200 <geekosaur> which is why I use a wrapper script around xmonad that reads mine
2022-07-12 21:40:54 +0200 <wusticality> by wrapper script, do you mean a script that loads some stuff, and then launches xmonad?
2022-07-12 21:41:02 +0200 <wusticality> or rather, xmonad-sesion
2022-07-12 21:41:04 +0200 <wusticality> *session
2022-07-12 21:41:07 +0200 <geekosaur> but I use xmonad as window manager for mate so I do that in mate's window manager configuration
2022-07-12 21:41:11 +0200 <geekosaur> yes
2022-07-12 21:41:34 +0200 <geekosaur> except we haven't found xmonad-session yet so it's not clear we can simply wrap that
2022-07-12 21:41:43 +0200 <geekosaur> it might still be a desktop file somewhere
2022-07-12 21:42:06 +0200 <geekosaur> xdg complicated things quite a bit with this desktop file stuff
2022-07-12 21:42:25 +0200 <wusticality> er, /usr/share/xsessions/xmonad.desktop contains Exec=xmonad-session
2022-07-12 21:42:57 +0200 <wusticality> I think the difficult thing for me is I just don't understand the relationship(s) between all these various paths / files
2022-07-12 21:43:00 +0200 <geekosaur> okay, so that probably is a program or script somewhere. the question becomes, where?
2022-07-12 21:43:06 +0200 <wusticality> Need to improve my Linux-fu
2022-07-12 21:43:22 +0200 <geekosaur> and the problem with that is it depends on the OS and how they chose to configure things
2022-07-12 21:43:33 +0200 <geekosaur> it works differently on ubuntu, fedora, etc.
2022-07-12 21:43:47 +0200 <wusticality> looks like /usr/bin/xmonad-session
2022-07-12 21:43:56 +0200 <geekosaur> and arch just has you use a default session with a ~/.xsession file
2022-07-12 21:44:09 +0200 <wusticality> #!/bin/bash
2022-07-12 21:44:10 +0200 <wusticality> if [ -r ".xmonad/xmonad-session-rc" ]
2022-07-12 21:44:10 +0200 <wusticality> then
2022-07-12 21:44:10 +0200 <geekosaur> that was what I suggested earlier and you said no?
2022-07-12 21:44:11 +0200 <wusticality>   . .xmonad/xmonad-session-rc
2022-07-12 21:44:11 +0200 <wusticality> fi
2022-07-12 21:44:12 +0200 <wusticality> exec xmonad "$@"
2022-07-12 21:44:22 +0200 <geekosaur> oh, that makes it easy then
2022-07-12 21:44:47 +0200 <wusticality> I guess I can just add ~/.xmonad/xmonad-session-rc ?
2022-07-12 21:44:49 +0200 <geekosaur> create that file, have it source your .bash_profile and .bashrc
2022-07-12 21:45:02 +0200 <wusticality> aight, let me try that quick
2022-07-12 21:45:36 +0200 <geekosaur> ("." is the old name for "source")
2022-07-12 21:47:09 +0200 <wusticality> hmm
2022-07-12 21:47:17 +0200chomwitt(~chomwitt@2a02:587:dc0d:4a00:ae09:5cbc:3a9a:5a89)
2022-07-12 21:47:23 +0200 <wusticality> outside of creating a file, is there some way to know that it's being loaded?
2022-07-12 21:48:10 +0200 <wusticality> I know Linux has logs or something
2022-07-12 21:48:32 +0200 <geekosaur> you could have it open an xmessage/zenity/whatever
2022-07-12 21:48:42 +0200 <geekosaur> I don't know where your session manager puts its logs
2022-07-12 21:50:11 +0200 <wusticality> added xmessage foobar, nothing happens
2022-07-12 21:50:15 +0200 <wusticality> I don't think it's being loaded, hmm
2022-07-12 21:50:57 +0200 <geekosaur> is xmessage installed? most modern systems don't any more
2022-07-12 21:51:19 +0200 <geekosaur> which is why I suggested zenity as well. zenity is the gtk alternative, kdialog is kde's version
2022-07-12 21:51:29 +0200 <wusticality> yep, I just tested it
2022-07-12 21:51:53 +0200 <wusticality> unless that script isn't loading ~/.xmonad/xmonad-session-rc, but some other .xmonad folder location perhaps?
2022-07-12 21:51:57 +0200 <wusticality> (which would be really weird)
2022-07-12 21:52:28 +0200 <geekosaur> I would be very surprised if that script started somewhere other than your home directory
2022-07-12 21:52:32 +0200 <wusticality> same
2022-07-12 21:52:41 +0200 <wusticality> doesn't appear to be loaded
2022-07-12 21:53:10 +0200 <wusticality> btw, I'm trying to pickup these changes by doing `modMask q`
2022-07-12 21:53:19 +0200 <geekosaur> that won't work
2022-07-12 21:53:19 +0200 <wusticality> would that completely relaunch xmonad?
2022-07-12 21:53:21 +0200 <wusticality> ahh
2022-07-12 21:53:34 +0200 <geekosaur> it restarts xmonad but won't rerun xmonad-session
2022-07-12 21:53:41 +0200 <geekosaur> you have to log out and back in
2022-07-12 21:53:44 +0200 <wusticality> ok, let me logout quick
2022-07-12 21:54:00 +0200 <wusticality> btw - if you source .bash_profile and it contains bash-specific things, what's going to happen exactly?
2022-07-12 21:54:15 +0200 <wusticality> in other words, under what shell will that source call occur?
2022-07-12 21:54:36 +0200 <geekosaur> the script starts with "#!/bin/bash" so it will use bash
2022-07-12 21:54:54 +0200 <geekosaur> and bash will do the source-ing
2022-07-12 21:55:07 +0200 <wusticality> ah
2022-07-12 21:55:17 +0200 <wusticality> if that's true, why wouldn't it pick up my bash_profile in the first place?
2022-07-12 21:55:26 +0200 <wusticality> apologies btw, learning a lot here as I go
2022-07-12 21:55:33 +0200 <geekosaur> because a script reads no startup files
2022-07-12 21:55:41 +0200 <wusticality> ahhh
2022-07-12 21:55:44 +0200 <geekosaur> an interactive shell runs startup files
2022-07-12 21:55:45 +0200 <wusticality> ok, let me logout quick
2022-07-12 21:55:52 +0200 <wusticality> got it :)
2022-07-12 21:56:00 +0200wusticality(~wusticali@c-67-161-204-49.hsd1.co.comcast.net) (Quit: Client closed)
2022-07-12 21:57:14 +0200wusticality(~wusticali@c-67-161-204-49.hsd1.co.comcast.net)
2022-07-12 21:57:26 +0200 <wusticality> btw, what do you use for irc in *nix?
2022-07-12 21:58:13 +0200 <geekosaur> I use hexchat, or element (matrix app, but matrix is linked to libera.chat irc) in my browser
2022-07-12 21:58:31 +0200 <wusticality> logging out / back in shows the message
2022-07-12 21:58:39 +0200 <wusticality> however, my env vars are still not showing up which is odd
2022-07-12 21:59:01 +0200 <wusticality> surely $HOME is defined at this point
2022-07-12 21:59:05 +0200 <wusticality> perhaps not?
2022-07-12 21:59:31 +0200 <wusticality> I'm doing something like this: [ -f "$HOME/.bash_profile" ] && . "$HOME/.bash_profile"
2022-07-12 21:59:44 +0200 <geekosaur> $HOME should always be defined, it's set by the login mechanism
2022-07-12 22:00:32 +0200 <wusticality> hmmm
2022-07-12 22:01:06 +0200wusticality(~wusticali@c-67-161-204-49.hsd1.co.comcast.net) (Client Quit)
2022-07-12 22:02:05 +0200wusticality(~wusticali@c-67-161-204-49.hsd1.co.comcast.net)
2022-07-12 22:02:23 +0200 <wusticality> heads up, every time I logout / login I'm losing the chat history, so apologies if I'm missing any comments
2022-07-12 22:02:44 +0200 <wusticality> I did an xmessage $HOME and it was correct
2022-07-12 22:04:04 +0200wusticality(~wusticali@c-67-161-204-49.hsd1.co.comcast.net) (Client Quit)
2022-07-12 22:10:01 +0200wusticality(~wusticali@c-67-161-204-49.hsd1.co.comcast.net)
2022-07-12 22:10:24 +0200 <geekosaur> https://ircbrowse.tomsmeding.com/browse/lcxmonad might be of interest, but I'm waiting while you're logged out
2022-07-12 22:10:24 +0200 <wusticality> So it seems like the file is getting sourced - could the issue be this?
2022-07-12 22:10:25 +0200 <wusticality> # Do nothing if not interactive.
2022-07-12 22:10:26 +0200 <wusticality> case $- in
2022-07-12 22:10:26 +0200 <wusticality>     *i*) ;;
2022-07-12 22:10:27 +0200 <wusticality>     *) return;;
2022-07-12 22:10:27 +0200 <wusticality> esac
2022-07-12 22:10:35 +0200 <geekosaur> yes
2022-07-12 22:10:52 +0200 <geekosaur> scripts aren't considered interactive, so it returns
2022-07-12 22:10:58 +0200 <wusticality> I guess that's saying, if it's not run as an actual shell, don't do anything?
2022-07-12 22:11:10 +0200 <wusticality> I'm trying to remember why I even did that
2022-07-12 22:11:19 +0200 <geekosaur> well, I'd quibble about "actual shell", but yes
2022-07-12 22:13:44 +0200 <geekosaur> I actually do something similar, but rather than abort the "source" entirely I skip the parts that I only want in interactive shells
2022-07-12 22:14:45 +0200 <wusticality> hu
2022-07-12 22:14:47 +0200 <wusticality> *huh
2022-07-12 22:15:08 +0200 <wusticality> Trying to think what you'd only want for interactive shells
2022-07-12 22:15:24 +0200 <MrElendig> wusticality: weechat in tmux
2022-07-12 22:19:58 +0200 <wusticality> What would you not run interactively?
2022-07-12 22:22:05 +0200 <geekosaur[m]> My dotfiles have a lot of Kerberos and OpenAFS setup intended for interactive shells, which needs to be different in scripts
2022-07-12 22:22:17 +0200allbery_b(~geekosaur@xmonad/geekosaur)
2022-07-12 22:22:17 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Killed (NickServ (GHOST command used by allbery_b)))
2022-07-12 22:22:20 +0200allbery_bgeekosaur
2022-07-12 22:22:27 +0200abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) (Quit: leaving)
2022-07-12 22:23:57 +0200gauge_(~gauge@user/gauge)
2022-07-12 22:24:08 +0200 <geekosaur[m]> You probably don't want to look at my dotfiles, they're scary 😀
2022-07-12 22:30:27 +0200Solitary_(~Solitary@user/solitary)
2022-07-12 22:31:16 +0200gauge(~gauge@user/gauge) (*.net *.split)
2022-07-12 22:31:16 +0200Solitary(~Solitary@user/solitary) (*.net *.split)
2022-07-12 22:31:16 +0200sagax(~sagax_nb@user/sagax) (*.net *.split)
2022-07-12 22:32:10 +0200Solitary_Solitary
2022-07-12 22:41:43 +0200 <wusticality> Should I potentially separate out parts of my bashrc into separate sections?
2022-07-12 22:41:55 +0200 <wusticality> I wonder if it's "safe (TM)" to just remove that "if interactive" check
2022-07-12 22:45:24 +0200wusticality(~wusticali@c-67-161-204-49.hsd1.co.comcast.net) (Quit: Client closed)
2022-07-12 22:46:43 +0200wusticality(~wusticali@c-67-161-204-49.hsd1.co.comcast.net)
2022-07-12 22:47:17 +0200 <geekosaur> possibly, but as I haven't seen it I wouldn't know (and in any case I'm not you and wouldn't know your preferences)
2022-07-12 22:47:47 +0200 <geekosaur> I have the $PATH stuff in mine separated out for when I want a minimal setup in other scripts
2022-07-12 22:48:04 +0200 <geekosaur> but then, my dotfiles are far from minimal
2022-07-12 22:49:15 +0200sagax(~sagax_nb@213.138.71.146)
2022-07-12 22:53:18 +0200 <wusticality> I think I'll disable it for now and give it some thought
2022-07-12 23:21:03 +0200chomwitt(~chomwitt@2a02:587:dc0d:4a00:ae09:5cbc:3a9a:5a89) (Ping timeout: 272 seconds)
2022-07-12 23:28:27 +0200 <liskin> wusticality: not sure if you solved your keyboard layout reversing issue, but I wanted to tell you two things yesterday after you left: if instead of spawnOnce you put it somewhere in /etc/default/keyboard or wherever your distro wants it, it won't revert
2022-07-12 23:28:53 +0200 <liskin> wusticality: and second thing, it's probably some udev event or something telling the X server to reload keyboard settings
2022-07-12 23:29:58 +0200 <liskin> my man 5 keyboard says that "udevadm trigger --subsystem-match=input --action=change" reloads keyboard config, so something like that's probably happening naturally
2022-07-12 23:30:07 +0200 <liskin> udevadm monitor to the rescue if you want to know what
2022-07-12 23:56:23 +0200sagax(~sagax_nb@213.138.71.146) (Read error: Connection reset by peer)
2022-07-12 23:59:10 +0200pok_(~pok@41.157.227.24)