Home freenode/#xmonad: Logs Calendar

Logs: freenode/#xmonad

←Prev  Next→
Page 1 .. 207 208 209 210 211 212 213 214 215 216 217 .. 397
39,606 events total
2021-03-04 09:57:31 <Liskni_s1> (Or with some sort of hack.)
2021-03-04 09:57:43 Liskni_s1 is now known as Liskni_si
2021-03-04 09:59:44 <Solid> 22:27 <Liskni_si> actually in that call for help issue in xmonad, someone suggested that we simply merge everything regardless of quality and give more contributors push rights << I mean, it's not like the bar to get a new module into -contrib is particularly high
2021-03-04 09:59:56 <Solid> setting it even lower might result in chaos
2021-03-04 10:01:41 <mc47> I see, thanks for the explanation
2021-03-04 10:02:09 <mc47> I guess it makes sense to have a sticky windows module
2021-03-04 10:02:25 <mc47> as in screen specific
2021-03-04 10:05:01 <Solid> does anyone know why X.U.XSelection.getSelection opens its own connection to the X server instead or re-using xmonad's?
2021-03-04 10:05:23 <Solid> is it just for the MonadIO constraint?
2021-03-04 10:05:28 <Solid> This seems to me like a weird priority
2021-03-04 10:12:49 <Liskni_si> Solid: I don't think the bar is very low actually
2021-03-04 10:14:08 <Liskni_si> Solid: yeah, I'm not forcing people to do kernel-style perfect commit messages, but I don't merge stuff without proper documentation and we even comment on coding style and so on
2021-03-04 10:14:48 <Liskni_si> (and yeah, some of this could be automated, which would then spare some reviewer time, probably, but it'd need to clean up the existing pieces first)
2021-03-04 10:14:50 <Solid> I suppose I have never submitted an entire module (though yesterday I got an idea for a really cool prompt2org module, so I'll probably try to find time for tat)
2021-03-04 10:15:08 <Liskni_si> re getSelection, did you read through https://code.google.com/archive/p/xmonad/issues/573 ?
2021-03-04 10:15:40 <Solid> my thinking usually is "if a project wants my garbage code their standards might not be that high" ... :>
2021-03-04 10:15:59 <mc47> Liskni_si yesterday I ran an hlint check on xmonad-contrib, and there were ~ 1000 warnings
2021-03-04 10:16:25 <Liskni_si> Solid: that's a thinking that is more dangerous every day you age :-)
2021-03-04 10:16:55 <mc47> I would go through them (not semi-automatically) if we want to enforce it in the CI
2021-03-04 10:17:30 <Solid> Liskni_si: I briefly read through that, but it seems to mostly be "how its implemented sucks, but maybe we can salvage it a bit"
2021-03-04 10:17:49 <Solid> maybe I need to de-mangle that IRC conversation
2021-03-04 10:18:41 <Liskni_si> yeah it doesn't really answer that question of yours, true :-)
2021-03-04 10:19:30 <Solid> I want proper primary selection and clipboard integration (in X, without a separate connection) for a proposed module of mine, so I guess I will find out at some point anyways :)
2021-03-04 10:20:24 <Liskni_si> I guess the real answer will be something like: we need a little event loop just around this one window and we don't want to fiddle with XCheckTypedWindowEvent so let's make another connection
2021-03-04 10:20:27 <Liskni_si> or something like that
2021-03-04 10:22:23 <Liskni_si> mc47: I have no opinion about hlint right now, but I guess it probably can't make things worse, so probably why not
2021-03-04 10:23:01 <Liskni_si> the best way to approach that would probably be to first fix ghc warnings, then maybe hlint warnings
2021-03-04 10:23:37 <Liskni_si> and this is the kind of thing where just pushing to master without going through PRs might be best :-)
2021-03-04 10:24:23 <Liskni_si> like do a couple fixes every day, see if CI passes, push to master, rinse, repeat
2021-03-04 10:24:33 <Solid> you mean people would bikeshed which hlint warnings are "worth" fixing? :)
2021-03-04 10:27:02 <Liskni_si> that's not my main concern, it's just that once we agree that those warnings should be fixed, there isn't much left to discuss, so there's no point in wasting other people's time on reviewing these changes in a PR
2021-03-04 10:28:44 <Solid> I see
2021-03-04 10:41:41 thc202 joins (~thc202@unaffiliated/thc202)
2021-03-04 11:00:50 <mc47> sounds reasonable
2021-03-04 12:00:14 xaltsc joins (~xaltsc@unaffiliated/xaltsc)
2021-03-04 13:07:36 geekosaur joins (82650c7a@130.101.12.122)
2021-03-04 13:35:43 × geekosaur quits (82650c7a@130.101.12.122) (Ping timeout: 240 seconds)
2021-03-04 13:51:12 geekosaur joins (82650c7a@130.101.12.122)
2021-03-04 13:51:46 × david2 quits (~david2@212-186-25-215.cable.dynamic.surfer.at) (Quit: WeeChat 3.0.1)
2021-03-04 14:01:08 seschwar joins (~seschwar@unaffiliated/seschwar)
2021-03-04 14:19:32 kelnoky joins (~shao@ip1f1285ec.dynamic.kabel-deutschland.de)
2021-03-04 14:41:36 × geekosaur quits (82650c7a@130.101.12.122) (Quit: Connection closed)
2021-03-04 15:04:48 × crab quits (~crab@pitta.toroid.org) (Remote host closed the connection)
2021-03-04 15:06:03 crab joins (~crab@pitta.toroid.org)
2021-03-04 15:38:11 kw joins (d4662d5d@212.102.45.93)
2021-03-04 15:39:00 × kw quits (d4662d5d@212.102.45.93) (Client Quit)
2021-03-04 16:29:29 × materiyolo quits (~materiyol@112.204.160.151) (Quit: WeeChat 3.0.1)
2021-03-04 16:39:05 × cfricke quits (~cfricke@unaffiliated/cfricke) (Quit: WeeChat 3.0.1)
2021-03-04 17:02:13 geekosaur joins (82650c7a@130.101.12.122)
2021-03-04 17:06:45 <Solid> mh I have to say I do like the look of the new website a bit more every time I visit it
2021-03-04 17:07:02 <Solid> it even works pretty well in eww, bar the huge picture on the front-page
2021-03-04 17:15:56 <heck-to-the-gnom> mc47: What's the benefit of using your StatusBar vs the older DynamicLog?
2021-03-04 17:16:06 toniz4 joins (~toniz4@unaffiliated/toniz4)
2021-03-04 17:16:31 <Solid> extensibility
2021-03-04 17:16:45 <heck-to-the-gnom> At first I thought it just a name change, but then I looked at your commits some more, and found them to be a bit different
2021-03-04 17:16:46 <Solid> and composability (supposedly, I haven't actually looked at the pr in quite a while :P)
2021-03-04 17:17:03 <heck-to-the-gnom> composability being? The ease of spinning up a new one?
2021-03-04 17:17:13 <Solid> plus safety if you count the new porperty-based logging solution
2021-03-04 17:17:23 <heck-to-the-gnom> (a new PP interface)
2021-03-04 17:17:27 <Solid> yes, much easier to configure several bars on several monitors without a lot of manual plumbing
2021-03-04 17:18:36 <heck-to-the-gnom> lets say I had one of these: `dynamicLogWithPP . namedScratchpadFilterOutWorkspacePP $ xmobarPP` - how easy would it be to transfer one of these to the new version once/if it gets accepted?
2021-03-04 17:18:51 <heck-to-the-gnom> Would it just work as-is?
2021-03-04 17:18:58 <Solid> yes
2021-03-04 17:19:08 <Solid> these functions stil exist
2021-03-04 17:19:28 <Solid> we do obviously provide backwards compatibility; don't want to break every config on the planet ;)
2021-03-04 17:19:50 <heck-to-the-gnom> No, I mean if I were to replace `dynamicLogWithPP` with the new `StatusBar`?
2021-03-04 17:20:07 <heck-to-the-gnom> Of course you'd leave the old one for compatibility sake
2021-03-04 17:22:29 <Solid> I think you'd just use `dynamicLogWithPP'
2021-03-04 17:23:08 <Solid> actually
2021-03-04 17:23:10 <Solid> no
2021-03-04 17:23:32 <Solid> heck-to-the-gnom: you are spawning your status bar manually right?
2021-03-04 17:24:01 <Solid> then you'd want to use something like statusBarProp
2021-03-04 17:24:12 <Solid> and remove things like the `docs' combinator
2021-03-04 17:27:17 ADG1089__ joins (~aditya@122.163.141.18)
2021-03-04 17:36:25 <mc47> heck-to-the-gnom it's more composable, and safer
2021-03-04 17:37:07 <mc47> basically, if you use it, you can easily have dynamic status bars (that react to screen changes)
2021-03-04 17:37:53 <mc47> Now, there's no support for multiple status bars: if you want to have more than one status bar, you'd have to write everything by hand
2021-03-04 17:39:58 <mc47> And to change something like `dynamicLogWithPP . namedScratchpadFilterOutWorkspacePP $ xmobarPP`, you'd have something like `main = do {mySb <- statusBarPipe "xmobar" (namedScratchpadFilterOutWorkspacePP xmobarPP); xmonad =<< makeStatusBar mySb myConf`
2021-03-04 17:41:30 <Solid> could probably just use `statusBar', no?
2021-03-04 17:41:56 <mc47> you can get rid of the `do ...` if you use dynamicSBs from #463, and you'd use it like you'd use ewmh or docks
2021-03-04 17:42:47 <mc47> Solid I removed statusBar' in my PR
2021-03-04 17:43:20 <mc47> Only the things from the release are kept, the rest is re-implemented in terms of StatusBarConfig
2021-03-04 17:43:35 <mc47> oh I left xmobarProp, thought it's useful
2021-03-04 17:44:54 <Solid> huh okay
2021-03-04 17:45:15 <Solid> seemed like a useful function to keep
2021-03-04 17:45:22 <Solid> but I was referring the the "normal" statusBar anyways :)
2021-03-04 17:51:36 <mc47> oh the normal is there
2021-03-04 17:51:45 <mc47> but it only takes a PP
2021-03-04 17:52:22 <mc47> btw, even the IORef trick doesn't fix the status bar getting launched too early
2021-03-04 17:53:31 × feepo quits (sid28508@gateway/web/irccloud.com/x-wcewznnvlbknipja) (Ping timeout: 272 seconds)
2021-03-04 17:53:45 tomjagua1paw is now known as tomjaguarpaw
2021-03-04 17:54:35 <Solid> rip
2021-03-04 17:55:03 <Solid> and what do you mean it only takes a PP?
2021-03-04 17:55:10 × ADG1089__ quits (~aditya@122.163.141.18) (Remote host closed the connection)
2021-03-04 17:55:16 <Solid> It's in 0.16 so surely it takes the arguments it did there?
2021-03-04 17:55:38 feepo joins (sid28508@gateway/web/irccloud.com/x-gkqhrcmhiiphbogr)
2021-03-04 18:06:11 <mc47> I mean not X PP
2021-03-04 18:06:53 <mc47> can get kinda awkward with the binds if someone is trying to follow a config or try it on their own
2021-03-04 18:07:18 <mc47> the new functions always take X PP to make the interface friendlier
2021-03-04 18:09:09 <Solid> is =<< so unfriendly? :o
←Prev  Next→
Page 1 .. 207 208 209 210 211 212 213 214 215 216 217 .. 397

All times are in UTC.