Ok, I just have to say, WOW. I get it, I have drunk the cool aid and I am in heaven. I started using TextMate for a new project, I have been a faithful beliver in the 'it doesn't suck' BBEdit for as long as I can remember (I have CD's back to at least 3.0), but I think that app may begin to get more and more idle time...
The power of this app, tied into the command line and other goodies is only hurting my productivity in that I keep streamlining my work process, and tuning it, and tweeking it, oh who knew a text editor could be FUN! Thank you to every one who has contributed to the commands and snipits, and the syntax files.
One question though, is there a way to print out a pretty (enough) list of the snipit triggers for a particular syntax?
this is one app that is so worth registering. Wicked!
Sam D
Join us!
Glad to hear you got the bug too. I love the "teach them how to fish" aspect of TextMate. Since I started using it I have learned shell scripting, Perl, python and now I am gettting more into ruby simply because this little editor makes it so easy and fun to want ot learn with.
Cheers Robert
On Apr 26, 2005, at 7:51 PM, Samuel DeVore wrote:
Ok, I just have to say, WOW. I get it, I have drunk the cool aid and I am in heaven. I started using TextMate for a new project, I have been a faithful beliver in the 'it doesn't suck' BBEdit for as long as I can remember (I have CD's back to at least 3.0), but I think that app may begin to get more and more idle time...
The power of this app, tied into the command line and other goodies is only hurting my productivity in that I keep streamlining my work process, and tuning it, and tweeking it, oh who knew a text editor could be FUN! Thank you to every one who has contributed to the commands and snipits, and the syntax files.
One question though, is there a way to print out a pretty (enough) list of the snipit triggers for a particular syntax?
this is one app that is so worth registering. Wicked!
Sam D ______________________________________________________________________ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
And now go and buy a license to support this awesome product!
Nick (TM amateur salesman)
On Apr 26, 2005, at 9:51 PM, Samuel DeVore wrote:
Ok, I just have to say, WOW. I get it, I have drunk the cool aid and I am in heaven. I started using TextMate for a new project, I have been a faithful beliver in the 'it doesn't suck' BBEdit for as long as I can remember (I have CD's back to at least 3.0), but I think that app may begin to get more and more idle time...
The power of this app, tied into the command line and other goodies is only hurting my productivity in that I keep streamlining my work process, and tuning it, and tweeking it, oh who knew a text editor could be FUN! Thank you to every one who has contributed to the commands and snipits, and the syntax files.
One question though, is there a way to print out a pretty (enough) list of the snipit triggers for a particular syntax?
this is one app that is so worth registering. Wicked!
Sam D ______________________________________________________________________ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On Apr 27, 2005, at 4:51, Samuel DeVore wrote:
One question though, is there a way to print out a pretty (enough) list of the snipit triggers for a particular syntax?
Kevin (eridanus on IRC) is working on something related to key bindings and bundle items.
However, to e.g. get a list of all the snippets in the Objective-C bundle and their tab-trigger, from Terminal.app you can run these two lines:
cd <bundle-directory> for file in Objective-C.tmbundle/Snippets/*.plist; do pl < "$file"|egrep '(name|tabTrigger) ='; done
Although the list might not be pretty, it should be easy to reformat.
My convention about naming the snippet after the construct it inserts (with “..” for placeholders) and the tab-trigger in parenthesis, seems to have failed miserably. I'll try harder in the future to enforce this! ;)