2022/04/11

2022-04-11 00:00:04 +0000mvk(~mvk@2607:fea8:5ce3:8500::9d5a) (*.net *.split)
2022-04-11 00:00:05 +0000ectospasm(~ectospasm@user/ectospasm) (*.net *.split)
2022-04-11 00:00:05 +0000joshproehl(~quassel@user/joshproehl) (*.net *.split)
2022-04-11 00:00:05 +0000coldpress(~coldpress@72.136.212.35.bc.googleusercontent.com) (*.net *.split)
2022-04-11 00:00:30 +0000joshproehl(~quassel@user/joshproehl)
2022-04-11 00:01:02 +0000ectospasm(~ectospasm@23-227-173-50.static.hvvc.us)
2022-04-11 00:01:56 +0000ectospasmGuest5909
2022-04-11 00:02:09 +0000coldpress(~coldpress@72.136.212.35.bc.googleusercontent.com)
2022-04-11 00:22:04 +0000Guest5909(~ectospasm@23-227-173-50.static.hvvc.us) (Quit: WeeChat 3.5)
2022-04-11 00:22:23 +0000ectospasm(~ectospasm@user/ectospasm)
2022-04-11 00:37:12 +0000noex(~null@user/noex) (Quit: :q!)
2022-04-11 00:40:09 +0000abhixec_(~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Quit: leaving)
2022-04-11 00:53:48 +0000noex(~null@user/noex)
2022-04-11 02:03:54 +0000banc(banc@gateway/vpn/airvpn/banc) (Ping timeout: 272 seconds)
2022-04-11 02:12:28 +0000noex(~null@user/noex) (Ping timeout: 260 seconds)
2022-04-11 02:13:09 +0000noex(~null@user/noex)
2022-04-11 02:18:54 +0000 <abastro[m]> Yea, "Clean code" recommends defining named function for many trivial-looking things
2022-04-11 02:39:48 +0000banc(banc@gateway/vpn/airvpn/banc)
2022-04-11 02:46:49 +0000steve_(~steve@ool-182c2b80.dyn.optonline.net) (Ping timeout: 248 seconds)
2022-04-11 04:07:23 +0000steve_(~steve@ool-182c2b80.dyn.optonline.net)
2022-04-11 04:30:12 +0000jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 272 seconds)
2022-04-11 05:31:48 +0000vanvik(~vanvik@78.156.12.223) (*.net *.split)
2022-04-11 05:31:48 +0000anon_kun600[m](~anonkun60@2001:470:69fc:105::1:ebb8) (*.net *.split)
2022-04-11 05:31:48 +0000robinhood0018[m](~robinhood@2001:470:69fc:105::1:4dca) (*.net *.split)
2022-04-11 05:31:48 +0000pentagrade[m](~pentagrad@2001:470:69fc:105::1:e4ae) (*.net *.split)
2022-04-11 05:31:48 +0000CodeBitCookie[m](~code-bit-@2001:470:69fc:105::a2f) (*.net *.split)
2022-04-11 05:31:48 +0000M-elo-[m](~gilganixm@2001:470:69fc:105::3d09) (*.net *.split)
2022-04-11 05:31:48 +0000yuu[m](~yuumatrix@2001:470:69fc:105::8a6) (*.net *.split)
2022-04-11 05:31:49 +0000ghormoon(~ghormoon@ghorland.net) (*.net *.split)
2022-04-11 05:32:49 +0000vanvik(~vanvik@78.156.12.223)
2022-04-11 05:33:07 +0000ghormoon(~ghormoon@ghorland.net)
2022-04-11 05:33:58 +0000CodeBitCookie[m](~code-bit-@2001:470:69fc:105::a2f)
2022-04-11 05:35:04 +0000pentagrade[m](~pentagrad@2001:470:69fc:105::1:e4ae)
2022-04-11 05:36:11 +0000anon_kun600[m](~anonkun60@2001:470:69fc:105::1:ebb8)
2022-04-11 05:36:44 +0000robinhood0018[m](~robinhood@2001:470:69fc:105::1:4dca)
2022-04-11 05:38:08 +0000M-elo-[m](~gilganixm@2001:470:69fc:105::3d09)
2022-04-11 05:39:05 +0000yuu[m](~yuumatrix@2001:470:69fc:105::8a6)
2022-04-11 05:43:13 +0000jludwig(~justin@li657-110.members.linode.com) (*.net *.split)
2022-04-11 05:43:13 +0000burp(~quassel@hedgewars/sysadmin/burp) (*.net *.split)
2022-04-11 05:43:14 +0000HAL[m](~evadk8mat@2001:470:69fc:105::3ed0) (*.net *.split)
2022-04-11 05:43:14 +0000dissociate[m](~jessehorn@2001:470:69fc:105::1:41af) (*.net *.split)
2022-04-11 05:43:14 +0000JosEduardo[m](~joseemdsm@2001:470:69fc:105::ce1d) (*.net *.split)
2022-04-11 05:43:14 +0000Drishal[m](~drishalma@2001:470:69fc:105::a36) (*.net *.split)
2022-04-11 05:43:14 +0000unclechu(~unclechu@2001:470:69fc:105::354) (*.net *.split)
2022-04-11 05:43:14 +0000FatBoyXPC(~FatBoyXPC@user/fatboyxpc) (*.net *.split)
2022-04-11 05:43:26 +0000burp(~quassel@hedgewars/sysadmin/burp)
2022-04-11 05:43:35 +0000FatBoyXPC(~FatBoyXPC@user/fatboyxpc)
2022-04-11 05:44:39 +0000jludwig(~justin@li657-110.members.linode.com)
2022-04-11 05:44:51 +0000unclechu(~unclechu@2001:470:69fc:105::354)
2022-04-11 05:45:31 +0000Drishal[m](~drishalma@2001:470:69fc:105::a36)
2022-04-11 05:46:20 +0000HAL[m](~evadk8mat@2001:470:69fc:105::3ed0)
2022-04-11 05:50:07 +0000dissociate[m](~jessehorn@2001:470:69fc:105::1:41af)
2022-04-11 05:50:13 +0000JosEduardo[m](~joseemdsm@2001:470:69fc:105::ce1d)
2022-04-11 06:03:39 +0000abhixec(~abhixec@c-67-169-139-16.hsd1.ca.comcast.net)
2022-04-11 06:19:55 +0000 <tdammers> No offense, but there's a lot of bullshit in the Clean Code book, and even more bullshit touted by all sorts of people under the "clean code" umbrella
2022-04-11 06:33:57 +0000cfricke(~cfricke@user/cfricke)
2022-04-11 06:35:31 +0000 <amenonsen> maybe, but _this_ function is excellent.
2022-04-11 06:41:38 +0000 <tdammers> Sure, nothing wrong with naming things. As long as those things are tangible enough to be named, that is. But if you try to condense that into a nice soundbitey rule, you just get "things that deserve to be named should be named", so... meh
2022-04-11 06:45:51 +0000 <amenonsen> oh, you mean the namey-names rule. ;-)
2022-04-11 07:10:32 +0000 <tdammers> Yeah. Naming things just because they exist.
2022-04-11 07:45:45 +0000mohab(~mohab@156.223.48.148)
2022-04-11 07:46:18 +0000mohab(~mohab@156.223.48.148) (Client Quit)
2022-04-11 07:48:25 +0000abhixec(~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Remote host closed the connection)
2022-04-11 07:59:38 +0000 <abastro[m]> tdammers: Well yeah, I agree. Nevertheless, beginners seem to find it as a golden standard. Lol
2022-04-11 07:59:50 +0000 <abastro[m]> Likely lots of ppl in industry would do so as well
2022-04-11 08:00:45 +0000 <abastro[m]> "Deserve names, Should be named" could be hard for beginners at least tbh
2022-04-11 08:01:15 +0000 <abastro[m]> Tho ye I guess it makes more sense where simple null checks could mean `isLeaf` of tree
2022-04-11 08:10:18 +0000cfricke(~cfricke@user/cfricke) (Ping timeout: 246 seconds)
2022-04-11 09:00:14 +0000liskin[m](~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
2022-04-11 09:32:29 +0000 <Solid> I've never heard a beginner mention that book ever
2022-04-11 09:32:42 +0000liskin[m](~liskinmat@2001:470:69fc:105::768)
2022-04-11 09:32:57 +0000m5zs7k(~m5zs7k@web10.mydevil.net) (Ping timeout: 272 seconds)
2022-04-11 09:37:41 +0000m5zs7k(aquares@web10.mydevil.net)
2022-04-11 09:59:17 +0000Natch(~natch@c-67bae255.014-297-73746f25.bbcust.telenor.se) (Remote host closed the connection)
2022-04-11 10:02:58 +0000banc(banc@gateway/vpn/airvpn/banc) (Ping timeout: 250 seconds)
2022-04-11 10:03:21 +0000vanvik(~vanvik@78.156.12.223) (Quit: Later)
2022-04-11 10:03:47 +0000vanvik(~vanvik@78.156.12.223)
2022-04-11 10:06:31 +0000Natch(~natch@c-67bae255.014-297-73746f25.bbcust.telenor.se)
2022-04-11 10:08:43 +0000banc(banc@gateway/vpn/airvpn/banc)
2022-04-11 10:09:21 +0000 <tdammers> No, but it is often recommended *to* beginners, or people just past the beginner stage.
2022-04-11 10:11:12 +0000Natch(~natch@c-67bae255.014-297-73746f25.bbcust.telenor.se) (Remote host closed the connection)
2022-04-11 10:13:30 +0000 <liskin> I'd argue that no single book should be taken as gospel (pun very much intended).
2022-04-11 10:15:05 +0000Natch(~natch@c-67bae255.014-297-73746f25.bbcust.telenor.se)
2022-04-11 10:28:49 +0000dschrempf(~dominik@92-249-159-213.pool.digikabel.hu)
2022-04-11 10:29:00 +0000dschrempf(~dominik@92-249-159-213.pool.digikabel.hu) (Client Quit)
2022-04-11 10:41:36 +0000cfricke(~cfricke@user/cfricke)
2022-04-11 11:19:16 +0000 <amenonsen> is spawnOnce a suitable replacement for spawn "pgrep xmobar >/dev/null || exec xmobar"?
2022-04-11 11:20:08 +0000 <amenonsen> from what i understand, it wouldn't work if xmobar might be running somewhere else, but in my case i'm not starting it anywhere else, so it should be ok.
2022-04-11 11:20:14 +0000 <amenonsen> s/running/started/
2022-04-11 11:23:47 +0000 <amenonsen> on the other hand, when i change my xmonad.hs and restart, i expect it'll re-spawn everything. maybe it's not worth changing.
2022-04-11 11:24:15 +0000 <liskin> amenonsen: have you seen https://xmonad.github.io/xmonad-docs/xmonad-contrib-0.17.0.9/XMonad-Hooks-StatusBar.html ? That thing will spawn it for you, and also kill/restart it when needed.
2022-04-11 11:24:41 +0000 <liskin> Especially useful for per-screen xmobars if one expects to (dis)connect outputs dynamically.
2022-04-11 11:24:55 +0000 <amenonsen> oh!
2022-04-11 11:24:57 +0000 <liskin> amenonsen: BTW thanks for reporting on your experiences with sway, that's really appreciated
2022-04-11 11:25:18 +0000 <amenonsen> i was looking at moving from DynamicLog to StatusBar, but i didn't realise it could start xmobar for me too.
2022-04-11 11:25:46 +0000 <amenonsen> (i'm using the spawn/pgrep trick to start other programs too, dunst, stalonetray, xss-lock, etc.)
2022-04-11 11:26:01 +0000 <amenonsen> liskin: thanks. it was an interesting experience for sure.
2022-04-11 11:26:07 +0000 <liskin> some stuff in DynamicLog already did start it for you, but only the property-based logging stuff, not the pipe-based
2022-04-11 11:26:50 +0000liskinstarts the other stuff via systemd, takes care of restarting too
2022-04-11 11:27:03 +0000 <amenonsen> the funny thing is, screen tearing under X has never bothered me very much, but i'm finding it ridiculously obtrusive now. i honestly can't figure out if it's worse on this new machine where i've never run X before, or if it's like it always was, and i'm just noticing it more now.
2022-04-11 11:27:24 +0000 <amenonsen> but i think it actually IS worse on this machine.
2022-04-11 11:27:54 +0000 <liskin> if you've used x86-video-intel in the past, as many of us had at some point, chances are tearing was indeed not a problem historically
2022-04-11 11:29:31 +0000 <liskin> but it's no longer maintained and crashes a lot more than the modesetting driver, so distros no longer use it, and everyone needs to run a compositor these days
2022-04-11 11:30:23 +0000 <amenonsen> oh
2022-04-11 11:32:35 +0000 <amenonsen> like picom?
2022-04-11 11:32:53 +0000 <liskin> like that, yes
2022-04-11 11:35:57 +0000carloratm(carloratm@tilde.club) ()
2022-04-11 11:37:56 +0000geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2022-04-11 11:38:16 +0000geekosaur(~geekosaur@xmonad/geekosaur)
2022-04-11 11:38:35 +0000 <mion> xf86-video-intel is still maintained
2022-04-11 11:38:44 +0000 <mion> (but modesetting is generally better)
2022-04-11 11:40:12 +0000 <amenonsen> yikes
2022-04-11 11:40:26 +0000 <amenonsen> (i just started picom)
2022-04-11 11:40:37 +0000 <mion> default picom config is pretty bad
2022-04-11 11:40:59 +0000 <amenonsen> thank you for giving me some hope that it may be possible to make it better :-)
2022-04-11 11:41:11 +0000 <mion> it does silly things like make right click menus transparent
2022-04-11 11:41:44 +0000 <liskin> amenonsen: it will make some things better and other things worse :-D
2022-04-11 11:53:53 +0000 <liskin> mion: oh, interesting; having last released 7 years ago and having last pushed a year ago gives a different impression, though :-)
2022-04-11 11:56:32 +0000 <mion> liskin: intel for some reason insist on keeping their own copy of it instead of upstreaming :/
2022-04-11 11:58:49 +0000 <liskin> mion: where does one find that copy?
2022-04-11 11:59:19 +0000 <mion> liskin: don't have the url at hand. Intel added support for their new dgpus and stuff to it
2022-04-11 11:59:54 +0000 <mion> wouldn't be surprised if its some big corporate that insists on using the driver and intel catering to them
2022-04-11 12:00:13 +0000sagax(~sagax_nb@user/sagax)
2022-04-11 12:04:27 +0000 <amenonsen> btw, i've started using a NamedScratchpad to run insect.sh (a calculator with a text interface). it's pretty handy.
2022-04-11 12:15:05 +0000mc47(~mc47@xmonad/TheMC47)
2022-04-11 12:21:33 +0000Czernobog(~Czernobog@user/czernobog) (Read error: Connection reset by peer)
2022-04-11 12:22:34 +0000Czernobog(~Czernobog@user/czernobog)
2022-04-11 12:56:45 +0000 <Ether[m]> Does anyone how i can only have borders on focused window?
2022-04-11 12:57:09 +0000 <Ether[m]> Not on inactive windows/recent windows..
2022-04-11 13:00:05 +0000 <geekosaur> that's somewhat difficult to do
2022-04-11 13:00:41 +0000 <geekosaur> and there would be a lot of flickering, because you'd have to do it in the logHook so every time something changed all the borders would flicker
2022-04-11 13:01:35 +0000 <geekosaur> I just set the inactive border color to the same as my gtk theme's window color so it's not obvious
2022-04-11 13:02:26 +0000 <Ether[m]> geekosaur: Cleaver
2022-04-11 13:02:32 +0000 <Ether[m]> Clever*
2022-04-11 13:02:58 +0000 <Ether[m]> But isnt that the norm window border color?
2022-04-11 13:03:08 +0000 <Ether[m]> How do i change inactive window color?
2022-04-11 13:03:31 +0000 <geekosaur> inactiveBorderColor is one of the things you can set in the config record
2022-04-11 13:04:19 +0000 <geekosaur> sorry, it's normalBorderColor as opposed ot activeBorderColor
2022-04-11 13:04:21 +0000 <geekosaur> https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs#L89
2022-04-11 13:06:53 +0000 <Ether[m]> Hmm
2022-04-11 13:09:20 +0000 <geekosaur> are you really seeing recent windows colored differently? I think that's a specific module that does that
2022-04-11 13:09:26 +0000 <geekosaur> not default behavior
2022-04-11 13:31:02 +0000 <Ether[m]> <geekosaur> "are you really seeing recent..." <- What module?
2022-04-11 13:31:27 +0000 <Ether[m]> How do i stop this behavior?
2022-04-11 13:41:00 +0000 <geekosaur> I don't recall the module offhand
2022-04-11 13:41:17 +0000 <geekosaur> also I thought it only did that when activated (for window selection). this sounds odd
2022-04-11 13:41:30 +0000 <geekosaur> can you pastebin your current config?
2022-04-11 13:41:34 +0000 <geekosaur> @where paste
2022-04-11 13:41:34 +0000 <lambdabot> Help us help you: please paste full code, input and/or output at e.g. https://paste.tomsmeding.com
2022-04-11 14:16:41 +0000syg_(~syg@flamebot.net)
2022-04-11 14:17:00 +0000nomadxx3(~lanomadx@69.167.45.235)
2022-04-11 14:17:51 +0000syg(~syg@flamebot.net) (Ping timeout: 256 seconds)
2022-04-11 14:18:39 +0000nomadxxxx3(~lanomadx@69.167.45.235) (Quit: ZNC 1.8.2 - https://znc.in)
2022-04-11 14:19:08 +0000Rockj(~rockj@chromie.geekrevolution.net) (Ping timeout: 252 seconds)
2022-04-11 14:21:11 +0000Rockj(~rockj@chromie.geekrevolution.net)
2022-04-11 14:28:47 +0000noex(~null@user/noex) (Ping timeout: 260 seconds)
2022-04-11 14:30:47 +0000noex(~null@user/noex)
2022-04-11 14:32:20 +0000 <Ether[m]> <geekosaur> "can you pastebin your current..." <- Hmm
2022-04-11 14:32:31 +0000 <Ether[m]> Giimmme 2 mins.m
2022-04-11 14:47:19 +0000 <Ether[m]> geekosaur: its in my github..
2022-04-11 14:47:40 +0000 <Ether[m]> https://github.com/Ahanaf-Ether/xmonad/blob/stable/xmonad.hs
2022-04-11 14:48:15 +0000mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2022-04-11 14:48:35 +0000mc47(~mc47@xmonad/TheMC47)
2022-04-11 14:59:55 +0000 <geekosaur> it's WindowNavigation, looks like
2022-04-11 15:00:58 +0000 <geekosaur> the documentation is unfortunate but it comes with a WNConfig that disables the feature (noNavigateBorders)
2022-04-11 15:18:53 +0000 <Ether[m]> No way to disable?
2022-04-11 15:21:11 +0000 <Ether[m]> geekosaur
2022-04-11 15:27:55 +0000 <geekosaur> You have to replace `windowNavigation` with `configurableNavigation noNavigateBorders` everywhere it appears
2022-04-11 15:30:55 +0000 <Ether[m]> How i do that?
2022-04-11 15:31:30 +0000 <geekosaur> edit your config? search and replace is in pretty much every editor
2022-04-11 15:32:34 +0000 <Ether[m]> Ohh
2022-04-11 15:32:43 +0000 <Ether[m]> Just like that?
2022-04-11 15:32:49 +0000 <geekosaur> yes
2022-04-11 15:32:50 +0000 <Ether[m]> Isnt that a function?
2022-04-11 15:33:14 +0000 <Ether[m]> So that will throw an error?
2022-04-11 15:33:20 +0000 <geekosaur> yes but your config is already set up so you can just replace one with the other
2022-04-11 15:33:43 +0000 <Ether[m]> Do change it everywhere?
2022-04-11 15:33:53 +0000 <Ether[m]> Excluding import..
2022-04-11 15:34:02 +0000 <geekosaur> theimport starts with uppercase
2022-04-11 15:34:07 +0000jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-04-11 15:34:16 +0000 <geekosaur> if you do a case-matching search and replace it'll just work
2022-04-11 15:34:30 +0000 <Ether[m]> Ohh so all lowercase ones?
2022-04-11 15:34:33 +0000 <Ether[m]> Roger..
2022-04-11 15:36:43 +0000 <Ether[m]> Throws an error
2022-04-11 15:37:14 +0000Ether[m]uploaded an image: (161KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/BNkpghrdaUpeqBlVSdluUiij/20220411_213… >
2022-04-11 15:37:15 +0000 <Ether[m]> geekosaur
2022-04-11 15:38:35 +0000 <Ether[m]> My bad no space*
2022-04-11 15:38:59 +0000 <Ether[m]> No luck same behavior:(
2022-04-11 15:39:56 +0000 <geekosaur> hm, you imported it without a list so it should work, and I'm using the 0.15 docs so it should be there
2022-04-11 15:40:52 +0000Guest53(~Guest53@190.192.80.102)
2022-04-11 15:41:12 +0000Ether[m]uploaded an image: (160KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/iHzJSIuTWNDAYUpGUdxMJwvj/20220411_213… >
2022-04-11 15:41:48 +0000 <Ether[m]> The less bright border is what i dont want..
2022-04-11 15:42:08 +0000 <Guest53> I would like to ask how i can get a transparent xmobar. I tryed setting alpha = 0, in the config file but nothing happens. Thanks
2022-04-11 15:42:58 +0000 <Ether[m]> Guest53: Picom..
2022-04-11 15:43:09 +0000 <Ether[m]> You need to use a compositor..
2022-04-11 15:43:45 +0000 <Ether[m]> Compton/picom one that supports transparency..
2022-04-11 15:44:20 +0000 <Ether[m]> Find class name for xmobar and set your picom config. Thats the general take..
2022-04-11 15:44:32 +0000 <Ether[m]> Guest53
2022-04-11 15:46:35 +0000 <geekosaur> Ether[m], you have that all over the place. you should probably pick one place to put it, not everywhere it could possibly appear…
2022-04-11 15:46:36 +0000 <Guest53> Ok, i am absolute layman with picom, how may I do what you suggested?
2022-04-11 15:47:13 +0000 <Ether[m]> geekosaur: ?
2022-04-11 15:48:02 +0000 <Ether[m]> Guest53: What distro are you on?
2022-04-11 15:48:04 +0000 <geekosaur> Guest53, https://github.com/geekosaur/xmonad.hs/blob/skkukuk/compton.conf#L11-L14 but you want to include it instead of excluding it (the key line is 13, but you want to match xmobar's window class instead)
2022-04-11 15:48:25 +0000 <geekosaur> Ether[m], I copied your config over here so I could see what was going wrong
2022-04-11 15:48:38 +0000 <Ether[m]> Oo
2022-04-11 15:48:39 +0000 <geekosaur> you have 10 different copies of `windowNavigation`
2022-04-11 15:48:48 +0000 <Ether[m]> Yes
2022-04-11 15:48:51 +0000 <Ether[m]> And?
2022-04-11 15:48:58 +0000 <geekosaur> one in each layout, one in myLayouts, and one where you use myLayouts
2022-04-11 15:48:59 +0000 <Ether[m]> For each layout..
2022-04-11 15:49:12 +0000 <Ether[m]> Yess.
2022-04-11 15:49:14 +0000 <geekosaur> so you're applyingt it 3 times
2022-04-11 15:49:27 +0000 <Ether[m]> Ohh
2022-04-11 15:49:31 +0000 <Ether[m]> So where should i apply it?
2022-04-11 15:49:39 +0000 <Ether[m]> For all/globally
2022-04-11 15:50:32 +0000 <geekosaur> you only need the one on line 538, the layoutHook definition
2022-04-11 15:50:46 +0000 <Ether[m]> Thanks
2022-04-11 15:52:07 +0000 <Guest53> Thanks, ill give it a try
2022-04-11 15:52:19 +0000cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.4.1)
2022-04-11 15:52:39 +0000 <Ether[m]> geekosaur: your a genius:)
2022-04-11 15:52:43 +0000 <geekosaur> and yes, any time you want to use alpha you need a compositor
2022-04-11 15:53:04 +0000 <geekosaur> some terminals can "fake" it but it's imperfect, and it's only terminals
2022-04-11 15:56:11 +0000 <geekosaur> which means just setting alpha might be enough as long as picom is running
2022-04-11 15:56:49 +0000 <geekosaur> (feel free to copy my config though, it's nicer than the default. unless you prefer inactive transparency to inactive dim, but I find that unreadable)
2022-04-11 16:13:08 +0000Guest53(~Guest53@190.192.80.102) (Quit: Client closed)
2022-04-11 16:24:36 +0000werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 272 seconds)
2022-04-11 16:47:16 +0000mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2022-04-11 16:47:35 +0000mc47(~mc47@xmonad/TheMC47)
2022-04-11 16:48:42 +0000 <Ether[m]> geekosaur i am really struggling trying to get swapping windows directional as expected 😫
2022-04-11 16:49:11 +0000 <Ether[m]> When i swap master window i cant move left..
2022-04-11 16:51:02 +0000 <Ether[m]> Window navigation2d doesn't know which window was last focused.. but windowNavigation does but swap wont work :(
2022-04-11 16:53:43 +0000 <geekosaur> I'm not sure I can help; I don't work with these layouts much, but I know they're kinda abusing xmonad a bit
2022-04-11 16:54:48 +0000 <Ether[m]> Any ideas?
2022-04-11 16:55:21 +0000 <Ether[m]> I hate having to itterate again and agin just to get to left or right windows..
2022-04-11 16:55:31 +0000 <Ether[m]> And i hate wrapping in general..
2022-04-11 16:56:37 +0000 <geekosaur> not really, no
2022-04-11 16:56:50 +0000 <geekosaur> maybe someone else here has an idea
2022-04-11 16:57:12 +0000 <geekosaur> (also I'm shortly going to be away for a couple of hours)
2022-04-11 16:57:38 +0000geekosaur's apartment has bedbugs. they're spraying every few weeks
2022-04-11 16:58:13 +0000 <geekosaur> (speaking of iterating…)
2022-04-11 16:58:35 +0000 <Ether[m]> Haha
2022-04-11 16:58:48 +0000 <Ether[m]> See ya!
2022-04-11 17:01:47 +0000The_Czernobog(~Czernobog@user/czernobog)
2022-04-11 17:01:51 +0000Czernobog(~Czernobog@user/czernobog) (Ping timeout: 256 seconds)
2022-04-11 17:02:21 +0000The_CzernobogCzernobog
2022-04-11 17:21:26 +0000geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2022-04-11 17:23:48 +0000geekosaur(~geekosaur@xmonad/geekosaur)
2022-04-11 17:24:32 +0000sagax(~sagax_nb@user/sagax) (Ping timeout: 250 seconds)
2022-04-11 17:29:40 +0000werneta(~werneta@137.79.198.1)
2022-04-11 17:29:52 +0000werneta(~werneta@137.79.198.1) (Client Quit)
2022-04-11 17:42:12 +0000Czernobog(~Czernobog@user/czernobog) (Ping timeout: 246 seconds)
2022-04-11 17:43:03 +0000Czernobog(~Czernobog@user/czernobog)
2022-04-11 19:13:56 +0000Guest53(~Guest53@190.192.80.102)
2022-04-11 19:26:24 +0000Zarak[m](~zarakmatr@2001:470:69fc:105::1:f67f)
2022-04-11 19:49:39 +0000 <anon_kun600[m]> how do I make it to where xmonad'
2022-04-11 19:49:45 +0000 <anon_kun600[m]> error messages actually are readable to me
2022-04-11 19:49:49 +0000 <anon_kun600[m]> how do I change font color
2022-04-11 19:52:21 +0000ircbrowse_tom(~ircbrowse@2a01:4f8:1c1c:9319::1)
2022-04-11 19:52:26 +0000Server+cnt
2022-04-11 19:52:43 +0000sagax(~sagax_nb@user/sagax)
2022-04-11 19:54:56 +0000geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2022-04-11 19:55:16 +0000geekosaur(~geekosaur@xmonad/geekosaur)
2022-04-11 20:14:49 +0000 <geekosaur> hm. normally it uses xmessage and the font is black on white
2022-04-11 20:15:36 +0000 <geekosaur> did your distro replace xmessage perhaps? or you have a gtk settings manager that also sets resources, in which case you would have to change it there somehow
2022-04-11 20:54:59 +0000Guest53(~Guest53@190.192.80.102) (Quit: Client closed)
2022-04-11 21:19:16 +0000yusz-01[m](~yusz-01ma@2001:470:69fc:105::1:f697)
2022-04-11 22:34:09 +0000mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2022-04-11 22:55:26 +0000geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2022-04-11 22:57:08 +0000geekosaur(~geekosaur@xmonad/geekosaur)
2022-04-11 23:07:25 +0000werneta(~werneta@137.79.198.1)