| 2023-03-31 00:08:44 +0200 | hightower2 | (~hightower@89-164-77-23.dsl.iskon.hr) |
| 2023-03-31 01:00:12 +0200 | mncheck | (~mncheck@193.224.205.254) (Ping timeout: 255 seconds) |
| 2023-03-31 01:57:12 +0200 | stackdroid18 | (14094@de1.hashbang.sh) (Quit: hasta la vista... tchau!) |
| 2023-03-31 02:59:04 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2023-03-31 03:03:18 +0200 | Ou42 | (~Ou4242a@2600:1700:e930:41b0:e8a8:fce9:a862:3779) |
| 2023-03-31 03:04:24 +0200 | <Ou42> | Hello |
| 2023-03-31 03:04:33 +0200 | <Ou42> | I'm BaaaaAAAAAaaaaack! |
| 2023-03-31 03:05:47 +0200 | <Ou42> | I'm still going thru <https://xmonad.org/TUTORIAL.html> mostly. I do tend to skip things. ;o) I'm also taking "simple" suggestions from DistoTube's Intro to Xmonad video... |
| 2023-03-31 03:07:26 +0200 | <Ou42> | DT suggests compton, but "apt show ..." says it's depricated and to use picom |
| 2023-03-31 03:08:05 +0200 | <Ou42> | So I try that and get some stuff working ,but not quite the same as compton. Then I remark it out and M-q and some effects are still in effect, is this normal? |
| 2023-03-31 03:13:14 +0200 | <geekosaur> | I'm not supposed to still be up… |
| 2023-03-31 03:13:25 +0200 | <geekosaur> | mod-q won't affect a compositor at all |
| 2023-03-31 03:14:42 +0200 | <geekosaur> | the deprecation of compton came with the new ubuntu lts, you still use compton with 20.04 because picom isn't packaged |
| 2023-03-31 03:15:08 +0200 | <geekosaur> | so I presume that's a video from before 22.04 was released |
| 2023-03-31 03:15:40 +0200 | <Ou42> | geekosaur: it's only 12 hours difference |
| 2023-03-31 03:15:46 +0200 | <Ou42> | "only" |
| 2023-03-31 03:16:18 +0200 | <Ou42> | I'll try to ask my quick Q ( dunno if the answer will be quick ) |
| 2023-03-31 03:16:50 +0200 | <Ou42> | I'm on a laptop connected to a tv. sitting on couch... I'd like to turn off the laptop screen when the tv is plugged in, but use the laptop screen when not... |
| 2023-03-31 03:17:50 +0200 | <Ou42> | ( FWIW, the compton / picom issue seems to be a "find the right setup" thing and not as important ATM. ) |
| 2023-03-31 03:18:43 +0200 | <Ou42> | ( ... as I can't always tell what's working and what isn't, but so far these tweaks are compiling, so not an xmonad issue per se. ) |
| 2023-03-31 03:19:34 +0200 | <Ou42> | back to the issue: so the xmonad.org tutorial shows how to get xmobar installed and up. I got it, on the laptop screen. not on the tv. Also, trayer is installed, but I don't see it. |
| 2023-03-31 03:20:04 +0200 | <geekosaur> | controlling screens like that is best done with autorandr |
| 2023-03-31 03:20:12 +0200 | <Ou42> | ... but, again, I've been skipping somethings and I haven't (yet) implemented the section in the tutorial where xmonad can talk to xmobar. |
| 2023-03-31 03:21:57 +0200 | <geekosaur> | if you're starting trayer and it doesn't show, it may be covered by xmobar. see https://hackage.haskell.org/package/xmonad-contrib-0.17.1/docs/XMonad-Util-Hacks.html#g:3 |
| 2023-03-31 03:22:38 +0200 | <Ou42> | those 2 tips should be enough for now! tyvm! |
| 2023-03-31 03:22:58 +0200 | <Ou42> | I *used* to say, "sleep is for sissies" but it's not! sleep is important! |
| 2023-03-31 03:23:14 +0200 | <geekosaur> | at my age it's really important 🙂 |
| 2023-03-31 03:23:36 +0200 | <Ou42> | let the young-ones things otherwise and be wrong. |
| 2023-03-31 03:23:49 +0200 | <Ou42> | it's not that later for me to typo this badly. |
| 2023-03-31 03:23:53 +0200 | <Ou42> | ugh |
| 2023-03-31 04:14:58 +0200 | <Ou42> | I dunno about this Linux business... |
| 2023-03-31 04:15:20 +0200 | <Ou42> | spawnOnce "feh -bg-fill -no-fehbg ~/.wallpapers/comet.jpg" <= what's wrong w/ this?! Wait for it ... |
| 2023-03-31 04:15:55 +0200 | <Ou42> | the 2 args need to be preceded by 2 dashes! |
| 2023-03-31 04:16:14 +0200 | <Ou42> | so, this works! `spawnOnce "feh --bg-fill --no-fehbg ~/.wallpapers/comet.jpg"` |
| 2023-03-31 04:25:34 +0200 | jabuxas | (~jabuxas@user/jabuxas) (Ping timeout: 276 seconds) |
| 2023-03-31 04:26:42 +0200 | jabuxas | (~jabuxas@user/jabuxas) |
| 2023-03-31 04:27:27 +0200 | td_ | (~td@i53870922.versanet.de) (Ping timeout: 265 seconds) |
| 2023-03-31 04:29:07 +0200 | td_ | (~td@i5387092B.versanet.de) |
| 2023-03-31 04:36:30 +0200 | <Ou42> | Gotta go. I'll be back later. |
| 2023-03-31 04:36:40 +0200 | Ou42 | (~Ou4242a@2600:1700:e930:41b0:e8a8:fce9:a862:3779) (Quit: Leaving) |
| 2023-03-31 05:04:40 +0200 | srk | (~sorki@user/srk) (Ping timeout: 252 seconds) |
| 2023-03-31 05:11:45 +0200 | srk | (~sorki@user/srk) |
| 2023-03-31 08:12:04 +0200 | chomwitt | (~chomwitt@2a02:587:7a16:e500:1ac0:4dff:fedb:a3f1) |
| 2023-03-31 08:15:01 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 276 seconds) |
| 2023-03-31 08:31:27 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2023-03-31 08:34:35 +0200 | <xmonadtrack> | xmonad Tony Zorman * v0.17.1-52-gb394435: ci: Test against GHC 9.6.1 (48 minutes ago, 4 files, 25+ 35-) https://github.com/xmonad/xmonad/commit/b39443544365 |
| 2023-03-31 08:34:37 +0200 | <xmonadtrack> | xmonad Tony Zorman * v0.17.1-53-ga17fa0d: ci: Bump 9.2 and 9.4 minor versions (46 minutes ago, 1 file, 4+ 4-) https://github.com/xmonad/xmonad/commit/a17fa0d28bd2 |
| 2023-03-31 08:34:44 +0200 | <xmonadtrack> | xmonad Tony Zorman * v0.17.1-54-g1364ee4: stack: Bump resolver to lts-20.16 (45 minutes ago, 1 file, 1+ 1-) https://github.com/xmonad/xmonad/commit/1364ee4b1f24 |
| 2023-03-31 08:34:52 +0200 | <xmonadtrack> | xmonad-contrib Tony Zorman * v0.17.1-145-g1d84db95: ci: Bump 9.2 and 9.4 minor versions (22 hours ago, 2 files, 5+ 5-) https://github.com/xmonad/xmonad-contrib/commit/1d84db959ca8 |
| 2023-03-31 08:34:59 +0200 | <xmonadtrack> | xmonad-contrib Tony Zorman * v0.17.1-146-g815a595b: stack: Bump resolver to lts-20.16 (22 hours ago, 1 file, 1+ 1-) https://github.com/xmonad/xmonad-contrib/commit/815a595b46fe |
| 2023-03-31 08:35:17 +0200 | <Solid> | (I was thinking of opening PRs for these, but since it's just routine bumps, I decided against it; feel free to yell at me for that :) |
| 2023-03-31 08:44:53 +0200 | mncheck | (~mncheck@193.224.205.254) |
| 2023-03-31 09:02:13 +0200 | mncheck | (~mncheck@193.224.205.254) (Read error: Connection reset by peer) |
| 2023-03-31 09:20:33 +0200 | mncheckm | (~mncheck@193.224.205.254) |
| 2023-03-31 10:03:24 +0200 | <geekosaur> | don't see a reason to use PRs in that case |
| 2023-03-31 10:05:19 +0200 | ft | (~ft@p4fc2a88b.dip0.t-ipconnect.de) (Quit: leaving) |
| 2023-03-31 11:00:13 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2023-03-31 11:02:04 +0200 | hightower2 | (~hightower@89-164-77-23.dsl.iskon.hr) (Ping timeout: 276 seconds) |
| 2023-03-31 11:47:52 +0200 | chomwitt | (~chomwitt@2a02:587:7a16:e500:1ac0:4dff:fedb:a3f1) (Ping timeout: 252 seconds) |
| 2023-03-31 12:25:10 +0200 | Ou42 | (~Ou4242a@2600:1700:e930:41b0:27e2:d5f9:7e0c:462b) |
| 2023-03-31 12:25:29 +0200 | <Ou42> | geekosaur: R U up yet? |
| 2023-03-31 12:25:43 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) |
| 2023-03-31 12:25:52 +0200 | <geekosaur> | yes |
| 2023-03-31 12:26:15 +0200 | <Ou42> | Cool. Here's an update ( from memory w/ a ton of stuff forgotten along the way ) |
| 2023-03-31 12:26:35 +0200 | chomwitt | (~chomwitt@2a02:587:7a16:e500:1ac0:4dff:fedb:a3f1) |
| 2023-03-31 12:26:48 +0200 | <Ou42> | . I compiled Xmobar from source. Took a LONG time. went from v 36 to v 46 |
| 2023-03-31 12:26:56 +0200 | <geekosaur> | I take notes for that kind of thing 🙂 |
| 2023-03-31 12:27:03 +0200 | <geekosaur> | betting that broke |
| 2023-03-31 12:27:13 +0200 | <geekosaur> | xmobar had a major update that changed how fonts work |
| 2023-03-31 12:27:43 +0200 | <Ou42> | dunno what I gained from it ( yet ), yeah, growing pains. but the reason for the jump was the DPI setting, which, works backwards on my setup |
| 2023-03-31 12:29:12 +0200 | <Ou42> | I've never gorked DPI other than "dots per inch" ... so, basically, a 1080p HDTV has a DPI of 40 ( learned that tonight -- there are calculators online! but got the measuring tape and it was pretty close! ), but, it's 10 feet away ... |
| 2023-03-31 12:29:41 +0200 | <Ou42> | so say i hold out the measuring tape and measure the percieved length of my tv? |
| 2023-03-31 12:29:57 +0200 | <Ou42> | I haven't done this, but I figure it's as if it's a hidpi monitor. |
| 2023-03-31 12:31:05 +0200 | <Ou42> | anyway, moving on. still can't figure out how to get xmobar on 2 screens, but found a setting... broadest(sp?) |
| 2023-03-31 12:31:37 +0200 | <geekosaur> | you have to run a separate xmobar for each screen, each with an option telling it which screen to run on (-x 0, -x 1, etc.) |
| 2023-03-31 12:31:53 +0200 | <Ou42> | so it's on the tv's screen and the page I found that pointed me to the fg/bg colors also mentioned font sizes, but very confusing, but linked to their source and that made sense! |
| 2023-03-31 12:32:07 +0200 | <geekosaur> | it's not one of the desktop environment panels that can instantiate for multiple screens or in multiple locations |
| 2023-03-31 12:32:29 +0200 | <Ou42> | I tried the -x 0 and -x 1 but it seriously broke things so I reverted. |
| 2023-03-31 12:32:51 +0200 | <geekosaur> | "broke things"? |
| 2023-03-31 12:33:03 +0200 | <Ou42> | instructions online usually predate the ewmh(sp?) change, which I think borks everything |
| 2023-03-31 12:34:06 +0200 | <Ou42> | I'm an idiot and should have taken a picture of it. in my tabbed layout it opened xmobar as 3 tabs |
| 2023-03-31 12:34:46 +0200 | <Ou42> | but then another tweak just didn't show anything. hotkeys didn't work. apps didn't show. not even term |
| 2023-03-31 12:34:52 +0200 | <geekosaur> | that sounds like either you don't have ManageDocks set up right or it's not setting struts any more |
| 2023-03-31 12:34:57 +0200 | <Ou42> | lots of artifcacting on the bottom 1/3rd |
| 2023-03-31 12:35:50 +0200 | <Ou42> | back to the idiot part, I was using "apt show" to check what ver installed apps were. Well, "show" doesn't prove they are in fact installed. |
| 2023-03-31 12:38:11 +0200 | <Ou42> | spent a whle getting xmessage to use a bigger font, but did this in cinnamon, switched to xmonad and it didn't use the scaled font! what gives? |
| 2023-03-31 12:38:27 +0200 | <Ou42> | IOW, your script replacing xmessage is probably the way I should go. |
| 2023-03-31 12:39:19 +0200 | <Ou42> | to add insult to injury, if I run the same test, calling, `xmessage "hello, world" &`it works w/ the scaled font! |
| 2023-03-31 12:40:48 +0200 | <Ou42> | there's more but mem is fading. I got trayer to show, found a thread from 2015? that said it might be due to the "virtual desktop" and the "top" of one monitor being "above the other" |
| 2023-03-31 12:41:00 +0200 | <Ou42> | not sure about that, but moved trayer to the bottom and it showed |
| 2023-03-31 12:43:13 +0200 | <Ou42> | <https://askubuntu.com/questions/10005/getting-trayer-to-work-with-dual-screen-setup> |
| 2023-03-31 12:43:23 +0200 | <geekosaur> | most desktop environments store things like that in their own private areas (somewhere in dconf, usually) so it's not surprising that a change made in cinnamon doesn't affect other environments |
| 2023-03-31 12:43:48 +0200 | <Ou42> | the xmessage font size thing? |
| 2023-03-31 12:43:51 +0200 | <geekosaur> | also (old) trayer doesn't support multiscreen, you need at least trayer-srg |
| 2023-03-31 12:43:54 +0200 | <geekosaur> | yes |
| 2023-03-31 12:44:58 +0200 | <Ou42> | trayer-srg gotcha. the other "tut" suggested stalonetray, but I fgure stick w/ the xmonad.org tut, unless you suggest otherwise |
| 2023-03-31 12:45:22 +0200 | <geekosaur> | actually it looks like debian-based distros have trayer as trayer-srg |
| 2023-03-31 12:45:46 +0200 | <geekosaur> | (see `apt show trayer`, note the homepage) |
| 2023-03-31 12:46:09 +0200 | <Ou42> | one sec |
| 2023-03-31 12:46:35 +0200 | <Ou42> | I really don't grok the workspace switching yet. sometimes it works and other times it flips to the other screen |
| 2023-03-31 12:47:24 +0200 | <geekosaur> | yes, if the workspace you select is on the other screen then by default it swaps what workspace is on what screen so the primary monitor is always focused |
| 2023-03-31 12:48:01 +0200 | <Ou42> | I grok your words, but need time to let it sink in |
| 2023-03-31 12:48:12 +0200 | <Ou42> | xmobar says [1] (2) 3 |
| 2023-03-31 12:48:20 +0200 | <Ou42> | sometimes the [ ] and ( ) swap |
| 2023-03-31 12:48:21 +0200 | <geekosaur> | https://wiki.haskell.org/Xmonad/Frequently_asked_questions#Replacing_greedyView_with_view |
| 2023-03-31 12:48:35 +0200 | <Ou42> | Homepage: https://github.com/sargon/trayer-srg |
| 2023-03-31 12:49:29 +0200 | <geekosaur> | right, this can be confusing because debian-derived systems call it trayer but it's actually trayer-srg |
| 2023-03-31 12:49:46 +0200 | <geekosaur> | which has somewhat different options |
| 2023-03-31 12:50:09 +0200 | <Ou42> | back to xmessage... the way I set it was in .Xresources. I spawnOnce that file. I don't reference anything when calling xmessage from the terminal and it picks up my font setting. I could change .Xresources and then M-q and see if it changes in M-S-fwd-slash |
| 2023-03-31 12:50:29 +0200 | <geekosaur> | anyway you want to look at that "replacing…" link if you want workspaces to work properly |
| 2023-03-31 12:51:07 +0200 | <geekosaur> | you can't spawnOnce that file directly, you spawnOnce `xrdb -merge ~/.Xresources` |
| 2023-03-31 12:51:19 +0200 | <Ou42> | that's what I have. |
| 2023-03-31 12:51:21 +0200 | <geekosaur> | although if you're on a debian it should be done for you automatically |
| 2023-03-31 12:51:39 +0200 | <Ou42> | actually, hold on, I might ave a "&" at the end |
| 2023-03-31 12:51:48 +0200 | <geekosaur> | ("cinnamon" makes me think you're on mint, which is derived from ubuntu, which is derived from debian testing) |
| 2023-03-31 12:52:38 +0200 | <Ou42> | yes |
| 2023-03-31 12:53:36 +0200 | <Ou42> | the .Xresources fg/bg fix worked, but the font change only works when calling xmessage directly.... does xmoand call xmessage by an alias? |
| 2023-03-31 12:54:33 +0200 | <Ou42> | xmobar lists it as "xmessage" |
| 2023-03-31 12:55:02 +0200 | <geekosaur> | no, it calls it directly. it may pass a font though |
| 2023-03-31 12:55:47 +0200 | <Ou42> | OK, then I will wind down with this... in the tut, I'm lost why the change from the first iteration of xmobar integration ... |
| 2023-03-31 12:55:54 +0200 | <geekosaur> | https://github.com/xmonad/xmonad/blob/master/src/XMonad/Core.hs#L463 we indeed set the font |
| 2023-03-31 12:56:55 +0200 | <Ou42> | that was gonna be my other Q, but forgot... I know of hoogle and was able to find some info, but how do you find the source so fast? |
| 2023-03-31 12:57:07 +0200 | <Ou42> | tips tricks appreciated |
| 2023-03-31 12:58:06 +0200 | <geekosaur> | I've been working with xmonad for 15+ years and know the source pretty well 🙂 no helpful tricks in there though |
| 2023-03-31 12:59:24 +0200 | <Ou42> | I think I'm up to 15 hours |
| 2023-03-31 12:59:28 +0200 | <Ou42> | that's a stretch |
| 2023-03-31 12:59:57 +0200 | <Ou42> | I learned (|||) is Arrow fan-in |
| 2023-03-31 13:00:08 +0200 | <Ou42> | I feel like a kid here |
| 2023-03-31 13:00:14 +0200 | <Ou42> | you guys got some serious candy |
| 2023-03-31 13:00:40 +0200 | <Ou42> | if I can just get FF to stop flipping to the other screen... |
| 2023-03-31 13:01:59 +0200 | <geekosaur> | our ||| is not the Arrow one |
| 2023-03-31 13:02:05 +0200 | <Ou42> | OK, reading the workspaces wrong |
| 2023-03-31 13:02:10 +0200 | <geekosaur> | it's a smart list separator that remembers its state |
| 2023-03-31 13:02:28 +0200 | <Ou42> | aww c'mon! I thought I was making progress w/ the learning. :face-palm: |
| 2023-03-31 13:02:36 +0200 | <geekosaur> | as for flipping screens you probably want to look at that link I sent earlier |
| 2023-03-31 13:02:48 +0200 | <geekosaur> | https://wiki.haskell.org/Xmonad/Frequently_asked_questions#Replacing_greedyView_with_view |
| 2023-03-31 13:02:49 +0200 | <Ou42> | working on it |
| 2023-03-31 13:02:51 +0200 | <Ou42> | thanks |
| 2023-03-31 13:03:27 +0200 | <Ou42> | I'm just not adept enough yet. best to use tabbed layout and the mouse for this back and forth |
| 2023-03-31 13:03:36 +0200 | <geekosaur> | https://github.com/xmonad/xmonad/blob/master/src/XMonad/Layout.hs#L176-L182 re (|||) |
| 2023-03-31 13:04:17 +0200 | <Ou42> | are you going directly to the source page? and/or is there a way to get to that link from say, hoogle? |
| 2023-03-31 13:04:25 +0200 | <Ou42> | "view source"? |
| 2023-03-31 13:04:38 +0200 | <geekosaur> | yes |
| 2023-03-31 13:04:42 +0200 | <Ou42> | oh oh oh and the log for this channel... is it searchable? |
| 2023-03-31 13:05:02 +0200 | <geekosaur> | but I'm going directly, as a developer I have the github sources open at all times |
| 2023-03-31 13:05:12 +0200 | <geekosaur> | we have a log but search functionality is disabled 😞 |
| 2023-03-31 13:05:28 +0200 | <Ou42> | even via duckduckgo? or archive? |
| 2023-03-31 13:05:41 +0200 | <geekosaur> | I think tomsmeding didn't want to have to set up full text indexing |
| 2023-03-31 13:05:56 +0200 | <geekosaur> | not sure if that's enabled |
| 2023-03-31 13:06:19 +0200 | <Ou42> | no worries. |
| 2023-03-31 13:06:52 +0200 | <Solid> | for reference: https://ircbrowse.tomsmeding.com/browse/lcxmonad |
| 2023-03-31 13:07:04 +0200 | <Ou42> | morning solid! |
| 2023-03-31 13:07:21 +0200 | <Ou42> | you guys really should move to PST, then we can all be up at 4AM |
| 2023-03-31 13:07:42 +0200 | <Solid> | waking up at 4am would really be something |
| 2023-03-31 13:07:46 +0200 | <geekosaur> | I just tried a site: search and it seems not, at least for lcxmonad (I did get one hit for lchaskell) |
| 2023-03-31 13:07:47 +0200 | <Solid> | but I think I'll pass :) |
| 2023-03-31 13:08:01 +0200 | <geekosaur> | I woke at 4am, yet again 😞 |
| 2023-03-31 13:08:08 +0200 | <geekosaur> | gonna need a nap today I think |
| 2023-03-31 13:09:57 +0200 | <Ou42> | same. |
| 2023-03-31 13:10:33 +0200 | <Ou42> | FYI, Solid isn't making a Billion$ on a bet I could annoy you. Your paticence is legendary. |
| 2023-03-31 13:11:15 +0200 | <Ou42> | ugh, full disclaimer, I've never been here before whenever that was... time blurs when one doesn't sleep |
| 2023-03-31 13:11:30 +0200 | <Ou42> | OK, here's my noob Q |
| 2023-03-31 13:11:36 +0200 | <Ou42> | from the xmonad.org tut: |
| 2023-03-31 13:11:40 +0200 | <Ou42> | "Changing What XMonad Sends to Xmobar" |
| 2023-03-31 13:12:00 +0200 | <Ou42> | I know this is boneheaded, but what is Xmonad sending to Xmobar?! |
| 2023-03-31 13:12:14 +0200 | <Ou42> | and why do [I] have to change the way they initially set it up? |
| 2023-03-31 13:12:36 +0200 | <Ou42> | <https://xmonad.org/TUTORIAL.html> |
| 2023-03-31 13:12:39 +0200 | <geekosaur> | that string you were talking about earlier, showing the active workspaces and window titles, etc |
| 2023-03-31 13:13:02 +0200 | <geekosaur> | and you can change it to customize how it appears, add/remove information, etc. |
| 2023-03-31 13:13:10 +0200 | <Ou42> | right, bt it's working and I didn't AFAICR yet continue w/ the tut. |
| 2023-03-31 13:13:45 +0200 | <geekosaur> | https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs#L318-L336 is what I send |
| 2023-03-31 13:14:20 +0200 | <geekosaur> | although I send it to xmonad-log-applet instead of xmobar because I use xmonad as MATE's window manager and run mate-panel instead of xmobar |
| 2023-03-31 13:14:48 +0200 | <Ou42> | you keep asking my 2ndary Q's before I can formulate them |
| 2023-03-31 13:14:50 +0200 | <Ou42> | amazing. |
| 2023-03-31 13:15:17 +0200 | <Ou42> | i dumped MATE as the panel hiccuped and the "click in the open space" part was a killer as there wasn't any |
| 2023-03-31 13:15:51 +0200 | <Solid> | Ou42: suggestions to improve the tutorial are always welcome (places that are hard to understand for a newcomer etc.) |
| 2023-03-31 13:15:55 +0200 | <Ou42> | moved to Cinamon. I've tinkered w/ xfce in the past and more beofre MATE, KDE |
| 2023-03-31 13:16:27 +0200 | <Ou42> | Solid: will keep that in mind. I would love to give back somehow. |
| 2023-03-31 13:16:52 +0200 | <Ou42> | I've been slowly learning Haskell for a while now. Not making any speed records learning it. |
| 2023-03-31 13:17:06 +0200 | <Solid> | Obviously I tried, but it's hard to know exactly what someone new to XMonad will find difficult, what they know and don't know etc. |
| 2023-03-31 13:18:02 +0200 | <Ou42> | it's honestly very good. I think the main issue y'all have is what's "broken" or easily broken by noobs when they try to implement sometihng that is "old" w/ the new stuff. |
| 2023-03-31 13:19:52 +0200 | <Ou42> | it honestly could have been my wonky haskell setup, but trying to get ewmhFullscreen to work before ( Jan per datestamps ) was a mess. I probably had wrong versions and I"m not that adept at stack and was trying to get it to serve a particular ghc ver w/o knowing what I was doing. |
| 2023-03-31 13:20:06 +0200 | <Ou42> | this attempt has been much more ... productive. |
| 2023-03-31 13:20:21 +0200 | <Ou42> | and it's because of that tut off of xmonad.org and the help here |
| 2023-03-31 13:20:34 +0200 | <Ou42> | single source of truth |
| 2023-03-31 13:20:41 +0200 | <Ou42> | unix philosophy |
| 2023-03-31 13:22:21 +0200 | <Ou42> | ah! memories. I rem why i deviated |
| 2023-03-31 13:22:42 +0200 | <Ou42> | what exactly is .xinitrc? and/or is it something that would be accessed by every WM? |
| 2023-03-31 13:23:42 +0200 | <Ou42> | "For the remainder of this document, .... If you have set up your ~/.xinitrc as directed in the xmonad guided tour, you should be good to go! If not, just smack an exec xmonad at the bottom of that file." |
| 2023-03-31 13:23:53 +0200 | <Solid> | It's the config for `xinit(1)` |
| 2023-03-31 13:24:06 +0200 | <Ou42> | I'd prefer to keep thinks as selfcontained and not affect the other WM/DE's |
| 2023-03-31 13:24:06 +0200 | <Solid> | it's what starts X11 when you don't have a display manager |
| 2023-03-31 13:24:21 +0200 | <Solid> | If you do then how to start XMonad depends on what you use |
| 2023-03-31 13:25:25 +0200 | <Ou42> | I"m not the smartest noob, changing any documentation based on my "preferences" might be a tad overkill. I'd prefer to keep xmonad "inside xmonad" to a point. I will contradict myself, by say using .Xresources. |
| 2023-03-31 13:26:16 +0200 | <Solid> | I mean, at some point you have to tell X11 which window manager to use |
| 2023-03-31 13:26:47 +0200 | <Solid> | whether that'd be via xinitrc or with a dm |
| 2023-03-31 13:27:02 +0200 | <Ou42> | but I ad a switcher already setup and whatever I had before was there, so I didn't start from scratch this time... I had xmonad installed... I jsut thought it was broken. I wiped out the xmonad.hs file and started w/ the tut. |
| 2023-03-31 13:27:18 +0200 | <Solid> | (if you plan on using multiple DEs/WMs then a display manager is definietly the better choice) |
| 2023-03-31 13:27:21 +0200 | <Ou42> | oh oh oh DM = switcher |
| 2023-03-31 13:27:31 +0200 | <Ou42> | yes, got that |
| 2023-03-31 13:27:41 +0200 | <Solid> | ah, yes :) |
| 2023-03-31 13:27:47 +0200 | <Ou42> | i can choose xmonad from a drop down on a GUI screen |
| 2023-03-31 13:29:51 +0200 | <Ou42> | OK, so here it is: |
| 2023-03-31 13:29:52 +0200 | <geekosaur> | right, so that doesn't use .xinitrc, it uses /usr/share/xsessions/xmonad.desktop and there's an Exec= line in there that tells it what to do |
| 2023-03-31 13:29:53 +0200 | <Ou42> | "Your ~/.xinitrc may wind up looking like this:" |
| 2023-03-31 13:30:08 +0200 | <Ou42> | right |
| 2023-03-31 13:30:14 +0200 | <Ou42> | I"m slow at skimming |
| 2023-03-31 13:30:16 +0200 | <Ou42> | sorry |
| 2023-03-31 13:31:07 +0200 | <Ou42> | so it's not req to use .xinitrc to start xmonad, but then you suggest editing it to include feh, nm-applet, trayer, and a few other things |
| 2023-03-31 13:31:34 +0200 | <Ou42> | so I didn't, I did the "myStarUpHooks = do" block thing |
| 2023-03-31 13:31:39 +0200 | <geekosaur> | right, because .xinitrc is the closest thing to a standard there is, but it assumes startx is used |
| 2023-03-31 13:32:07 +0200 | <geekosaur> | .xsession is another possibility (and is used on debian if .xinitrc doesn't exist even for startx/xinit) |
| 2023-03-31 13:33:38 +0200 | <Ou42> | not trying to be difficult ( it comes naturally ), but what if I didn't want to use any of those files? is it possible to *completely* setup xmobar / trayer w/o one of those files? |
| 2023-03-31 13:33:43 +0200 | <geekosaur> | also the xmonad.desktop on debian and derivatives runs xmonad-session which runs ~/.xmonad/xmonad-session-rc before starting xmonad iirc |
| 2023-03-31 13:33:50 +0200 | <geekosaur> | but that is very debian-dependent |
| 2023-03-31 13:34:23 +0200 | <geekosaur> | you can run stuff in the startupHook |
| 2023-03-31 13:34:44 +0200 | <Ou42> | i think my gist is the same... checking. |
| 2023-03-31 13:35:07 +0200 | <geekosaur> | but for xmobar, since we need to be able to send it information about workspaces, you use `withEasySB` to start it |
| 2023-03-31 13:35:39 +0200 | <geekosaur> | https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs#L181-L198 |
| 2023-03-31 13:38:50 +0200 | <Ou42> | OK ... |
| 2023-03-31 13:39:09 +0200 | <Ou42> | huh |
| 2023-03-31 13:39:26 +0200 | <Ou42> | brb |
| 2023-03-31 13:45:04 +0200 | <Ou42> | if either of you 2 are up for this... I'll upload another gist... short ver: xmobar is up and it does give some feedback ( still using xmobarProp iteration from tut ) |
| 2023-03-31 13:45:16 +0200 | <Ou42> | trayer is up but on the wrong screen |
| 2023-03-31 13:45:23 +0200 | <Ou42> | can look into fixing that later |
| 2023-03-31 13:45:34 +0200 | <Ou42> | but it does make seeing what is working / not working harder |
| 2023-03-31 13:45:50 +0200 | <Ou42> | feh is working via spawnOnce |
| 2023-03-31 13:46:07 +0200 | <Ou42> | trayer & nm-applet |
| 2023-03-31 13:46:35 +0200 | <Ou42> | are too, but spawnOnce "xfce4-power-manager &" isnt' showing up |
| 2023-03-31 13:47:17 +0200 | <Ou42> | oh and hexchat has an icon showing up on trayer too |
| 2023-03-31 13:47:31 +0200 | redgloboli | (~redglobol@user/redgloboli) (Quit: ...enter the matrix...) |
| 2023-03-31 13:48:28 +0200 | redgloboli | (~redglobol@user/redgloboli) |
| 2023-03-31 13:49:26 +0200 | <geekosaur> | you may need to run that one in a terminal and see what errors if any it spits out |
| 2023-03-31 13:50:10 +0200 | <geekosaur> | although you may also need to check if it's actually running; conceivably it's configured to not show an icon when fully charged on power (I know I can set up mate-power-manager that way) |
| 2023-03-31 13:50:38 +0200 | <Ou42> | interesting |
| 2023-03-31 13:52:29 +0200 | <Ou42> | "$ Xfce Power Manager: Another power manager is already running" |
| 2023-03-31 13:52:59 +0200 | <geekosaur> | pgrep xfce4-power-manager |
| 2023-03-31 13:54:40 +0200 | <Ou42> | shows nothing |
| 2023-03-31 13:57:54 +0200 | <geekosaur> | ps -ef | grep power |
| 2023-03-31 13:58:31 +0200 | <geekosaur> | (which on my system shows the indicator icon is in fact a separate process… /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service) |
| 2023-03-31 14:01:08 +0200 | <Ou42> | which means ... there needs to be something else to attach it to trayer? |
| 2023-03-31 14:01:39 +0200 | <geekosaur> | looks like it, yes |
| 2023-03-31 14:05:44 +0200 | <Ou42> | I'm gonna try a tweak for trayer... might get disconnected... |
| 2023-03-31 14:09:11 +0200 | <Ou42> | I guess I don't get dc'd... OK, so uhhh spawnOnce... if a M-q is issued, will all spanOnce items get skipped? |
| 2023-03-31 14:12:07 +0200 | <geekosaur> | yes |
| 2023-03-31 14:12:22 +0200 | <geekosaur> | that's the point of spawnOnce |
| 2023-03-31 14:15:23 +0200 | <Ou42> | so I have to logout to test my trayer changes? |
| 2023-03-31 14:16:26 +0200 | <geekosaur> | or kill and restart it from a terminal |
| 2023-03-31 14:17:35 +0200 | <Ou42> | i killed it. I"m a killer. mom will be so disapointed |
| 2023-03-31 14:23:59 +0200 | <Ou42> | so silly |
| 2023-03-31 14:24:04 +0200 | <Ou42> | testing |
| 2023-03-31 14:25:10 +0200 | <Ou42> | yup. user error again. |
| 2023-03-31 14:25:19 +0200 | <Ou42> | that's at least 4 blunders on my end. |
| 2023-03-31 14:25:47 +0200 | <Ou42> | didn't copy the line right... dropped "--width 10", but how?! |
| 2023-03-31 14:26:42 +0200 | <geekosaur> | not sure what you're asking |
| 2023-03-31 14:27:02 +0200 | <geekosaur> | also not sure how you fit more than a couple of indicators into --width 10 🙂 |
| 2023-03-31 14:28:09 +0200 | <Ou42> | I have 3 and looks like room for 2 more! |
| 2023-03-31 14:28:13 +0200 | <Ou42> | :oD |
| 2023-03-31 14:28:34 +0200 | <Ou42> | I dunno about all this. really bad noob errors on my end. |
| 2023-03-31 14:29:15 +0200 | <Ou42> | what does a tray look like w/o any indicators? w/ no width assignment? |
| 2023-03-31 14:29:51 +0200 | <Ou42> | i should write a book. "noob's guide to inefficient computing". |
| 2023-03-31 14:31:51 +0200 | <Ou42> | interstingly picom is working better now too... I was getting transparency, but the rectangle was larger than it needed to be. now it's fine. |
| 2023-03-31 14:32:27 +0200 | <Ou42> | OK, I'll go back over the tut and see what changing things for xmobar does/doesn't do ... |
| 2023-03-31 14:32:54 +0200 | <Ou42> | or much more likely what boneheaded typo's and mistakes and things I'll accidentally leave out that will cause me hours of adventures |
| 2023-03-31 14:33:57 +0200 | <Ou42> | BTW, the "--width 10" is directly from the tut. Not my doing. My subconcious, apparently, wanted the width to fill the screen. |
| 2023-03-31 14:35:19 +0200 | <geekosaur> | I think the tutorial is shooting for having xmobar and trayer share the same part of the screen, so xmobar should be a little short and trayer's supposed to fill in the rest? but that's Solid's bailiwick since I don't run either |
| 2023-03-31 14:36:31 +0200 | <Ou42> | Yes, he sets xmobar at 90 and trayer at 10 |
| 2023-03-31 14:37:25 +0200 | <Ou42> | I still have a ton of Q's, but you've given me a ton to sift thru. tyvm |
| 2023-03-31 14:38:29 +0200 | <Ou42> | Solid: your tut is fine. maybe add a warning, "leaving out '--width 10' will cause trayer to expand to the full screen width and occlude xmobar. |
| 2023-03-31 14:38:49 +0200 | <Ou42> | y'know? for those "special" noobs. |
| 2023-03-31 14:50:15 +0200 | jade[m] | (~jade1024t@2001:470:69fc:105::3:238b) () |
| 2023-03-31 14:57:26 +0200 | stellacy1 | (~stellacy@gateway/tor-sasl/stellacy) |
| 2023-03-31 14:57:38 +0200 | stellacy | (~stellacy@gateway/tor-sasl/stellacy) (Ping timeout: 255 seconds) |
| 2023-03-31 15:05:29 +0200 | stellacy1 | (~stellacy@gateway/tor-sasl/stellacy) (Remote host closed the connection) |
| 2023-03-31 15:06:26 +0200 | stellacy | (~stellacy@gateway/tor-sasl/stellacy) |
| 2023-03-31 15:14:01 +0200 | <Ou42> | If I wanted to make a git repo to track all these files ... but to have them in the same directory/folder, would u symlink them into the .config/xmonad folder and git init there? or put the actual files there and symlink them were they are accessed? or something else? |
| 2023-03-31 15:15:10 +0200 | <Ou42> | ( off the top of my head it's ~/.config/xmonad/xmonad.hs, ~/.Xresources, ~/.xmobarrc ) |
| 2023-03-31 15:33:42 +0200 | <galactic_starfis> | I hate the work needed to get trayer working with xmb |
| 2023-03-31 15:33:48 +0200 | <galactic_starfis> | It's so buggy and broken too |
| 2023-03-31 15:34:21 +0200 | <galactic_starfis> | If xmobat could read window sizes that would help |
| 2023-03-31 15:34:28 +0200 | <galactic_starfis> | R* |
| 2023-03-31 15:49:33 +0200 | matijja | (~matijja@193.77.181.201) (Ping timeout: 250 seconds) |
| 2023-03-31 15:51:57 +0200 | matijja | (~matijja@193.77.181.201) |
| 2023-03-31 15:53:53 +0200 | chomwitt | (~chomwitt@2a02:587:7a16:e500:1ac0:4dff:fedb:a3f1) (Ping timeout: 250 seconds) |
| 2023-03-31 16:18:47 +0200 | <Ou42> | my bad luck! git tut was wrong! |
| 2023-03-31 16:18:49 +0200 | hightower2 | (~hightower@213.149.51.128) |
| 2023-03-31 16:18:51 +0200 | <Ou42> | <https://mokacoding.com/blog/symliks-in-git/> |
| 2023-03-31 16:18:55 +0200 | <Ou42> | grrr |
| 2023-03-31 16:19:51 +0200 | <Ou42> | ofc I could be interpretting things incorrectly. ;o) |
| 2023-03-31 16:24:21 +0200 | <geekosaur> | the latter |
| 2023-03-31 16:24:40 +0200 | <geekosaur> | and no, git doesn't do symlinks because they're not portable (specifically, to Windows) |
| 2023-03-31 16:24:59 +0200 | <geekosaur> | (not that you care because xmonad doesn't run on Windows, but git does) |
| 2023-03-31 16:25:25 +0200 | ft | (~ft@p4fc2a88b.dip0.t-ipconnect.de) |
| 2023-03-31 16:40:45 +0200 | <Ou42> | geekosaur: thanks |
| 2023-03-31 16:41:05 +0200 | <Ou42> | ... I was trying to convert them to hard links, but I don't know what I'm doing. |
| 2023-03-31 16:41:47 +0200 | <geekosaur> | https://github.com/geekosaur/xmonad.hs/tree/skkukuk fwiw |
| 2023-03-31 16:42:29 +0200 | stellacy | (~stellacy@gateway/tor-sasl/stellacy) (Ping timeout: 255 seconds) |
| 2023-03-31 16:45:09 +0200 | <Ou42> | "compton.conf should be symlinked into ~/.config" |
| 2023-03-31 16:46:08 +0200 | <Ou42> | I'll be symlinking these 4: stack.yaml, xmonad.hs, .Xresources & .xmobarrc. |
| 2023-03-31 16:47:36 +0200 | Ou42 | thinking |
| 2023-03-31 16:47:49 +0200 | <Ou42> | I dunno if I'm still using stack ?! hmmm |
| 2023-03-31 16:48:03 +0200 | <Ou42> | to compile xmobar I used cabal |
| 2023-03-31 16:48:21 +0200 | <Ou42> | this cross-training is turning out to be a huge adventure. |
| 2023-03-31 16:50:26 +0200 | <geekosaur> | fwiw I `git clone`d to ~/.config/xmonad and symlinked other stuff (compton.conf, xmessage, 10profile) from there |
| 2023-03-31 16:50:45 +0200 | <geekosaur> | I no longer use start-xmonad.desktop since MATE stopped requiring it for window managers |
| 2023-03-31 16:52:04 +0200 | <Ou42> | I'm avoiding a line of Q's that might make things easier, but I kinda want to take the slow road. MATE was "OK" but editting the panel. eeesh. |
| 2023-03-31 17:08:08 +0200 | stackdroid18 | (14094@de1.hashbang.sh) |
| 2023-03-31 17:09:43 +0200 | <Ou42> | ah, you said git doesn't do symlinks... I misread that. I had "dir junctions" in Windows so my VM files could be on an ext ssd. |
| 2023-03-31 17:10:01 +0200 | <Ou42> | but I'm dual booting now. |
| 2023-03-31 17:11:12 +0200 | <Ou42> | the neat thing about the "symlinks" was I could fire up my VM on different hw as long as I had vritualbox installed. I'm still not sure about this native setup thing when it comes to upgrading more often. It's a pain. |
| 2023-03-31 17:11:45 +0200 | <Ou42> | but the non virtualized speed is nice. |
| 2023-03-31 17:11:57 +0200 | <geekosaur> | well, the situation is more complex than "doesn't have symlinks". for excample, win10 past some version does have them, in a new API that older versions don't have |
| 2023-03-31 17:12:36 +0200 | <geekosaur> | but in older windows back to win7 there are junction points, which function somewhat as symlinks but require an administrator to create/manipulate/delete |
| 2023-03-31 17:15:54 +0200 | <Ou42> | good to know. I pretty much learned how to do junctions because of all this "symplink" this and "symlink" that. So, basically, Linux muscle got me to try something in Win that was a 2nd cousin once removed. |
| 2023-03-31 17:16:39 +0200 | stellacy | (~stellacy@gateway/tor-sasl/stellacy) |
| 2023-03-31 17:18:36 +0200 | hightower2 | (~hightower@213.149.51.128) (Remote host closed the connection) |
| 2023-03-31 17:18:59 +0200 | hightower2 | (~hightower@213.149.51.128) |
| 2023-03-31 17:20:58 +0200 | <geekosaur> | when it comes down to it, though, a symlink even when supported is a pointer somewhere else. I want the contents, not a pointer |
| 2023-03-31 17:21:13 +0200 | <geekosaur> | so the actual file is in my repo and I symlink that elsewhere |
| 2023-03-31 17:21:54 +0200 | <Ou42> | yup. I just read the tut wrong. again. one of these days I'll grok all this. but the git symlink tut was misleading. |
| 2023-03-31 17:22:20 +0200 | <Ou42> | it's taking me a long time to git rm, mv, cd, ln the right way, for only 4 files |
| 2023-03-31 17:23:27 +0200 | hightower2 | (~hightower@213.149.51.128) (Ping timeout: 255 seconds) |
| 2023-03-31 17:23:45 +0200 | <Ou42> | the sad thing is ... this is probably not the right way either |
| 2023-03-31 17:23:49 +0200 | <Ou42> | I made a sub-folder |
| 2023-03-31 17:24:00 +0200 | <Ou42> | so I probably will need to move things again |
| 2023-03-31 17:24:04 +0200 | <Ou42> | oh well |
| 2023-03-31 17:28:01 +0200 | <Ou42> | I was supposed to delete the last commit before making changes, wasn't I? |
| 2023-03-31 17:29:07 +0200 | <Ou42> | why bother erasing the past? |
| 2023-03-31 17:29:16 +0200 | <Ou42> | gotta keep moving fwd! |
| 2023-03-31 17:58:16 +0200 | <Ou42> | geekosaur: Finally have a git repo going: <https://github.com/Ou42/xmonad-adventure/blob/main/xmonad.hs> |
| 2023-03-31 18:00:14 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Remote host closed the connection) |
| 2023-03-31 18:00:15 +0200 | belowdecent[m] | (~belowdece@2001:470:69fc:105::2:f47c) (Quit: You have been kicked for being idle) |
| 2023-03-31 18:00:36 +0200 | <Ou42> | "below decent" |
| 2023-03-31 18:00:40 +0200 | Ou42 | thinking |
| 2023-03-31 18:13:33 +0200 | <Ou42> | ofc I goofed! I should change my nick to super below, below decent. |
| 2023-03-31 18:14:21 +0200 | <Ou42> | "Errors detected while compiling xmonad config: /home/me/.config/xmonad/xmonad.hs $ stack build --silent --stack-yaml /home/me/.config/xmonad/git-repo/stack.yaml Please check the file for errors. |
| 2023-03-31 18:15:27 +0200 | <Ou42> | I was able to find those lins in .xsessions-errors, but where are the acual errors?! are they saved or does "--silent" mute them? |
| 2023-03-31 18:15:47 +0200 | <Ou42> | i see the whitespace issue, but would be nice to get help from ghc, no? |
| 2023-03-31 18:16:02 +0200 | hightower2 | (~hightower@85.94.71.188) |
| 2023-03-31 18:16:47 +0200 | <geekosaur> | --silent shouldn't mute the errors but stack may be putting them in a log file somewhere. I'm not really familiar with it |
| 2023-03-31 18:17:36 +0200 | <geekosaur> | (I use cabal pretty exclusively and have only used stack when debugging someone else's config that uses it) |
| 2023-03-31 18:18:51 +0200 | <Ou42> | it wasn't the whitespace issue I saw |
| 2023-03-31 18:25:04 +0200 | <Ou42> | brb |
| 2023-03-31 18:25:21 +0200 | Ou42 | (~Ou4242a@2600:1700:e930:41b0:27e2:d5f9:7e0c:462b) (Quit: Leaving) |
| 2023-03-31 18:30:14 +0200 | Ou42 | (~Ou4242a@2600:1700:e930:41b0:27e2:d5f9:7e0c:462b) |
| 2023-03-31 18:30:35 +0200 | <Ou42> | "xmonad: X11 error: BadAtom (invalid Atom parameter), request code=18, error code=5" |
| 2023-03-31 18:32:08 +0200 | <Ou42> | "Bad _NET_WM_DESKTOP with data=[-1,0,0,0,0]" |
| 2023-03-31 18:32:20 +0200 | <geekosaur> | 18 is XChangeProperty |
| 2023-03-31 18:32:38 +0200 | <Ou42> | ?? |
| 2023-03-31 18:32:54 +0200 | <geekosaur> | and the _NET_WM_DESKTOP thing is known, you can ignore it. (something is trying to display on all desktops, EwmhDesktops doesn't support that as yet) |
| 2023-03-31 18:33:18 +0200 | <Ou42> | I set allDesktops to True |
| 2023-03-31 18:33:21 +0200 | <Ou42> | in xmobar |
| 2023-03-31 18:33:27 +0200 | <Ou42> | but it's been running, i thought |
| 2023-03-31 18:33:51 +0200 | <Ou42> | I'm also getting xfce4-power-manager errros.... last line ends with: |
| 2023-03-31 18:33:56 +0200 | <Ou42> | "Failed to connect to session manager: Failed to connect to the session manager: SESSION_MANAGER environment variable not defined" |
| 2023-03-31 18:34:23 +0200 | <geekosaur> | right, so it only works as part of an xfce4 desktop, not standalone |
| 2023-03-31 18:34:36 +0200 | <geekosaur> | xfce made that change several years ago |
| 2023-03-31 18:34:56 +0200 | <Ou42> | then I should make a PR? as it's the things in xmonad.org's tut |
| 2023-03-31 18:35:44 +0200 | <geekosaur> | uh? I don't recall the power manager being in there |
| 2023-03-31 18:36:53 +0200 | <Ou42> | I'm def not multitasking that fast. gimme a sec and I'll link/copy/paste it |
| 2023-03-31 18:37:07 +0200 | <geekosaur> | oh, found it. guess that's a non-starter then |
| 2023-03-31 18:37:18 +0200 | <geekosaur> | Solid ^ |
| 2023-03-31 18:37:29 +0200 | <geekosaur> | and it looks like lxde doesn't have its own |
| 2023-03-31 18:37:33 +0200 | hightower2 | (~hightower@85.94.71.188) (Remote host closed the connection) |
| 2023-03-31 18:38:44 +0200 | <Ou42> | consider the source. ;o) If you want I could fire up a VM and try everything clean and see if the same issues persist. |
| 2023-03-31 18:38:50 +0200 | <Ou42> | but that will take me a bit of time. |
| 2023-03-31 18:39:47 +0200 | Solid | uses xfce-power-manager |
| 2023-03-31 18:39:55 +0200 | <Solid> | and I definitely don't run the xfce desktop :) |
| 2023-03-31 18:40:21 +0200 | <Ou42> | dont' knock it. some of us felt they had to ... for years |
| 2023-03-31 18:40:31 +0200 | <Ou42> | and even now I wonder if I should return to it. |
| 2023-03-31 18:40:41 +0200 | <Ou42> | when not using xmonad, ofc. |
| 2023-03-31 18:40:42 +0200 | <Ou42> | ;o) |
| 2023-03-31 18:41:05 +0200 | <geekosaur> | maybe it just throws those but they're not really meaningful? wouldn't be the first time |
| 2023-03-31 18:41:15 +0200 | <geekosaur> | (meaning it's actually a warning)) |
| 2023-03-31 18:41:22 +0200 | <Ou42> | "xmobar: Caught signal 15; exiting..." |
| 2023-03-31 18:41:46 +0200 | <Ou42> | "ATTENTION: default value of option mesa_glthread overridden by environment." |
| 2023-03-31 18:42:25 +0200 | <Ou42> | "xfce4-power-manager-WARNING **: 09:26:23.564: Failed to get keyboard max brightness level : GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/freedesktop/UPower/KbdBacklight”" |
| 2023-03-31 18:42:26 +0200 | <geekosaur> | as for allDesktops in xmobar, that shouldn't be the source of the _NET_WM_DESKTOP thing because it's unmanaged so desktops don't really apply to it as such |
| 2023-03-31 18:42:47 +0200 | <geekosaur> | unless your keyboard is backlit, that can be ignored |
| 2023-03-31 18:42:54 +0200 | <Ou42> | yeah, no change on M-q w/ allDesktops set to False. better check it's not Flase |
| 2023-03-31 18:43:16 +0200 | <Ou42> | I have a usb keyboard that is backlit and I used it last monday. |
| 2023-03-31 18:43:30 +0200 | <geekosaur> | but are you using it now? |
| 2023-03-31 18:44:24 +0200 | <geekosaur> | if not, xfce4-power-manager has nothing to connect to for keyboard brightness. and even if you were, it would only apply to keyboards whose brightness could be adjusted by the OS |
| 2023-03-31 18:44:43 +0200 | <geekosaur> | (I've had two backlit keyboards, neither could be adjusted by the OS) |
| 2023-03-31 18:45:34 +0200 | <Ou42> | semi-related, but MATE's battery tray icon would give me battery satus of wireless keyboard. no clue if accurate, but thought it interesting. |
| 2023-03-31 18:46:00 +0200 | <Ou42> | i dont' see anything wrong. any clue how to find the "file" w/ the error messages? |
| 2023-03-31 18:48:28 +0200 | <geekosaur> | error messages about what, your config? |
| 2023-03-31 18:48:46 +0200 | <geekosaur> | I don't know stack well enough to know where it would put its logs |
| 2023-03-31 18:48:48 +0200 | <Ou42> | it's not just warnings |
| 2023-03-31 18:49:01 +0200 | <Ou42> | because trayer is going to the bottom when I moved it back to the top |
| 2023-03-31 18:49:13 +0200 | <Ou42> | what on earth changed besides symlinks? |
| 2023-03-31 18:49:56 +0200 | <Ou42> | so it's failing to build, but it can still use the prev version, but I changed trayer to move to the top... but I ran it in term |
| 2023-03-31 18:50:46 +0200 | chomwitt | (~chomwitt@ppp-94-69-24-223.home.otenet.gr) |
| 2023-03-31 18:54:18 +0200 | <Ou42> | ok, has to be the symlinking... |
| 2023-03-31 18:54:32 +0200 | <Ou42> | and ran the stack cmd w/o "--silent" but it errors out w/ |
| 2023-03-31 18:54:48 +0200 | <Ou42> | "getDirectoryContents:openDirStream: does not exist (No such file or directory)" |
| 2023-03-31 18:54:56 +0200 | <Ou42> | so moving stack.yaml is the issue |
| 2023-03-31 18:55:05 +0200 | <Ou42> | prob relative ref for dir |
| 2023-03-31 18:55:34 +0200 | <Ou42> | ".config/xmonad/git-repo/xmonad: getDirectoryContents:openDirStream: does not exist (No such file or directory)" |
| 2023-03-31 18:55:49 +0200 | <Ou42> | it should be ".config/xmonad/git-repo/" |
| 2023-03-31 18:59:26 +0200 | <Ou42> | fixed: I don't need to symlink stack.yaml. I can copy it for backups as needed ( when I remember ) |
| 2023-03-31 18:59:54 +0200 | <Ou42> | I changed the color of xmobar and trayer is back on top vs botom. so it is working. |
| 2023-03-31 19:00:12 +0200 | <Ou42> | symlinking stack.yaml was the culprit. |
| 2023-03-31 19:02:24 +0200 | <Ou42> | since I"m still here and "awake" a quick Q: when in "tiled" layout, why does M-J go CW and M-k CCW? |
| 2023-03-31 19:04:21 +0200 | <geekosaur> | were you expecting something else? |
| 2023-03-31 19:05:10 +0200 | <Ou42> | the opposite. every time! |
| 2023-03-31 19:06:27 +0200 | <Ou42> | it's worse in "mirroed" w/ 1 master on top and 3 stacked on bottom. J goes right and K goes left. weird. |
| 2023-03-31 19:07:44 +0200 | <Ou42> | I fig it's akin to a flight stick |
| 2023-03-31 19:07:51 +0200 | <Ou42> | just gotta learn the ropes |
| 2023-03-31 19:08:13 +0200 | <Ou42> | apprecaite the help and support. |
| 2023-03-31 19:08:38 +0200 | <geekosaur> | it's a combination of the StackSet (M-j is focusDown) and the order of rectangles returned by the layout. I would expect focusDown to go CW but I've been using this for 15 years |
| 2023-03-31 19:08:55 +0200 | <geekosaur> | but I also think you're pretty much the only one who's asked about that |
| 2023-03-31 19:09:20 +0200 | <Ou42> | therefore we must rewrite all the tutorials ASAP! |
| 2023-03-31 19:09:23 +0200 | <geekosaur> | you could always swap the bindings if you feel that strongly about window order |
| 2023-03-31 19:09:42 +0200 | <Ou42> | I get nervous when deviating from the defaults, but good to know |
| 2023-03-31 19:10:48 +0200 | <Ou42> | lemme see if can iterate on xmond.org tut and get to the next level of xmobar integration, then, xmessage replacement, maybe?! dunno. you sent a link. |
| 2023-03-31 19:12:00 +0200 | <Ou42> | not complaining.. just observing... in tabbed layout, it is ... something to get used to w/ J going right and K going left. |
| 2023-03-31 19:14:12 +0200 | <geekosaur> | re "deviating from the defaults", the whole point of xmonad is its customizability. you're supposed to deviate from the defaults 🙂 |
| 2023-03-31 19:14:23 +0200 | <Ou42> | /me wets himself |
| 2023-03-31 19:14:32 +0200 | Ou42 | grrrr |
| 2023-03-31 19:16:18 +0200 | <Ou42> | since a ton of this adventure is learning more Linux, which I've put off for too long, how much to attention to decrecation warnings? off the top of my mind: compton & autorandr |
| 2023-03-31 19:16:38 +0200 | <Ou42> | the typos are gonna kill me |
| 2023-03-31 19:24:43 +0200 | <geekosaur> | compton, you should probably switch to picom if it's packaged |
| 2023-03-31 19:25:40 +0200 | <geekosaur> | autorandr is deprecated? I wasn't aware of that |
| 2023-03-31 19:27:14 +0200 | <liskin> | compton is fine, picom only made things worse :-) |
| 2023-03-31 19:27:15 +0200 | <Ou42> | sorry, I was trying to be concise |
| 2023-03-31 19:27:32 +0200 | <Ou42> | picom is working, just using basic like compton .... |
| 2023-03-31 19:27:40 +0200 | <Ou42> | spawnOnce "picom &" |
| 2023-03-31 19:28:25 +0200 | <Ou42> | "/usr/bin/autorandr:42: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives -- from distutils.version import LooseVersion as Version" |
| 2023-03-31 19:29:27 +0200 | <geekosaur> | you can't do much about that one |
| 2023-03-31 19:30:00 +0200 | <Ou42> | it says Python 3.12, but I have Python 3.10.6 installed. So upgrading is a no go? |
| 2023-03-31 19:30:30 +0200 | <Ou42> | So much to learn so little time! |
| 2023-03-31 19:33:13 +0200 | <Ou42> | > $ compton -h |
| 2023-03-31 19:33:13 +0200 | <Ou42> | compton (1) |
| 2023-03-31 19:33:14 +0200 | <Ou42> | This is the maintenance fork of compton, please report |
| 2023-03-31 19:33:14 +0200 | <Ou42> | bugs to https://github.com/yshui/compton |
| 2023-03-31 19:33:15 +0200 | <lambdabot> | <hint>:1:1: error: |
| 2023-03-31 19:33:15 +0200 | <lambdabot> | parse error on input ‘$’ |
| 2023-03-31 19:33:15 +0200 | <lambdabot> | Perhaps you intended to use TemplateHaskell |
| 2023-03-31 19:33:51 +0200 | <Ou42> | I dunno, but I thought I saw that compton was deprecated and picom was the successor. This sounds like compton is alive and kicking. |
| 2023-03-31 19:34:28 +0200 | <Ou42> | or... |
| 2023-03-31 19:34:38 +0200 | <Ou42> | clicking on that link redirects to ... |
| 2023-03-31 19:34:51 +0200 | <Ou42> | <https://github.com/yshui/picom> |
| 2023-03-31 19:41:27 +0200 | <geekosaur[m]> | Right, it has a complex history |
| 2023-03-31 19:41:44 +0200 | <Ou42> | OK, so when do we start to rewrite everything in Haskell? |
| 2023-03-31 19:44:04 +0200 | <geekosaur> | probably never; that's a lot of effort that has to be maintained to keep feature parity |
| 2023-03-31 19:44:18 +0200 | <geekosaur> | binding to libraries works better |
| 2023-03-31 19:44:58 +0200 | <geekosaur> | and rewriting xcompmgr/compton/picom in Haskell won't avoid the issue of maintainers vanishing and others forking it, possibly renaming it, and taking over maintenance |
| 2023-03-31 19:45:18 +0200 | <geekosaur> | (happened to xcompmgr twice before it was renamed, then to compton once before it was renamed) |
| 2023-03-31 19:46:39 +0200 | <Ou42> | but what maintenence? if it compiles it runs. |
| 2023-03-31 19:46:44 +0200 | <Ou42> | ;o) |
| 2023-03-31 19:47:08 +0200 | <geekosaur> | but does it do what it's supposed to? |
| 2023-03-31 19:47:26 +0200 | <geekosaur> | (Knuth: "I have only proven this program correct, not tested it.") |
| 2023-03-31 19:48:10 +0200 | <geekosaur> | basically when it comes to IO, all bets are off |
| 2023-03-31 19:48:31 +0200 | <geekosaur> | and even with pure code, tell me what `Num a => a -> a` does |
| 2023-03-31 19:50:13 +0200 | <Ou42> | id? no, its got a constraint. |
| 2023-03-31 19:50:53 +0200 | <geekosaur> | that type has an infinite number of inhabitants 🙂 |
| 2023-03-31 19:50:58 +0200 | <Ou42> | I haven't really graduated to IO yet. only simple things. AdventOfCode... mostly ghci, but did have to compile to get better times on Day 23. |
| 2023-03-31 19:51:58 +0200 | <Ou42> | @djinn Num a => a -> a |
| 2023-03-31 19:51:58 +0200 | <lambdabot> | Error: Class not found: Num |
| 2023-03-31 19:52:08 +0200 | <Ou42> | @yow |
| 2023-03-31 19:52:08 +0200 | <lambdabot> | Actually, what I'd like is a little toy spaceship!! |
| 2023-03-31 19:52:13 +0200 | <Ou42> | me too! |
| 2023-03-31 19:52:29 +0200 | <Ou42> | at djinn doesn't have [ ] either. |
| 2023-03-31 20:02:26 +0200 | <geekosaur> | right, djinn can only handle a small number of typeclasses and can't do recursive types. there was a (now bitrotted) fancier version but if you add support for recursive types it can fail to find a solution |
| 2023-03-31 20:03:00 +0200 | <geekosaur> | (exference, if you want to look it up) |
| 2023-03-31 20:04:54 +0200 | <Ou42> | that's not part of lambdabot, right? |
| 2023-03-31 20:05:26 +0200 | <geekosaur> | right |
| 2023-03-31 20:05:41 +0200 | <geekosaur> | there used to be an exferenceBot, it's gone now |
| 2023-03-31 20:06:33 +0200 | <Ou42> | @hoogle Num a => a -> a |
| 2023-03-31 20:06:39 +0200 | <Ou42> | @hoogle Num a => a -> a |
| 2023-03-31 20:06:39 +0200 | <lambdabot> | Prelude negate :: Num a => a -> a |
| 2023-03-31 20:06:39 +0200 | <lambdabot> | Prelude abs :: Num a => a -> a |
| 2023-03-31 20:06:39 +0200 | <lambdabot> | Prelude signum :: Num a => a -> a |
| 2023-03-31 20:06:42 +0200 | <Ou42> | 3! |
| 2023-03-31 20:06:45 +0200 | <Ou42> | the answer is 3 |
| 2023-03-31 20:07:05 +0200 | <Ou42> | sorry, sleep deprivation |
| 2023-03-31 20:07:37 +0200 | <Ou42> | OK, gonna wind down and dream of the awesomeness that will be afforded me w/ all this soon to have efficiency. once I go left to go right etc etc. ( just joshing. ) |
| 2023-03-31 20:09:21 +0200 | <Ou42> | BTW, what does [m] mean? |
| 2023-03-31 20:09:54 +0200 | <Ou42> | it's a bridge to ... matrix? |
| 2023-03-31 20:10:05 +0200 | <geekosaur> | yes |
| 2023-03-31 20:10:30 +0200 | <Ou42> | can't belive I figured that out. I've only used it once a few years ago. |
| 2023-03-31 20:10:37 +0200 | <geekosaur> | I'm on both for various reasons including that element for android works better than any android IRC client I've found |
| 2023-03-31 20:10:58 +0200 | <Ou42> | nice. |
| 2023-03-31 20:12:19 +0200 | <Ou42> | thanks again. Hopefully things will smooth out and I'll make less noob errors. |
| 2023-03-31 20:12:29 +0200 | <Ou42> | until next time. Nanu Nanu. |
| 2023-03-31 20:15:55 +0200 | Ou42 | (~Ou4242a@2600:1700:e930:41b0:27e2:d5f9:7e0c:462b) (Quit: Leaving) |
| 2023-03-31 20:29:46 +0200 | catman | (~catman@user/catman) |
| 2023-03-31 21:19:14 +0200 | stackdroid18 | (14094@de1.hashbang.sh) (Quit: hasta la vista... tchau!) |
| 2023-03-31 21:21:55 +0200 | catman | (~catman@user/catman) (Ping timeout: 250 seconds) |
| 2023-03-31 21:42:18 +0200 | catman | (~catman@user/catman) |
| 2023-03-31 22:00:32 +0200 | catman | (~catman@user/catman) (Ping timeout: 248 seconds) |