Of course you can make TM scope aware and such, but AFAIK the completion mechanism can't be modified. Your bundle can be very refined but you will always have to use ESC and press again and again until you find the option you need...
The built in completion (ESC by default) might not be able to be modified (it actually can a little), but almost every language has one or several completion commands in the bundle. Check out PyRopes, and also the PHP bundle has a couple different great completion commands.
Brandon M Fryslie wrote:
The built in completion (ESC by default) might not be able to be modified (it actually can a little), but almost every language has one or several completion commands in the bundle. Check out PyRopes, and also the PHP bundle has a couple different great completion commands.
Well that is my point, you need to use a command.
Xcode gives you automatically the list of possible options, as compared to having to press a key and cycle through each possible option.
Check the video on my latest mail to see it in action.
On Jul 1, 2011, at 12:53 PM, pier25 wrote:
Brandon M Fryslie wrote:
The built in completion (ESC by default) might not be able to be modified (it actually can a little), but almost every language has one or several completion commands in the bundle. Check out PyRopes, and also the PHP bundle has a couple different great completion commands.
Well that is my point, you need to use a command.
Xcode gives you automatically the list of possible options, as compared to having to press a key and cycle through each possible option.
That is one of the things where I hope TM2 will give us more flexibility. I am hoping that we gain the ability (be it in a script, plugin, whatever) to intercept nearly all events, like mouse clicks (cmd-click, cmd-souble-click, alt-click etc), or cursor moved events, text changed events etc.
That would allow bundles or plugins to add a lot of really cool stuff.
Another 'must' in my book is for bundles to be able to hook into context menus (for things like "Show definition", "Show documentation" etc for the clicked text).
Some way of temporarily marking up code on the fly would also be cool, so that when a compiler/parser/whatever flags a problem in a certain line, we could highlight that line and if the compiler/parser/whatever provides a problem description or (gasp) even fix suggestions (like clang) there would be a way to add UI for that.
Well, we can dream...
Gerd
On Jul 1, 2011, at 11:12 AM, Gerd Knops gerti-textmate@bitart.com wrote:
That is one of the things where I hope TM2 will give us more flexibility. I am hoping that we gain the ability (be it in a script, plugin, whatever) to intercept nearly all events, like mouse clicks (cmd-click, cmd-souble-click, alt-click etc), or cursor moved events, text changed events
To me, this and related bundle enhancements is all 'textmate 2' needs to be. A release focused on extending it's strongest feature.
On Fri, Jul 1, 2011 at 7:44 PM, Brandon M Fryslie bmf@email.arizona.edu wrote:
The built in completion (ESC by default) might not be able to be modified (it actually can a little), but almost every language has one or several completion commands in the bundle. Check out PyRopes, and also the PHP bundle has a couple different great completion commands.
Do you have a URL to PyRopes? Couldn't find it in GetBundles or in a quick Google Search ...
-
Brandon M Fryslie -
Gerd Knops -
Phil -
pier25 -
Will