News for hackers. Stuff that matters.
Re:Show HN: completeme, 't' in Github for Bash by GhotiFish on Wednesday February 20, 2013 @10:35AM (#5250963)
You opted for JSON for configuring your project. I've seen other people do that, but the problem is most interpreters don't support comments (because comments arn't part of json) and even if you have really_verbose_names_with_underlines_for_spaces, sometimes you just can't get away without comments.

YAML, I think, is better suited for configuration files.

Disclaimer: This is a minor criticism.

Re:Show HN: completeme, 't' in Github for Bash by glenjamin on Wednesday February 20, 2013 @10:39AM (#5250989)
Depending on how strict the interpreter of the JSON is, you can often get away with using unexpected keys - something like:

    {
      "//comment": "default = 0",
      "godMode": 1
    }
Re:Show HN: completeme, 't' in Github for Bash by mattspitz on Wednesday February 20, 2013 @11:20AM (#5251289)
Thanks for the thought. I wanted to use something like YAML but I didn't want to introduce an unnecessary dependency.

Upon further review, I probably could have used a vanilla .ini file and ConfigParser (http://docs.python.org/2/library/configparser.html) It's a built-in module and .ini supports comments.

Re:Show HN: completeme, 't' in Github for Bash by notaddicted on Wednesday February 20, 2013 @12:37PM (#5251841)
(not OP) I personally like using regular python for python project config files (like django does.) If you want to keep it simple, it will be simple, if you want to do something fancy you have the whole language.