Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Curt J. Sampson
    @0cjs
    I get <$>; that's just fmap. It's <$ that I was asking about.
    sssjjjnnn
    @sssjjjnnn
    If you leave the < or > off it just drops that argument without passing it to the function
    You can do that with the star too
    function <$ drop_this_arg <*> arg1 <*> arg2
    func <$> arg1 <* drop_this_arg <*> arg2
    BTW, thanks for taking care of everything while I was gone/sick. Maybe we can get together once more sometime soon
    Curt J. Sampson
    @0cjs
    Yeah, I get <* and *>, too, I think; those seem pretty simple. But the type signature (<$) :: a -> f b -> f a isn't obvious to me, and from what you've said here and elsewhere I think I'm missing an intuition about the relationship between Appicative and Functors. I'll go back and spend an hour on it and I'm sure it will all come clear.
    No problem. Yeah, we should definitely get together soon, assuming I don't have measles. :-/ (I'm hoping this is just an alergic reaction to the MMR vaccination I had last Friday. Someone at work apparently came in with measles.)
    Ah ha! The b type in the above is completely unused! (I just had to think for a moment about what fmap . const does.)
    sssjjjnnn
    @sssjjjnnn
    That's not good, hopefully you didn't catch it. Maybe I should update my MMR
    Curt J. Sampson
    @0cjs
    You should, I think. The US CDC page is currently recommending that any adult born after 1957 who hasn't already had all three diseases get vaccinated. I don't know if it's because the shots we all (should have) had as children are losing effectiveness for some reason, or if there's a pool of non-immunized people out there.
    I'm sure that god-damned Jenny McCarthy hasn't been helping the situation at all.
    Curt J. Sampson
    @0cjs
    So, doctor was very mistaken and it's Shingles, not Measles. But regardless, I'm in a fair amount of pain at this point and probably will not be able to do stuff on the site over the next week or so.
    sssjjjnnn
    @sssjjjnnn
    I've heard that can be painful. Take it easy and get well soon
    Curt J. Sampson
    @0cjs
    It wasn't very painful for the first few days, but yeah, in the last day or so it's gotten bad enough that I can't really do anything at all.
    sssjjjnnn
    @sssjjjnnn
    If you have enough energy to look at some code, I just checked in more of the wiki markup processing. It can now read a file and do all the transcludes an produce the final output that should work in pandoc. Doesn't do parameters yet though.
    Curt J. Sampson
    @0cjs
    Oh, very cool. I will have a look at that at some point, but I can't really do anything code-related until the pain subsides. (Right now I feel as if someone's pounded a large nail into my head.) Maybe you can co-ordinate with @E14n_twitter (I've confirmed in person that the's real Edward) to get more pages brought over and some CSS etc. done. He's got a branch with some work on this done already. And you guys have the password for the Netlify account, though it should just start working when the DNS is changed. Same for lists.tlug.jp for the scraped copy of the current lists site. I didn't do any other subdomains; @ragga things we should just drop them and I agree. Everything should be pretty fully documented but ask here if you have questions.
    sssjjjnnn
    @sssjjjnnn
    Okay. Edward, are you on here? I don't have a twitter account. Still need to get the wiki parser branch sync'd up with master and tied into Hakyll.
    Curt J. Sampson
    @0cjs
    Edward is on here using his twitter account, @E14n_twitter . That's why I mentioned it's ben verified by me, since you have no evidence otherwise that it's actually the same person @emiddleton that is a member of https://github.com/tlug.
    sssjjjnnn
    @sssjjjnnn
    Ah, I see
    Curt J. Sampson
    @0cjs
    Yeah, identity verification is one of the rather cool things about Gitter that hadn't occurred to me until recently.
    sssjjjnnn
    @sssjjjnnn
    I just pushed some more code to dev/sjn/mediawiki-parser. This is fully sync'd up with master and with Edward's branch, and the transclude parser is linked in to Hakyll so it's generating the wiki pages correctly except for the params.
    sssjjjnnn
    @sssjjjnnn
    Just added parameter handling
    Edward Middleton
    @E14n_twitter
    @sssjjjnnn I am here now. Sorry about not being around on the weekend.
    Jim Tittsler
    @jimt
    Is it OK to change the DNS for the web site? Is everything done?
    Henri "Ragga" Servomaa
    @ragga

    At a quick glance, all looks good except the archive user/pw images which don't load on new.tlug.jp. Was that intentional?

    In any case, lists.tlug.jp is now pointed at Jims server and looks to be working fine, which is kinda the most important as it's the portal for the mailing list.
    Going forward, I think the main pages on both tlug.jp and lists.tlug.jp will have to be checked for consistency anyway.

    Jim Tittsler
    @jimt
    A lot of the links on new.tlug.jp front page appear to be broken (anything with wiki in the URL?).
    Henri "Ragga" Servomaa
    @ragga
    Yes, images in general seem to be missing.
    Curt J. Sampson
    @0cjs
    You guys did remember to regenerate the production release branch after committing the changes to master, right?
    sssjjjnnn
    @sssjjjnnn
    I haven't merged it yet. Does ./Test --dev-release work?
    Curt J. Sampson
    @0cjs
    Works fine, so long as you set up a site on netlify serving that branch.
    sssjjjnnn
    @sssjjjnnn
    What's the correct way to do it? Isn't it already set up on netlify?
    Does netlify need to be changed to point to the new release branch each time?
    Curt J. Sampson
    @0cjs
    We do not change the branch name holding the release; that would be as silly as changing the main branch name from master every time we did a commit. Perhaps it's not clear, but the release branch is an entirely different set of files from the source branch. It's basically a commit of everything under the _site directory and nothing else.
    Have you read through the docs on this?
    sssjjjnnn
    @sssjjjnnn
    No, that's why I haven't merged anything yet
    Curt J. Sampson
    @0cjs
    Ah. BTW, I think you already know this, but I do strongly suggest rebase and fast-forward over actual merge commits. Anyway, the docs are all there, and hopefully do a better and more detailed job of describing the release process that I could by typing here. But if you have questions, I'll try to answer them. I would start by setting up a release branch for your dev branch and serving that from your personal netlify account, so you can have some confidence you understand what's going on. (@E14n_twitter may also be able to help; I think he's done this.)
    sssjjjnnn
    @sssjjjnnn
    Right now my branch is rebased on to master with everyone's latest stuff an no merge commits. If there's one command I can type right now, I'll do it. (./Test --prod-release ??) If it's more involved than that, I can look at it a little later. Really busy with work at the moment.
    Curt J. Sampson
    @0cjs
    And all commits on your local master are pushed up to GitHub?
    sssjjjnnn
    @sssjjjnnn
    There are none, my branch is clean with respect to the GitHub master
    Curt J. Sampson
    @0cjs
    I'm confused by "there are none"; you mean you have made commits on master and pushed them up, and so what's on GitHub's master is the same as what's on your master? Or they're the same because you haven't put any new commits on master?
    sssjjjnnn
    @sssjjjnnn
    I've never committed anything to master, my master is the same as GitHub
    I don't know the exact git terminology, but you could set the github master branch to point to the same commit as dev/sjn/mediawiki-parser head and all would be good
    No need for any additional merging/rebasing/etc.
    Curt J. Sampson
    @0cjs
    Ah, ok. I see the last change on master is my last change. So the _site/ generated by that is still what's on the release branch, and running ./Test --prod-release will generate the same output, and so the commit to the release branch will be a do-nothing operation.
    sssjjjnnn
    @sssjjjnnn
    So I need to update master and then prod-release?
    Curt J. Sampson
    @0cjs
    But we're now getting to the point where we're the time you wait for me to type these answers is longer than it would be just to read the docs....
    sssjjjnnn
    @sssjjjnnn
    Okay...just give me a couple hours and I'll take care of it
    Curt J. Sampson
    @0cjs
    Yes. You add commits to the source branch, update the release branch with the new site generated from the latest commit, and push both. If you don't push the source branch, you end up with a released site that nobody can regenerate.
    sssjjjnnn
    @sssjjjnnn
    Makes sense