Hi Rob,
On 03.12.2009, at 18:26, Rob Goedman wrote:
My understanding of how to customize TextMate is limited, but earlier this week I did learn the hard way that below steps to update R.tmbundle override local modifications.
Sorry about that. I think my suggestion to remove the R.bundle entirely before updating caused that.
In my particular way of working with R (R.app mostly), I do not want TextMate to ever change working directories inside R, I like to source a file instead of sending all lines as commands, print through SubEthaEdit, build packages, etc. . Not better than other ways of working with R, just what I have grown to like as best of breed. Typically I have been putting these 4 or 5 modified commands at the top of the R command list with associated shortcut keys.
What is the 'TextMate' way to preserve these changes with future updates? From the docs, should I have updated below 'cd ...' line to point at '~/Library/"Application Support"/TextMate/"Pristine Copy"/Bundles' (or even to go into /Library/...)?
It depends on how you would like to be up-to-date. Via svn is one way. Then:
export LC_CTYPE=en_US.UTF-8 mkdir -p ~/Library/Application\ Support/TextMate/Bundles cd ~/Library/Application\ Support/TextMate/Bundles svn co http://svn.textmate.org/trunk/Bundles/R.tmbundle
or to update only svn up http://svn.textmate.org/trunk/Bundles/R.tmbundle
works fine.
An other way is GetBundles which informs you about updates and you can install a new bundle or update a bundle just by double-clicking at the bundle name. Furthermore GetBundles keeps your Support/lib folder up-to-date.
Both ways won't touch your local changes because your changes are stored in .../Pristine Copy/Bundles - as the name it says. If you add your favourite commands this would be ok but if you changes a pre-defined command, well this could lead to some problems.
Hope this is of some help.
Cheers,
--Hans