Show HN: completeme, 't' in Github for Bash
pypi.python.org
pypi.python.org
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.
Also, it'd be really nice if the open action ended up in my bash history, e.g., open something via `completeme`, close it, and then use ctrl+r or the up arrow to get back to it and open it again.
One more—running the escape command (ctrl+g) seems to exit emacs? (using emacs 24.2.1)
- Good catch on the subdirectories within a git repository. Currently, we'll open the file you end up on with $EDITOR, which isn't necessarily correct relative to your cwd. I'll fix that. - Re: curses cleaning up after itself, I haven't seen that in xterm or terminator. Are you sure that's completeme's fault? Perhaps it's iTerm or emacs? I've never used iTerm and don't have access to a Mac. It could have something to do with this function not getting called: https://github.com/mattspitz/completeme/blob/80328799a000180... - I originally had this writing to your bash history but removed it because it wasn't really executed by the user. This may end up being obviated by: https://github.com/mattspitz/completeme/pull/1 I'd like to have Return open your editor (with history) and something else (Tab?) dump back into your prompt. - I don't know what could cause your misbehavior in emacs with Ctrl+G. I'm using 24.3.1 and can't reproduce it.
I don't use SublimeText because it's not installed on all the machines I login to. Also, GUI windows are a pain.
Hard to believe that shipped two years ago
YAML, I think, is better suited for configuration files.
Disclaimer: This is a minor criticism.
{
"//comment": "default = 0",
"godMode": 1
}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.