Logs: liberachat/#xmonad
| 2021-06-02 15:34:31 | benin5 | is now known as benin |
| 2021-06-02 15:45:15 | → | benin1 joins (~benin@183.82.205.186) |
| 2021-06-02 15:47:00 | × | benin quits (benin@gateway/vpn/protonvpn/benin) (Ping timeout: 245 seconds) |
| 2021-06-02 15:47:01 | benin1 | is now known as benin |
| 2021-06-02 18:26:44 | → | tremon joins (~tremon@217-63-61-89.cable.dynamic.v4.ziggo.nl) |
| 2021-06-02 18:46:16 | × | wenzel quits (~wenzel@user/wenzel) (Read error: Connection reset by peer) |
| 2021-06-02 18:46:36 | → | wenzel joins (~wenzel@user/wenzel) |
| 2021-06-02 18:58:49 | × | wenzel quits (~wenzel@user/wenzel) (Quit: Leaving) |
| 2021-06-02 19:39:31 | → | Guest73 joins (~Guest73@124.40.244.150) |
| 2021-06-02 19:41:29 | <Guest73> | Is there a way to add description to key bindings? I am thinking of generating help automatically. |
| 2021-06-02 19:43:35 | <liskin> | Guest73: reminds me of https://old.reddit.com/r/xmonad/comments/nhu6uu/keybindings_generator/ |
| 2021-06-02 19:43:55 | <liskin> | also https://hackage.haskell.org/package/xmonad-contrib-0.16/docs/XMonad-Util-NamedActions.html |
| 2021-06-02 19:52:51 | <Guest73> | I liked this part: An additional step may be to have them displayed in a picture like those in the xmonad documentation |
| 2021-06-02 19:56:22 | <liskin> | we have an open issue that mentions something similar: https://github.com/xmonad/xmonad/issues/287 |
| 2021-06-02 19:56:51 | <liskin> | (and I can almost guarantee I will not work on this myself) |
| 2021-06-02 19:59:28 | × | Guest73 quits (~Guest73@124.40.244.150) (Ping timeout: 250 seconds) |
| 2021-06-02 20:00:19 | → | Guest73 joins (~Guest73@124.40.244.150) |
| 2021-06-02 20:03:20 | × | Guest73 quits (~Guest73@124.40.244.150) (Client Quit) |
| 2021-06-02 20:11:06 | → | benin0 joins (benin@gateway/vpn/protonvpn/benin) |
| 2021-06-02 20:13:30 | × | benin quits (~benin@183.82.205.186) (Ping timeout: 264 seconds) |
| 2021-06-02 20:13:31 | benin0 | is now known as benin |
| 2021-06-02 20:43:42 | → | lyiriyah[m] joins (~lyiriyahm@2001:470:69fc:105::cc0) |
| 2021-06-02 20:51:58 | <lyiriyah[m]> | Hi -- trying to figure out how to integrate IndependentScreens and PerWorkspace. IndependentScreens documentation doesn't really tell me anything. If anyone could should some insight that'd be great |
| 2021-06-02 20:52:54 | → | lyiriyah52 joins (~lyiriyah@host109-157-157-23.range109-157.btcentralplus.com) |
| 2021-06-02 20:53:02 | ← | lyiriyah52 parts (~lyiriyah@host109-157-157-23.range109-157.btcentralplus.com) () |
| 2021-06-02 20:54:05 | × | benin quits (benin@gateway/vpn/protonvpn/benin) (Ping timeout: 245 seconds) |
| 2021-06-02 21:01:58 | <lyiriyah[m]> | * Hi -- trying to figure out how to integrate IndependentScreens and PerWorkspace. IndependentScreens documentation doesn't really tell me anything. If anyone could share some insight that'd be great |
| 2021-06-02 21:15:23 | × | mc47 quits (~yecinem@89.246.239.190) (Remote host closed the connection) |
| 2021-06-02 21:19:59 | × | Guest7213 quits (~Guest7213@78.32.70.245) (Quit: Client closed) |
| 2021-06-02 21:26:50 | × | geekosaur quits (~geekosaur@069-135-003-034.biz.spectrum.com) (Remote host closed the connection) |
| 2021-06-02 21:27:00 | <liskin> | lyiriyah[m]: you can use https://hackage.haskell.org/package/xmonad-contrib-0.16/docs/XMonad-Layout-IndependentScreens.html#v:marshall to obtain a WorkspaceId to use in PerWorkspace |
| 2021-06-02 21:28:24 | <lyiriyah[m]> | <liskin "lyiriyah: you can use https://ha"> Ok, but what is ScreenId? |
| 2021-06-02 21:29:10 | → | geekosaur joins (~geekosaur@069-135-003-034.biz.spectrum.com) |
| 2021-06-02 21:29:18 | <liskin> | lyiriyah[m]: you can just use a number, 0 being the primary screen, 1 being the next (in whatever order xinerama reports it to xmonad) |
| 2021-06-02 21:29:27 | <lyiriyah[m]> | Oh I see |
| 2021-06-02 21:29:30 | <lyiriyah[m]> | Thanks |
| 2021-06-02 21:30:52 | <lyiriyah[m]> | How would I marshall more than one workspace? |
| 2021-06-02 21:34:49 | <liskin> | *Main XMonad.Layout.IndependentScreens> map (marshall 1) ["one", "two"] |
| 2021-06-02 21:34:51 | <liskin> | ["1_one","1_two"] |
| 2021-06-02 21:35:17 | <lyiriyah[m]> | Ah, thanks so much. I'll give it a go |
| 2021-06-02 21:41:17 | × | tremon quits (~tremon@217-63-61-89.cable.dynamic.v4.ziggo.nl) (Quit: getting boxed in) |
| 2021-06-02 21:50:24 | → | habib joins (~habib@89.38.69.198) |
| 2021-06-02 21:50:35 | × | habib quits (~habib@89.38.69.198) (Quit: habib) |
| 2021-06-02 22:09:36 | × | seschwar quits (~seschwar@user/seschwar) (Quit: :wq) |
| 2021-06-02 22:11:30 | <liskin> | geekosaur: what has to come from somewhere? |
| 2021-06-02 22:12:07 | <liskin> | (we can continue the discussion there, just didn't want to add unnecessary noise by asking for this clarification) |
| 2021-06-02 22:12:16 | <geekosaur> | GHC_ENVIRONMENT and friends |
| 2021-06-02 22:12:34 | <liskin> | that would come from the build of xmonad library itself |
| 2021-06-02 22:12:37 | <geekosaur> | you have to have somewhere to capture them from, so at least once have to build with cabal or stack |
| 2021-06-02 22:13:08 | <liskin> | I kind of assumed cabal/stack set them when invoking ghc to build |
| 2021-06-02 22:13:11 | <geekosaur> | oh. that's not certain to be the same as the one we need, though, especially if there are added deps |
| 2021-06-02 22:13:26 | <liskin> | yes, that is a very legitimate concern |
| 2021-06-02 22:14:37 | × | de-vri-es quits (~de-vri-es@voyager.de-vri.es) (Quit: Bathrobe!) |
| 2021-06-02 22:15:05 | → | de-vri-es joins (~de-vri-es@voyager.de-vri.es) |
| 2021-06-02 22:22:16 | <geekosaur> | come to think of it, when cabal or stack is building xmonad-contrib, it's doing so under /tmp |
| 2021-06-02 22:22:35 | <geekosaur> | so the environment you capture potentially won't include it or xmonad |
| 2021-06-02 22:23:30 | <liskin> | I thought it'd point somewhere in ~/.stack/snapshots or ./.stack-work/… |
| 2021-06-02 22:23:53 | <liskin> | anyway, I'm leaning towards not even trying this |
| 2021-06-02 22:24:22 | <geekosaur> | it may point under there but it's a PATH-like variable so it may point separately to a bunch of different package dirs |
| 2021-06-02 22:24:23 | <liskin> | if cabal --package-env ~/.xmonad/ works, then cabal is a non-issue |
| 2021-06-02 22:24:38 | <geekosaur> | only way to know is to try it and then hope they don''t change it |
| 2021-06-02 22:24:50 | <geekosaur> | oh, I know that works, it was the first thing I tried |
| 2021-06-02 22:25:05 | <geekosaur> | think I erased my setup afterward though |
| 2021-06-02 22:25:26 | <liskin> | and for stack I think a more explicit approach like configuring the stack.yaml path or detecting stack.yaml at known locations seems like a better approach |
| 2021-06-02 22:25:28 | <geekosaur> | yeh, it's gone now |
| 2021-06-02 22:25:37 | <liskin> | I'm a bit confused about --package-env though |
| 2021-06-02 22:25:45 | <liskin> | it sounds like such a perfect solutions |
| 2021-06-02 22:25:51 | <liskin> | why isn't it recommended everywhere? |
| 2021-06-02 22:26:30 | <geekosaur> | because most people work in terms of projects, not quasi-global installs |
| 2021-06-02 22:26:58 | <geekosaur> | --package-env is what replaces global installs with cabal; for stack it's the global environment that replaces it |
| 2021-06-02 22:27:22 | <liskin> | are you sure most people do that? |
| 2021-06-02 22:27:40 | <geekosaur> | reasonably certain, yes |
| 2021-06-02 22:27:43 | <liskin> | I thought most people just have a single xmonad.hs |
| 2021-06-02 22:28:18 | <geekosaur> | oh, I was talkingg in general. I have no idea what most xmonad users do at this point |
| 2021-06-02 22:28:21 | <liskin> | I mean, I consider myself an advanced xmonad "user" :-), and I had a single xmonad.hs until this year |
| 2021-06-02 22:28:28 | <geekosaur> | exceot get confused at ancient instructions :) |
| 2021-06-02 22:28:45 | <liskin> | oh |
| 2021-06-02 22:29:00 | <liskin> | I meant why isn't it recommended for installing xmonad |
| 2021-06-02 22:29:08 | <geekosaur> | actually I think most xmonad users install via system package manager and the really global env is still there |
| 2021-06-02 22:29:44 | <liskin> | is it just that we haven't updated our instructions since cabal went v2 and 3rd party guides are a mess in general? |
| 2021-06-02 22:30:26 | <liskin> | because if cabal install --package-env ~/.xmonad/ works just as well as the old v1 cabal install, then we should just recommend that |
| 2021-06-02 22:30:38 | <geekosaur> | pretty much |
| 2021-06-02 22:30:42 | <liskin> | oh, good point about package managers |
| 2021-06-02 22:31:07 | <liskin> | arch people can probably even get the git version via their package manager |
| 2021-06-02 22:31:26 | <liskin> | and as long as they manage to not run into dynamic linking breakage, they might live in blissful ignorance of cabal/stack |
| 2021-06-02 22:32:06 | <liskin> | come to think of it, I should probably be qualified enough to provide builds of git xmonad for ubuntu and debian |
| 2021-06-02 22:32:20 | <liskin> | brilliant, more things to put on my todo list :-D |
| 2021-06-02 22:34:08 | <geekosaur> | evidently they patch xmonad to include -dynamic in its build command |
| 2021-06-02 22:35:14 | × | wonko quits (~wjc@62.115.229.50) (Quit: See You Space Cowboy..) |
| 2021-06-02 22:36:54 | <liskin> | understandably |
| 2021-06-02 23:00:41 | → | benin0 joins (~benin@183.82.205.186) |
| 2021-06-02 23:00:54 | → | dmwit joins (~dmwit@pool-96-255-233-247.washdc.fios.verizon.net) |
| 2021-06-03 00:02:20 | × | geekosaur quits (~geekosaur@069-135-003-034.biz.spectrum.com) (Remote host closed the connection) |
| 2021-06-03 00:04:15 | → | geekosaur joins (~geekosaur@069-135-003-034.biz.spectrum.com) |
| 2021-06-03 00:05:57 | → | electr0n joins (~electr0n@hunt.revrse.sh) |
| 2021-06-03 00:59:44 | → | jg joins (~jrgiacone@47.149.222.98) |
| 2021-06-03 00:59:57 | <jg> | Hiya :) how was everyone's day? |
| 2021-06-03 01:01:24 | <geekosaur> | busier than I liked, because I inadvertently slept in over an hour |
| 2021-06-03 01:02:30 | liskin | was woken up at 10am by a Tesco delivery and then had to get more sleep in the afternoon :-) |
| 2021-06-03 01:03:09 | <liskin> | and now I'm digging deeper into the recompilation rabbit hole instead of going to bed early :-/ |
All times are in UTC.