joe update
KangOl opened this issue · 7 comments
Why vendoring https://github.com/github/gitignore?
Why not adding a joe update command that will do a git pull --quiet --force of the gitignore repository?
The initial clone can be done automatically at first call
And why not allowing to update from another repository (with custom gitignore files (see #9))
Looking into it.
We might want to do what's being proposed in #9. For any platform, we make a ~/.joe folder where all gitignore files can reside.
Post installation, we run joe update which pulls in the submodules and structures the folder as:
- .joe
---- github/gitignore # submodule
--------- Global
---- custom # custom files can go in here
This is not a submodule but a simple git repository.
Personally, I would follow XDG specs and store data in ~/.local/share/joe
+1 Great idea!
You could use the Github API so that you don't need to worry this at all. The API automatically pulls the latest version from the gitignore repo. I suppose using the API would conflict with using gitignore.io.
+1
+1. For now joe is not synced with python-ignore. Notice the .eggs folder.
After running pip install --upgrade joe, now I am using joe 0.0.6. Still missing some patterns.