Aaron D. Marasco

I have had problems with this in large repos as well, and appreciate the improvement. However, in the past, I've had trouble with "git rev-parse" before. I'll annotate the changeset.

Honestly, I don't want/use untracked indication. That is different than dirty.

`git help stash` says "The command takes options applicable to the `git log` command to control what is shown and how." I just got it from there. `--grep` without the...

`if [ -n "$(git stash ...)" ]; then do_something_because_string_is_not_blank; fi`

Instead of a variable that disables all repos in your current shell, another option is to have something in your local clone that you know is problematic. A quick example...

IMHO this is kind of useless; it uses the local file system to _assume_ that you checked it out in a way that matches the repo name. Personally, I almost...

@paulaltin that sounds good to me if you add some inline comments to each concerning what you're trying to compute (I know `rev-parse` is kinda esoteric). That said, I'm just...

I haven't looked at the source lately, but if the "check if git (c726016)" isn't already in there, it should probably be at the beginning of _everything_ and just shortcut...

Same here, on Linux. Just upgraded w/ apm: "atom-ctags 5.1.0 -> 5.1.2" ``` $ atom --version Atom : 1.19.4 Electron: 1.6.9 Chrome : 56.0.2924.87 Node : 7.4.0 ```