Logs: liberachat/#xmonad
| 2022-07-12 15:01:51 | → | benin09 joins (~benin@183.82.29.162) |
| 2022-07-12 15:04:13 | × | benin0 quits (~benin@156.146.51.131) (Ping timeout: 272 seconds) |
| 2022-07-12 15:04:13 | benin09 | is now known as benin0 |
| 2022-07-12 15:20:57 | → | Guest50 joins (~Guest50@pd9ec2719.dip0.t-ipconnect.de) |
| 2022-07-12 15:34:53 | × | cfricke quits (~cfricke@user/cfricke) (Quit: WeeChat 3.5) |
| 2022-07-12 16:11:49 | × | Guest50 quits (~Guest50@pd9ec2719.dip0.t-ipconnect.de) (Quit: Client closed) |
| 2022-07-12 16:49:12 | <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 17:05:03 | × | benin0 quits (~benin@183.82.29.162) (Quit: The Lounge - https://thelounge.chat) |
| 2022-07-12 17:30:49 | → | abhixec joins (~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) |
| 2022-07-12 17:46:28 | × | abhixec quits (~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 260 seconds) |
| 2022-07-12 17:47:43 | → | abhixec joins (~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) |
| 2022-07-12 18:12:07 | <abhixec> | Hello! how do people handle sticky notes in xmonad? |
| 2022-07-12 18:12:20 | <abhixec> | is there an app or what workflow do people use? |
| 2022-07-12 18:12:28 | <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 18:12:31 | <ectospasm> | https://git.eldon.me/trey/XMonad/src/branch/master/xmonad.hs |
| 2022-07-12 18:13:13 | <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 18:13:21 | <geekosaur> | abhixec, I used to use leafpad with NamedScratchpads |
| 2022-07-12 18:13:56 | <geekosaur> | ectospasm, most of those should still be defined, just deprecated in favor of simply using `def` |
| 2022-07-12 18:14:21 | <ectospasm> | geekosaur: so replace each one it's complaining about with 'def'? |
| 2022-07-12 18:15:44 | <geekosaur> | I think so? it is for example hard to see how you'd have `dynamicLogWithPP` but not `defaultPP` otherwise |
| 2022-07-12 18:16:21 | <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 18:16:43 | <geekosaur> | (iirc we follow the three-release deprecation cycle) |
| 2022-07-12 18:17:57 | <abhixec> | geekosaur: I used use to? (do you use something else now? or you dont have that workflow requirement anymore :P ) |
| 2022-07-12 18:18:50 | <geekosaur> | hm, no, apparently we did remove them (or at least we removed `defaultGSConfig`, haven't checked the others yet) |
| 2022-07-12 18:19:27 | <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 18:19:46 | <geekosaur> | `defaultConfig` is also slated to be removed in favor of `def` at some point |
| 2022-07-12 18:20:19 | <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 18:21:17 | <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 18:26:55 | <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 18:27:27 | <geekosaur> | yes, probably including `defaultConfig`. you'll want to change those at some point |
| 2022-07-12 18:27:40 | <geekosaur> | not all of them change to `def` though |
| 2022-07-12 18:27:56 | <geekosaur> | the deprecation warnings should tell you what to change |
| 2022-07-12 18:30:04 | <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 18:31:19 | <geekosaur> | right, `docks` goes somewhere else |
| 2022-07-12 18:31:38 | <geekosaur> | instead of using all the separate hooks, you wrap your whole config in `docks` |
| 2022-07-12 18:31:57 | <geekosaur> | xmonad $ docks def { … } |
| 2022-07-12 18:32:44 | <ectospasm> | Looks like I'll be checking out a new branch of my xmonad.hs (-; |
| 2022-07-12 18:35:41 | <geekosaur> | I've got 5 🙂 |
| 2022-07-12 18:38:04 | <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 18:54:16 | × | Safeguard-IRC quits (~doctor-se@151.41.199.212) (Remote host closed the connection) |
| 2022-07-12 19:10:54 | <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 19:11:18 | <ectospasm> | Well, I did remove a keybinding, because I was never using it. |
| 2022-07-12 19:12:10 | <geekosaur> | if it was the toggle keybinding, I think we have a better way to do that as well now |
| 2022-07-12 19:12:28 | <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 19:20:12 | <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 19:20:37 | <ectospasm> | Or at least, which my brain maps better. |
| 2022-07-12 19:26:24 | → | wusticality joins (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) |
| 2022-07-12 19:27:53 | <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 19:27:53 | <wusticality> | xmonad side? None of my environment variables are getting picked up properly as a result. :) |
| 2022-07-12 19:29:22 | <geekosaur> | I wrap xmonad in a script that sources my .profile (you would presumably use .bash_profile) and .bashrc |
| 2022-07-12 19:29:43 | <geekosaur> | if you use a .xsession file then source them in that |
| 2022-07-12 19:31:33 | <wusticality> | It's not clear to me how xmonad gets launched when you login I guess |
| 2022-07-12 19:32:10 | <geekosaur> | how it gets launched depends on what display manager you're using and how the session is defined |
| 2022-07-12 19:32:58 | <wusticality> | looks like in /etc/passwd my default shell is bash as expected |
| 2022-07-12 19:33:08 | <wusticality> | i'm using x, not wayland atm |
| 2022-07-12 19:33:30 | <geekosaur> | right, that isn;t being used here |
| 2022-07-12 19:33:43 | <geekosaur> | what display manager are you running, and on what kind of system |
| 2022-07-12 19:33:47 | <geekosaur> | ? |
| 2022-07-12 19:34:06 | <wusticality> | I'm afraid my knowledge is limited here, but I'm on PopOS |
| 2022-07-12 19:34:16 | <wusticality> | As far as display manager, I'm not sure :/ |
| 2022-07-12 19:35:02 | <geekosaur> | is there anything in /usr/share/xsessions? |
| 2022-07-12 19:35:42 | <wusticality> | yeah, the various window managers I'm using - xmonad, awesome, gnome, etc. |
| 2022-07-12 19:35:59 | <geekosaur> | okay, so you want to look at xmonad.desktop |
| 2022-07-12 19:36:18 | <wusticality> | Exec=xmonad-session |
| 2022-07-12 19:36:19 | <wusticality> | Icon=xmonad.png |
| 2022-07-12 19:36:19 | <wusticality> | Type=XSession |
| 2022-07-12 19:36:50 | <wusticality> | apologies btw, I'm learning as I go here :) |
| 2022-07-12 19:36:59 | <geekosaur> | is there a /usr/share/applications/xmonad-session.desktop? |
| 2022-07-12 19:37:44 | <wusticality> | no, but there's a /usr/share/applications/xmonad.desktop |
| 2022-07-12 19:38:12 | <geekosaur> | okay, so there is probably a /usr/bin/xmonad-session script |
| 2022-07-12 19:38:31 | <geekosaur> | you'll have to look at that to see what can be done to configure the session |
| 2022-07-12 19:38:48 | <wusticality> | not that I see |
| 2022-07-12 19:39:06 | <wusticality> | I guess this is happening because I'm not using .profile eh |
| 2022-07-12 19:39:11 | <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 19:39:12 | <geekosaur> | no |
| 2022-07-12 19:39:18 | <geekosaur> | it won't read either of them |
| 2022-07-12 19:39:38 | <geekosaur> | only fedora bothers to read your startup files |
| 2022-07-12 19:39:54 | <wusticality> | so env vars are just ignored by default? |
| 2022-07-12 19:39:57 | <geekosaur> | yes |
| 2022-07-12 19:39:59 | <wusticality> | I guess it's shell-dependent though eh |
| 2022-07-12 19:40:14 | <geekosaur> | no, it doesn't read any shell's startup files |
| 2022-07-12 19:40:15 | <wusticality> | i guess the other (icky) option would be to launch everything wrapped in a bash shell or something |
| 2022-07-12 19:40:23 | <wusticality> | (for programs like dmenu) |
| 2022-07-12 19:40:35 | <geekosaur> | which is why I use a wrapper script around xmonad that reads mine |
| 2022-07-12 19:40:54 | <wusticality> | by wrapper script, do you mean a script that loads some stuff, and then launches xmonad? |
| 2022-07-12 19:41:02 | <wusticality> | or rather, xmonad-sesion |
| 2022-07-12 19:41:04 | <wusticality> | *session |
| 2022-07-12 19:41:07 | <geekosaur> | but I use xmonad as window manager for mate so I do that in mate's window manager configuration |
| 2022-07-12 19:41:11 | <geekosaur> | yes |
| 2022-07-12 19:41:34 | <geekosaur> | except we haven't found xmonad-session yet so it's not clear we can simply wrap that |
| 2022-07-12 19:41:43 | <geekosaur> | it might still be a desktop file somewhere |
| 2022-07-12 19:42:06 | <geekosaur> | xdg complicated things quite a bit with this desktop file stuff |
| 2022-07-12 19:42:25 | <wusticality> | er, /usr/share/xsessions/xmonad.desktop contains Exec=xmonad-session |
| 2022-07-12 19:42:57 | <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 19:43:00 | <geekosaur> | okay, so that probably is a program or script somewhere. the question becomes, where? |
| 2022-07-12 19:43:06 | <wusticality> | Need to improve my Linux-fu |
| 2022-07-12 19:43:22 | <geekosaur> | and the problem with that is it depends on the OS and how they chose to configure things |
| 2022-07-12 19:43:33 | <geekosaur> | it works differently on ubuntu, fedora, etc. |
| 2022-07-12 19:43:47 | <wusticality> | looks like /usr/bin/xmonad-session |
| 2022-07-12 19:43:56 | <geekosaur> | and arch just has you use a default session with a ~/.xsession file |
All times are in UTC.