๐Ÿ‘คmattspitz๐Ÿ•‘12y๐Ÿ”ผ23๐Ÿ—จ๏ธ20

(Replying to PARENT post)

Very 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.

๐Ÿ‘คmrcoles๐Ÿ•‘12y๐Ÿ”ผ0๐Ÿ—จ๏ธ0

(Replying to PARENT post)

I've no idea how I'm supposed to install it. Didn't find instructions anywhere.
๐Ÿ‘คgoldfeld๐Ÿ•‘12y๐Ÿ”ผ0๐Ÿ—จ๏ธ0

(Replying to PARENT post)

Eh, SublimeText does this already. Cool to have it in Bash though.
๐Ÿ‘คcalinet6๐Ÿ•‘12y๐Ÿ”ผ0๐Ÿ—จ๏ธ0

(Replying to PARENT post)

This removes a major bash painpoint for me. Wicked awesome.
๐Ÿ‘คsmokestack๐Ÿ•‘12y๐Ÿ”ผ0๐Ÿ—จ๏ธ0

(Replying to PARENT post)

Wishlist #1 in a pull request :)
๐Ÿ‘คmarksteve๐Ÿ•‘12y๐Ÿ”ผ0๐Ÿ—จ๏ธ0

(Replying to PARENT post)

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.

๐Ÿ‘คGhotiFish๐Ÿ•‘12y๐Ÿ”ผ0๐Ÿ—จ๏ธ0