On April 5, 2017 at 2:27:34 PM, Tim Bates (timothy.c.bates(a)gmail.com) wrote:
I should have said I’ve forked these bundles from github so as to be able
to maintain my changes, use them on multiple machines etc.
So, I don’t have a set of over-rides from pristine.
On 5 Apr 2017, at 4:16 pm, Jacob Carlborg <doob(a)me.com> wrote:
Like many of us, I suspect, I’ve got core bundles (like markdown, regex
etc.) that I have customised with new snippets and commands, or just just
tweaks to language.
I’d like extricate my code from these, so that
1. I can let TM2 easily update the mainstream bundle
2. I can control my mods
3. From that base of clarity, I can submit generally-useful changes back to
the widely used central repo.
Are there any solutions to
1. Diffing the pristine bundle with my dirty copy?
2. Exporting modified snippets and commands to my personal repo
Ideally, the UUID exported commands would be entered into the plist of my
personal repo, perhaps under “exported from <bundlename> as a menu name.
Hope others have had this problem and solved it :-) Otherwise bit of a
manual trek in store for summer :-)
As far as I understand, at least for the built-in bundles, TextMate will
store the changes separately from the main bundle. The built-in bundles are
stored in ~/Library/Application Support/TextMate/Managed/Bundles, if you
make a change to one of those, it will store those changes as a diff (or
rather the overrides) in ~/Library/Application Support/TextMate/Bundles.
There’s also a directory called "Pristine Copy”, see section 5.2 here 
for more information.
- not sure if this is up to
textmate mailing list
I’m interested in hearing from a bundle developer or 2 on the topic. I
I use homeshick <https://github.com/andsens/homeshick> to manage my
settings/bundles. I’ve used the symlinking
<https://github.com/andsens/homeshick/wiki/Symlinking> guide and
now points to
Homeshick creates a git repo under repos/[repo name]. Committing (or
reverting) changes is now done in this git repository. If you like what
you’ve changed you can commit or you could move the change into the bundle.
For instance: If I make a change to a command, first I look at repo status,
and then I move the changes in into the bundle. Remove the diffs, and
I’m way over complicating this, I assume?