We develop on Mac with UnityDevelop through virtualization and a bridge program we assign as the Unity editor (which relays files/line #s to the virtualized UnityDevelop).
I installed TextMate and the Unity/Javascript Bundle from the Wiki.
Everything works without errors, but I don’t understand the autocomplete.
Apparently you’re supposed to hit ESC when you start typing a word… but when I do, it just completes it without giving me options to pick from nor an explanation from the scripting reference.
Is that how it’s supposed to work?
Could you explain a little bit about the workflow using TextMate?
You can change how the binds work by using the bundle editor, and changing the key bindings. You can also change colors in preference and stuff.
The current version of Textmate doesn’t support realtime variable saving (they are supposedly adding that in the next version). That can be a little bit annoying at first ( I came from Xcode which is imo the king of autocompletion and real time variable saving ), but I got used to it reasonably quickly. Really, the upsides of Textmate far out-weigh the downsides, its very nice to be able to change virtually every aspect of everything. You can also write debuggers, command-line commands, wizards, that all will run in Textmate.
It will highlight various predefined variables (its all up to the bundle designer), so for me Vector3 does highlight, so does transform, player, and things like that. You can add new ones though, by just editing the Unity Javascript bundle a little bit.
The ESC-autocomplete in TextMate is really basic but largely powerful enough for most cases. It simply completes the current word by looking back- and forward in the current document for matches. You just hit ESC again to cycle through the matches (and shift-ESC to cycle backwards).
My Boo TextMate bundle includes autocomplete of all Unity methods using alt-ESC and will present you with a pop-up menu of all matches. (As well as tooltips for all properties and methods using ctrl-ESC). That kind of autocomplete is a per-bundle feature so you’ll have to check what a specific bundle offers for additional features.
If you don’t see the Unity stuff highlighted (e.g. Vector3) then check you’ve selected the Unity-specific language bundle. There are two bundles for all three Unity languages: A general one without Unity highlighting and a Unity-specific with the highlighting and you might have to select the one with “… (Unity)” in the name first.