Logs: liberachat/#xmonad
| 2022-10-17 08:25:08 | <dminuoso> | There's also i3 which you can customize quite arbitrarily as well |
| 2022-10-17 08:25:11 | <dminuoso> | If you can stand the pain of C. |
| 2022-10-17 08:25:41 | <Phaseditto> | The problem is that sway behaves like i3, and i haven't seen anyone being able to make the workspaces on multi monitors or at all behave like xmonad |
| 2022-10-17 08:26:13 | <dminuoso> | It took me a while to get used to the default behavior of xmonad on multi mopnitor |
| 2022-10-17 08:26:36 | <dminuoso> | But once I did, I began to embrace it - there's just so many right things with the way StackSet is used. |
| 2022-10-17 08:27:23 | <Phaseditto> | I prefer to have one set of workspaces accessible to every monitor. I have a set of workspaces, designated to functionality, 1 for instance is Production. When i want to access audacity and i know i have it open, i access 1, does not matter which monitor, it just works |
| 2022-10-17 08:27:42 | <dminuoso> | you can do that with xmonad too, and I used to use as well |
| 2022-10-17 08:28:10 | <dminuoso> | Mostly the pinning can also be solved by just a small bit of discipline |
| 2022-10-17 08:28:18 | <dminuoso> | My browser is always on 2, chat windows on 4 |
| 2022-10-17 08:28:22 | <dminuoso> | development stuff is on 1 |
| 2022-10-17 08:28:26 | <Phaseditto> | no this is the specific reason why i use xmonad to begin with :D |
| 2022-10-17 08:28:38 | <dminuoso> | well by "it with xmonad" I meant the deafult. |
| 2022-10-17 08:29:01 | <Phaseditto> | maybe i modified its behavior, don't remember |
| 2022-10-17 08:29:30 | <Phaseditto> | Though it's weird that this is not the default behavior or at least a setting on most WMs |
| 2022-10-17 08:29:38 | <Phaseditto> | in any case: https://paste.tomsmeding.com/Bqfms9oo |
| 2022-10-17 08:29:39 | <Phaseditto> | Did this ... work? |
| 2022-10-17 08:33:35 | <dminuoso> | Yes. |
| 2022-10-17 08:33:45 | <Phaseditto> | amazing |
| 2022-10-17 08:33:46 | <dminuoso> | What you saw is just a warning (as you can see in line 11 right next to the file + line) |
| 2022-10-17 08:33:57 | <dminuoso> | Where it says `warning:` |
| 2022-10-17 08:34:06 | <Phaseditto> | Yeah i would've guessed, i just expected more... resistance? |
| 2022-10-17 08:34:27 | <dminuoso> | Glad to have surprised you. :) |
| 2022-10-17 08:34:39 | <dminuoso> | A bit sad that it was that much of a hurdle, though |
| 2022-10-17 08:34:54 | <dminuoso> | Feel free to file a bug report on ghcup to not tell the user about `gmp-devel` on void |
| 2022-10-17 08:35:08 | <Phaseditto> | when i get around, sure :D |
| 2022-10-17 08:35:09 | <Phaseditto> | So all i need is to make a corresponding .desktop file and link / paste the binary? |
| 2022-10-17 08:35:17 | <dminuoso> | Nope |
| 2022-10-17 08:35:33 | <dminuoso> | So the build script already symlinks the artifact to the directory itself, that should be sufficient |
| 2022-10-17 08:35:46 | <dminuoso> | Just run `exec /path/to/your/xmonad//directory/xmonad` as your window manager now. |
| 2022-10-17 08:35:56 | <dminuoso> | Ah without the double slash of course. |
| 2022-10-17 08:36:01 | <Phaseditto> | does the rebuild go back to the build script in its own? |
| 2022-10-17 08:36:42 | <dminuoso> | Yes, so the way xmonad works is, it looks in your ~/.config/xmonad/ for whether an executable called `build` exists. |
| 2022-10-17 08:36:49 | <dminuoso> | And if it does, that is what it will use. |
| 2022-10-17 08:37:04 | <Phaseditto> | it's not currently located there, should i move it there? |
| 2022-10-17 08:37:09 | <dminuoso> | The directory, yes. |
| 2022-10-17 08:37:13 | <dminuoso> | Alternatively ~/.xmonad works too |
| 2022-10-17 08:37:38 | <Phaseditto> | so the whole build script and all in one of those corresponding directories and the rest is up to cabal? |
| 2022-10-17 08:38:30 | <Phaseditto> | In that case i will take a small break and try that in a bit |
| 2022-10-17 08:38:42 | <dminuoso> | I do not understand the question |
| 2022-10-17 08:39:04 | <dminuoso> | Basically there's just two bits you need: |
| 2022-10-17 08:40:13 | <dminuoso> | Ah the build script is incomplete by the way. |
| 2022-10-17 08:40:31 | <dminuoso> | Adapt it, so it symlinks to $1 |
| 2022-10-17 08:40:43 | <dminuoso> | First, ~/.xmonad/build or ~/.config/xmonad/build need to exist (for custom build scripts) |
| 2022-10-17 08:40:54 | <Phaseditto> | got it |
| 2022-10-17 08:41:11 | <dminuoso> | If a file there is found, it will be used to rebuild. The script will be passed the name of the resulting artifact, so `build` must place it at that path. |
| 2022-10-17 08:41:28 | <dminuoso> | (Whether or not that directory contains anything else, is almost entirely irrelevant) |
| 2022-10-17 08:41:30 | <dminuoso> | Second: |
| 2022-10-17 08:41:50 | <dminuoso> | You might want the build script to keep an *additional* symlink at a known path |
| 2022-10-17 08:42:07 | <Phaseditto> | hm okay |
| 2022-10-17 08:42:19 | <dminuoso> | Such that your X start script can `exec` directly into the existing binary, rather than relying on xmonad -- because that would try and `build` first (causing a delay) |
| 2022-10-17 08:42:39 | <dminuoso> | (In a custom build script, xmonad does not do any caching at the moment) |
| 2022-10-17 08:42:41 | <Phaseditto> | okay |
| 2022-10-17 08:43:30 | <Phaseditto> | i presume when i got the build script in ~/.xmonad/ or ~/.config/xmonad/ i need the corresponsing files around there aswell, such as the cabal file and xmonad.hs |
| 2022-10-17 08:43:43 | <dminuoso> | That doesnt really matter |
| 2022-10-17 08:43:49 | <dminuoso> | as long as the build script itself executes. |
| 2022-10-17 08:44:01 | <dminuoso> | so you can shuffle things around, but then adapt the build script to locate the proper directory |
| 2022-10-17 08:44:08 | <Phaseditto> | ah yeah |
| 2022-10-17 08:44:11 | <Phaseditto> | that was what i meant |
| 2022-10-17 08:44:15 | <dminuoso> | As soon as xmonad detects the build script, it really doesnt care about anything. it just calls that script |
| 2022-10-17 08:44:43 | <dminuoso> | Its then the scripts responsibility to produce an xmonad executable at the given argument |
| 2022-10-17 08:53:20 | <Phaseditto> | I will set everything up and test it out, that would be so cool if it would work |
| 2022-10-17 08:59:48 | → | wonko joins (~wjc@2a0e:1c80:2:0:45:15:19:130) |
| 2022-10-17 09:05:55 | → | andrejsh[m] joins (~andrejshm@2001:470:69fc:105::2:a171) |
| 2022-10-17 09:06:33 | <Phaseditto> | should i compile xmobar myself aswell or just take the xmobar-0.42_1 from xbps? |
| 2022-10-17 09:23:07 | <dminuoso> | Up to you, really. |
| 2022-10-17 09:23:15 | <dminuoso> | I would just use `cabal install` for this. |
| 2022-10-17 09:36:08 | × | Phaseditto quits (~Phaseditt@p200300f03f0a9400773b3c68de96c9f8.dip0.t-ipconnect.de) (Quit: Client closed) |
| 2022-10-17 09:37:31 | × | ft quits (~ft@p3e9bc57b.dip0.t-ipconnect.de) (Quit: leaving) |
| 2022-10-17 09:42:57 | → | Phaseditto joins (~Phaseditt@p200300f03f0a9400773b3c68de96c9f8.dip0.t-ipconnect.de) |
| 2022-10-17 09:51:31 | × | Phaseditto quits (~Phaseditt@p200300f03f0a9400773b3c68de96c9f8.dip0.t-ipconnect.de) (Quit: Client closed) |
| 2022-10-17 09:54:11 | → | Phaseditto joins (~Phaseditt@p200300f03f0a9400773b3c68de96c9f8.dip0.t-ipconnect.de) |
| 2022-10-17 09:55:19 | <Phaseditto> | almost done with it, though when i try to start it it immediately closes and the error log is non conclusive: |
| 2022-10-17 09:55:20 | <Phaseditto> | $ /home/user/.xmonad/build /home/user/.xmonad/xmonad-x86_64-linux |
| 2022-10-17 09:59:50 | <geekosaur> | if you're using cabal, drop 'exec 1>&2' near the top of the buildscript so cabal sends the error messages to the right place (sigh) |
| 2022-10-17 10:00:00 | <geekosaur> | or run "xmonad --recompile" in a terminal |
| 2022-10-17 10:01:34 | <Phaseditto> | it recompiles successfully |
| 2022-10-17 10:02:47 | <geekosaur> | also you usually can't start xmonad directly because another window manager will already be running so it'll get an error about "access to private resource denied" |
| 2022-10-17 10:03:25 | <geekosaur> | that or you are trying to run it from a text terminal and it'll fail to connect to an X server; it does not start the server itself |
| 2022-10-17 10:03:52 | <geekosaur> | if you're at a virtual console, try: startx /path/to/xmonad |
| 2022-10-17 10:04:23 | <geekosaur> | (you must specify the full path or it'll use the default window manager and pass "xmonad" as a parameter to it. startx is weird) |
| 2022-10-17 10:05:45 | <Phaseditto> | my tests were done through configuration in lightdm |
| 2022-10-17 10:05:58 | <Phaseditto> | just throws me back to the greeter |
| 2022-10-17 10:07:48 | <geekosaur> | 😞 |
| 2022-10-17 10:09:52 | <geekosaur> | is there anything in .xsession-errors? |
| 2022-10-17 10:12:24 | <Phaseditto> | lemme check |
| 2022-10-17 10:13:54 | <Phaseditto> | oh... |
| 2022-10-17 10:14:13 | <Phaseditto> | "Couldn't exec xmonad: No such file or directory" |
| 2022-10-17 10:14:39 | <geekosaur> | x11 via a greeter won't have the path your terminal does |
| 2022-10-17 10:14:55 | <Phaseditto> | i made a .desktop file for it |
| 2022-10-17 10:15:11 | <Phaseditto> | thought that would solve the problem |
| 2022-10-17 10:15:46 | <Phaseditto> | should probably enter the whole path in the exec section of said file |
| 2022-10-17 10:15:59 | <geekosaur> | you would still need a full pathname, or use a wrapper script that sets $PATH (I used a wrapper script that did "source ~/.profile" until I arranged for X11 to do so itself) |
| 2022-10-17 10:16:28 | <Phaseditto> | so either i have the corresponding binary in /usr/bin or i put the whole path |
| 2022-10-17 10:16:37 | <geekosaur> | yes |
| 2022-10-17 10:16:45 | <Phaseditto> | alright, will try that in a bit |
| 2022-10-17 10:19:15 | × | Phaseditto quits (~Phaseditt@p200300f03f0a9400773b3c68de96c9f8.dip0.t-ipconnect.de) (Quit: Client closed) |
| 2022-10-17 10:26:36 | → | Phaseditto joins (~Phaseditt@p200300f03f0a9400773b3c68de96c9f8.dip0.t-ipconnect.de) |
| 2022-10-17 10:26:44 | <Phaseditto> | Ladies and Gentlemen, it works |
| 2022-10-17 10:26:57 | <Phaseditto> | currently on xmonad on void |
| 2022-10-17 10:27:18 | <Phaseditto> | With my own config, xmobar and everything |
All times are in UTC.