Logs: liberachat/#xmonad
| 2022-04-11 05:43:14 | × | dissociate[m] quits (~jessehorn@2001:470:69fc:105::1:41af) (*.net *.split) |
| 2022-04-11 05:43:14 | × | JosEduardo[m] quits (~joseemdsm@2001:470:69fc:105::ce1d) (*.net *.split) |
| 2022-04-11 05:43:14 | × | Drishal[m] quits (~drishalma@2001:470:69fc:105::a36) (*.net *.split) |
| 2022-04-11 05:43:14 | × | unclechu quits (~unclechu@2001:470:69fc:105::354) (*.net *.split) |
| 2022-04-11 05:43:14 | × | FatBoyXPC quits (~FatBoyXPC@user/fatboyxpc) (*.net *.split) |
| 2022-04-11 05:43:26 | → | burp joins (~quassel@hedgewars/sysadmin/burp) |
| 2022-04-11 05:43:35 | → | FatBoyXPC joins (~FatBoyXPC@user/fatboyxpc) |
| 2022-04-11 05:44:39 | → | jludwig joins (~justin@li657-110.members.linode.com) |
| 2022-04-11 05:44:51 | → | unclechu joins (~unclechu@2001:470:69fc:105::354) |
| 2022-04-11 05:45:31 | → | Drishal[m] joins (~drishalma@2001:470:69fc:105::a36) |
| 2022-04-11 05:46:20 | → | HAL[m] joins (~evadk8mat@2001:470:69fc:105::3ed0) |
| 2022-04-11 05:50:07 | → | dissociate[m] joins (~jessehorn@2001:470:69fc:105::1:41af) |
| 2022-04-11 05:50:13 | → | JosEduardo[m] joins (~joseemdsm@2001:470:69fc:105::ce1d) |
| 2022-04-11 06:03:39 | → | abhixec joins (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) |
| 2022-04-11 06:19:55 | <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 | → | cfricke joins (~cfricke@user/cfricke) |
| 2022-04-11 06:35:31 | <amenonsen> | maybe, but _this_ function is excellent. |
| 2022-04-11 06:41:38 | <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 | <amenonsen> | oh, you mean the namey-names rule. ;-) |
| 2022-04-11 07:10:32 | <tdammers> | Yeah. Naming things just because they exist. |
| 2022-04-11 07:45:45 | → | mohab joins (~mohab@156.223.48.148) |
| 2022-04-11 07:46:18 | × | mohab quits (~mohab@156.223.48.148) (Client Quit) |
| 2022-04-11 07:48:25 | × | abhixec quits (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Remote host closed the connection) |
| 2022-04-11 07:59:38 | <abastro[m]> | tdammers: Well yeah, I agree. Nevertheless, beginners seem to find it as a golden standard. Lol |
| 2022-04-11 07:59:50 | <abastro[m]> | Likely lots of ppl in industry would do so as well |
| 2022-04-11 08:00:45 | <abastro[m]> | "Deserve names, Should be named" could be hard for beginners at least tbh |
| 2022-04-11 08:01:15 | <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 | × | cfricke quits (~cfricke@user/cfricke) (Ping timeout: 246 seconds) |
| 2022-04-11 09:00:14 | × | liskin[m] quits (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2022-04-11 09:32:29 | <Solid> | I've never heard a beginner mention that book ever |
| 2022-04-11 09:32:42 | → | liskin[m] joins (~liskinmat@2001:470:69fc:105::768) |
| 2022-04-11 09:32:57 | × | m5zs7k quits (~m5zs7k@web10.mydevil.net) (Ping timeout: 272 seconds) |
| 2022-04-11 09:37:41 | → | m5zs7k joins (aquares@web10.mydevil.net) |
| 2022-04-11 09:59:17 | × | Natch quits (~natch@c-67bae255.014-297-73746f25.bbcust.telenor.se) (Remote host closed the connection) |
| 2022-04-11 10:02:58 | × | banc quits (banc@gateway/vpn/airvpn/banc) (Ping timeout: 250 seconds) |
| 2022-04-11 10:03:21 | × | vanvik quits (~vanvik@78.156.12.223) (Quit: Later) |
| 2022-04-11 10:03:47 | → | vanvik joins (~vanvik@78.156.12.223) |
| 2022-04-11 10:06:31 | → | Natch joins (~natch@c-67bae255.014-297-73746f25.bbcust.telenor.se) |
| 2022-04-11 10:08:43 | → | banc joins (banc@gateway/vpn/airvpn/banc) |
| 2022-04-11 10:09:21 | <tdammers> | No, but it is often recommended *to* beginners, or people just past the beginner stage. |
| 2022-04-11 10:11:12 | × | Natch quits (~natch@c-67bae255.014-297-73746f25.bbcust.telenor.se) (Remote host closed the connection) |
| 2022-04-11 10:13:30 | <liskin> | I'd argue that no single book should be taken as gospel (pun very much intended). |
| 2022-04-11 10:15:05 | → | Natch joins (~natch@c-67bae255.014-297-73746f25.bbcust.telenor.se) |
| 2022-04-11 10:28:49 | → | dschrempf joins (~dominik@92-249-159-213.pool.digikabel.hu) |
| 2022-04-11 10:29:00 | × | dschrempf quits (~dominik@92-249-159-213.pool.digikabel.hu) (Client Quit) |
| 2022-04-11 10:41:36 | → | cfricke joins (~cfricke@user/cfricke) |
| 2022-04-11 11:19:16 | <amenonsen> | is spawnOnce a suitable replacement for spawn "pgrep xmobar >/dev/null || exec xmobar"? |
| 2022-04-11 11:20:08 | <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 | <amenonsen> | s/running/started/ |
| 2022-04-11 11:23:47 | <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 | <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 | <liskin> | Especially useful for per-screen xmobars if one expects to (dis)connect outputs dynamically. |
| 2022-04-11 11:24:55 | <amenonsen> | oh! |
| 2022-04-11 11:24:57 | <liskin> | amenonsen: BTW thanks for reporting on your experiences with sway, that's really appreciated |
| 2022-04-11 11:25:18 | <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 | <amenonsen> | (i'm using the spawn/pgrep trick to start other programs too, dunst, stalonetray, xss-lock, etc.) |
| 2022-04-11 11:26:01 | <amenonsen> | liskin: thanks. it was an interesting experience for sure. |
| 2022-04-11 11:26:07 | <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 | liskin | starts the other stuff via systemd, takes care of restarting too |
| 2022-04-11 11:27:03 | <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 | <amenonsen> | but i think it actually IS worse on this machine. |
| 2022-04-11 11:27:54 | <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 | <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 | <amenonsen> | oh |
| 2022-04-11 11:32:35 | <amenonsen> | like picom? |
| 2022-04-11 11:32:53 | <liskin> | like that, yes |
| 2022-04-11 11:35:57 | ← | carloratm parts (carloratm@tilde.club) () |
| 2022-04-11 11:37:56 | × | geekosaur quits (~geekosaur@xmonad/geekosaur) (Remote host closed the connection) |
| 2022-04-11 11:38:16 | → | geekosaur joins (~geekosaur@xmonad/geekosaur) |
| 2022-04-11 11:38:35 | <mion> | xf86-video-intel is still maintained |
| 2022-04-11 11:38:44 | <mion> | (but modesetting is generally better) |
| 2022-04-11 11:40:12 | <amenonsen> | yikes |
| 2022-04-11 11:40:26 | <amenonsen> | (i just started picom) |
| 2022-04-11 11:40:37 | <mion> | default picom config is pretty bad |
| 2022-04-11 11:40:59 | <amenonsen> | thank you for giving me some hope that it may be possible to make it better :-) |
| 2022-04-11 11:41:11 | <mion> | it does silly things like make right click menus transparent |
| 2022-04-11 11:41:44 | <liskin> | amenonsen: it will make some things better and other things worse :-D |
| 2022-04-11 11:53:53 | <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 | <mion> | liskin: intel for some reason insist on keeping their own copy of it instead of upstreaming :/ |
| 2022-04-11 11:58:49 | <liskin> | mion: where does one find that copy? |
| 2022-04-11 11:59:19 | <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 | <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 | → | sagax joins (~sagax_nb@user/sagax) |
| 2022-04-11 12:04:27 | <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 | → | mc47 joins (~mc47@xmonad/TheMC47) |
| 2022-04-11 12:21:33 | × | Czernobog quits (~Czernobog@user/czernobog) (Read error: Connection reset by peer) |
| 2022-04-11 12:22:34 | → | Czernobog joins (~Czernobog@user/czernobog) |
| 2022-04-11 12:56:45 | <Ether[m]> | Does anyone how i can only have borders on focused window? |
| 2022-04-11 12:57:09 | <Ether[m]> | Not on inactive windows/recent windows.. |
| 2022-04-11 13:00:05 | <geekosaur> | that's somewhat difficult to do |
| 2022-04-11 13:00:41 | <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 | <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 | <Ether[m]> | geekosaur: Cleaver |
| 2022-04-11 13:02:32 | <Ether[m]> | Clever* |
| 2022-04-11 13:02:58 | <Ether[m]> | But isnt that the norm window border color? |
| 2022-04-11 13:03:08 | <Ether[m]> | How do i change inactive window color? |
| 2022-04-11 13:03:31 | <geekosaur> | inactiveBorderColor is one of the things you can set in the config record |
| 2022-04-11 13:04:19 | <geekosaur> | sorry, it's normalBorderColor as opposed ot activeBorderColor |
| 2022-04-11 13:04:21 | <geekosaur> | https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs#L89 |
| 2022-04-11 13:06:53 | <Ether[m]> | Hmm |
All times are in UTC.