GitSavvy icon indicating copy to clipboard operation
GitSavvy copied to clipboard

Feature Request: Do not load on excluded directories

Open stdedos opened this issue 6 years ago • 6 comments

I routinely work on remote git repositories, e.g.

sntentos@home [2018-03-16 14:47:39]:/run/user/1000/gvfs$ ls -lah
total 28K
dr-x------  9 sntentos sntentos    0 Μάρ  16 11:33 .
drwx------ 12 sntentos sntentos  320 Μάρ  16 13:59 ..
drwxr-xr-x  1 sntentos sntentos 4,0K Μάρ  14 06:52 sftp:host=172.16.253.147
drwxr-xr-x  1 sntentos sntentos 4,0K Φεβ  22 06:17 sftp:host=192.168.200.104

Where git calls are too slow. I want to keep my extensions etc as-is, but simply 'not access' the repositories for information.

or, change something in Sublime? I don't know if it is possible that way

stdedos avatar Mar 16 '18 12:03 stdedos

ok... What are you asking for?

stoivo avatar Mar 16 '18 13:03 stoivo

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

randy3k avatar Mar 16 '18 14:03 randy3k

@randy3k :+1: @stoivo I tried really hard to make it understandable on the first try ... thank you for proving me wrong 😂

stdedos avatar Mar 16 '18 16:03 stdedos

Potentially, there are three places to specify such setting.

  1. use git config
git config --add GitSavvy.disable true
git config --get GitSavvy.disable
  1. use Sublime project settings in foobar.subime-projects
{
    "settings": {
        "GitSavvy": {
           "disable": true
        }
    }
}
  1. use GitSavvy.sublime-settings with a setting such as
{
      "directories_to_exclude" : []
}

Not sure which method is the best.

randy3k avatar Mar 19 '18 19:03 randy3k

I recently started to use projects and likes it alt but I would implement 1. and 2.

stoivo avatar Mar 19 '18 19:03 stoivo

Disclaimer; I will use my personal scope. Feel free to ignore me 😃

@randy3k @stoivo

  1. "I am not opposed" to having a git add/get config. That's manageable.

  2. I find it complicated to fit this in my usecase - since the file would be required to exist in the repository. Problem is not "the repository itself", rather it's location (on the network)

  3. That's what I've been originally thinking. I'd see me write one of the following versions:

"/run/user/1000/gvfs/", provided 'it applies to any git repository found here and underneath',
"/run/user/1000/gvfs/**" / "/run/user/1000/gvfs/*", as a glob-pattern, or
"(gvfs|sftp|nfs)", as a ReGeX pattern

I am happy you are picking up the task 😄

stdedos avatar Mar 19 '18 20:03 stdedos