Show HN: completeme, 't' in Github for Bash
pypi.python.org
Show HN: completeme, 't' in Github for Bash
1–10 of 21 posts
Re: Show HN: completeme, 't' in Github for Bash
#2You 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
#3You 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.
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
#4Eh, SublimeText does this already. Cool to have it in Bash though.
Re: Show HN: completeme, 't' in Github for Bash
#5Eh, SublimeText does this already. Cool to have it in Bash though.
That may be where GitHub got it from.
I don't use SublimeText because it's not installed on all the machines I login to. Also, GUI windows are a pain.
Re: Show HN: completeme, 't' in Github for Bash
#6Re: Show HN: completeme, 't' in Github for Bash
#7You 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.
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
#8Very cool, I love using this feature on github.
Looks like it looks for github repos, and will search up the tree and back down from there. However, this seems to mess up for me. If I go into a sub-directory in a repo and then try to open a file in the parent directory via `ctl+t`, then it tries to open that filename in the current directory, not from the parent (I'm using emacs as $EDITOR).
One other little thing, is there a way to get curses to cleanup better after itself? My terminal ends up with a relatively large blank spot after finding something, viewing it, and then closing emacs.
Re: Show HN: completeme, 't' in Github for Bash
#9Eh, SublimeText does this already. Cool to have it in Bash though.
That may be where GitHub got it from. I don't use SublimeText because it's not installed on all the machines I login to. Also, GUI windows are a pain.
I find tiling window managers to alleviate the pain of GUI windows. I use XMonad, and I love it!