Randy Lai

I think what he is requesting is to disable GitSavvy for certain directories.

Potentially, there are three places to specify such setting. 1) use `git config` ``` git config --add GitSavvy.disable true git config --get GitSavvy.disable ``` 2) use Sublime project settings in...

I remember trying to add support for multiline staging. It'll require a partial rewrite of the related codebase. Given that it'll only have a little bit of gain, I am...

By the way, [this](https://github.com/divmain/GitSavvy/blob/master/core/commands/inline_diff.py#L348) is the related code. Take a look if you are interested in contributing.

Yes, at the very end after all the test suites are executed. I want to abort the tests as early as possible.

Maybe we should set the default value of `prompt_on_abort_commit` to true?

Actually, I tried the approach of applying the syntax line by line in the blame view, but it was incredibly slow and I had to abandon that.

It is ok for small files, but it is an O(n) operation.

No. I am not sure if sublime has an event listener on change of viewport.

I used `view.scope_name` to extract the scopes from an ordinary view of the file and then use `view.add_regions` to apply the scopes to the blame view. It was quite slow...