I hadn't originally included that tab stop, but added it for various and sundry reasons before uploading. But I think you're right, if you wanted to use a shortcut or something other than a preconfigured property:value; pair, a return at the end of the line would have the same effect with fewer keystrokes. I think that it's important to tab the entire declaration when first creating the definition, as at that point you haven't had a chance to make that choice. My other question would be: is the comment section worth the extra tab stop? Do other developers add comments on EVERY rule or should there just be a separate shortcut for adding a quick comment?
My revision to the class and ID definition snippets would include the initial property/value pair:
${2:${3:property}: ${4:value};}$0
and the New Declaration would remove the second tab stop:
; ${1:property}: ${2:value};$0
Also, the New Selector would remove the comment block and I would add a quick snippet triggered on *-Tab to create /* $0 */
Would that be a worthwhile improvement? Thanks for the feedback.
Thanks, Brett
On Oct 30, 2006, at 7:50 AM, Andreas Wahlin wrote:
These things are sweet, I modified them to fit my taste but the basic idea is left. I do question the wisdom of wrapping new declarations in a "tab" the first time around, seems pretty pointless, I want to get into the property directly. thanks again
Andreas
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
Brett Terpstra : Art Director Circle Six Design, Inc. 111 Riverfront Dr, Suite 204 .................................................. p: 507.459.4398 877.858.4332 f: 1.866.540.3063 e: brett@circlesixdesign.com http://www.circlesixdesign.com ..................................................