On Nov 20, 2006, at 10:13 PM, Charilaos Skiadas wrote:
change this number. So what you would have to do is in the command line find the bundle and duplicate it, and then in the copy find the corresponding info file, and use the "uuidgen" command line tool to generate a random UUID, and put that as the UUID in that file, so that it differs from the shell one.
Now, this is only half the work[snip]
Even simpler… ;)
Go into the bundle editor and select your bundle, hit the button at the bottom with two plusses to duplicate (middle button). This will give everything in there a unique uuid. Close the bundle editor. Then go into finder and delete your first bundle (in ~/Library/Application Support/Bundles/). Then in TextMate choose the reload bundles option under the Bundles menu. (You don't want to delete the bundle from within TextMate because then it would mark it as deleted and the old Shell Bundle would never appear.)
The simply rename the new bundle and everything should work just fine.
Realistically the Shell bundle was never meant to be specific to bash, it just has been because most people use bash so that's what people submitted stuff for. ;) Some of the things like command completion, path completion etc could actually be shared so it might make sense to leave it as one. But it depends how many bundle items a shell gets.
Also if it ends up that a lot of stuff is shared between them perhaps it would be good to use source.shell.*? Dunno, just a thought.