[14:20] good morning [14:21] <_stink_> yo [14:22] cmaloney, getting back to you re cron scheduling, we have some tasks on particular days weekly, some on particular schedules. I'd be most interested in spacing/neatly scheduling the weekly jobs which need to be run on particular days [14:22] morning [14:22] happy new year! wondering when I [14:22] will write 2017 instead of 2018 first [14:26] <_stink_> when you writ eyour first check of 2018 [14:26] <_stink_> HAHAHA [14:26] <_stink_> funny right, writing a check? [15:05] not yet, I don't typically write them though, and I make use of things like date +%Y_%m_%d which should save me from messing it up for a while [15:07] date -R 4 lyfe yo. [15:49] Good morning [15:49] waldo323: I think you might want to check into a job scheduler [15:50] isn't cron a job scheduler? [15:50] It is, but something with a little more smarts than what cron has [15:50] :) [15:50] thanks [15:51] because its not just multiple things needing schedules, it is state-interdependant multiple things needing schedules. [15:51] You also might want to look into something like Luigi: https://github.com/spotify/luigi [17:12] thank you [17:33] yeah, time of execution sounds like a needed bit here [17:34] brousch: I got an email from joindiaspora re your birthday on the first :) assumed it was a fake bday [17:37] goat-g: why are you a goat? [17:40] `man timeout` limit the time something runs. [17:42] jrwren: I decided to transition from irssi to weechat+glowing bear over break, not 100% happy with the config yet, so irssi is running with my real nick over in screen 0 :) [17:43] * goat-g switches nicks === greg-g is now known as greg-goat === goat-g is now known as greg-g [17:44] you could use `timeout -s STOP` and then manually examine why it took so long and stopped and then `kill -s CONT` to continue if you wanted to let it keep going. [17:44] meh, me just kills irssi [17:45] * greg-g pours one out [17:45] greg-g: poor irssi. I'm not ready for the leap just yet. [17:45] :) [17:46] I know, and I just put this awesome irssi sticker on my new laptop (well, in Aug) [18:14] heh [18:14] I've been rather happy with Weechat greg-g so if you need some pointers I might be able to help with the transition [18:14] and as always, dumb looks are free [18:15] s/dumb looks/blank expressions/ [18:17] :) [18:18] rubby ducky mode? :) [18:18] rubber* [18:18] I don't want to rub anything [18:19] cmaloney: what are your buflist settings? [18:20] /set buflist.* [18:23] https://paste.ubuntu.com/26308001/ [18:23] I don't think I did anything special in there [18:24] * greg-g nods [18:24] doesn't look like it [18:24] what frontend do you use? [18:24] (if any) [18:24] tmux [18:24] * greg-g nods [18:24] weechat-curses [18:25] right right. Was wondering if you were a 100% glowing bear or whatever person [18:25] https://paste.ubuntu.com/26308011/ [18:25] a what? [18:26] No, I'm 100% terminal [18:26] via ssh [18:26] (though Glowing Bear looks rather nice) [18:30] yeah, I'm doing glowing bear on my phone, and -curses via mosh+screen :) [18:30] Sweet [18:32] Also - Pro-tip: Do not accidentally substitute * for % in Python: print("foo %s" * bar) [18:32] That does not end well [18:33] :) [18:44] just more evidence that static type checking is good. [18:47] Nah, I likke juggling with fire. :) [20:25] <_stink_> cmaloney++ [20:39] But what advantages does cmaloney++ have over regular cmaloney? Also, will Microsoft put out its own version of cmaloney#? :P [21:25] cmaloney# [22:47] cmaloney: do you use the smartfilter for filtering out most joins/parts?