Textmate is looking awesome (I just tried it Friday for the first time) and though I own a copy of BBEdit, I think I may switch. But there are a couple of things still missing, IMHO.
First, the Perl syntax bundle doesn't handle POD (=begin, =cut, etc.) yet. I very quickly hacked in support for simply =begin and =cut as block comments, but it would be ideal if it could do as good a job as BBEdit's syntax coloring for Perl/POD.
Second, I do miss BBEdit's integration of certain things in its script menu - 'find in reference' (really just shelling out of perldoc -f) and 'view POD' (just shelling out of perldoc), as well as the ability to execute in the debugger. It would be nice to be able to, within a project, execute things like 'perl -d <filename>' and such - or for a C/C++ program, run it in gdb. I realize this can be done in Textmate using the Automation->Commands menu, so perhaps what I'm saying is that a few more built-ins would be nice :)
Finally, for the syntax bundles, the non-uniformity of color schemes between bundles (I routinely work in projects involving Perl and C code) could stand to be improved - ideally, a way to graphically change the colors for the syntax bundles would be nice, too, rather than editing the bundles. For example, rather than specifying the RGB values in each syntax plist, have an indirect color code - for example, "keyword" or "comment" - and then in TextMate have a preference that allows you to specify colors for all of those, globally.
Anyways, TextMate is looking great. Keep up the good work!
-- "Failure is not an option, it comes bundled with the software" -DefCon 10 Noah M. Daniels ndaniels@mac.com
On Dec 19, 2004, at 18:32, Noah M.Daniels wrote:
[...] there are a couple of things still missing, IMHO.
I'm only aware of a single item [1] that kept 1.0.2 from being my final release -- I apologize for this obvious negligence, but as a tea drinker I am heavily biased toward letting it make tea before it can make coffee ;)
First, the Perl syntax bundle doesn't handle POD [...] it would be ideal if it could do as good a job as BBEdit's syntax coloring for Perl/POD.
Well... I never used BBEdit and I don't program in Perl -- but if there is anything limiting users in supporting various language constructs, I'd like to know about it (and I'm already aware of lack of recursion and back references in the end pattern (for heredocs) which I hope to have fixed for 1.1.1, along with some other improvements).
Second, I do miss BBEdit's integration of certain things in its script menu [...] what I'm saying is that a few more built-ins would be nice :)
As of such, there's nothing built-in, but there's a few default bundle items. TextMate is a general purpose text editor, and for most of what you want as build-in, I'm certain the majority doesn't need it.
When I add actual language modes it'll be more appropriate to have the stuff you talk about as 'defaults' (because it's then limited to a mode), but when that happens, I'll rely on external language mode maintainers. I see my job as writing the editor, not as writing the customization files for each and every language out there ;)
Finally, for the syntax bundles, the non-uniformity of color schemes between bundles [...]
Yes, I've commented on this a few times before. In the future (currently scheduled for version 1.1.1) it will be possible to impose style (and behavior) for language elements w/o changing the syntax files (and apply it to multiple syntaxes). The keyword system is too simplistic for what I have in mind, but a GUI is a goal, even if it only expose half the functionality available by editing the files manually.
[1] http://one.textdrive.com/pipermail/textmate/2004-November/001249.html
On Dec 20, 2004, at 8:55 AM, Allan Odgaard wrote:
On Dec 19, 2004, at 18:32, Noah M.Daniels wrote:
[...] there are a couple of things still missing, IMHO.
I'm only aware of a single item [1] that kept 1.0.2 from being my final release -- I apologize for this obvious negligence, but as a tea drinker I am heavily biased toward letting it make tea before it can make coffee ;)
So a full-fledged Turkish coffee isn't likely until 2.0?
First, the Perl syntax bundle doesn't handle POD [...] it would be ideal if it could do as good a job as BBEdit's syntax coloring for Perl/POD.
Well... I never used BBEdit and I don't program in Perl -- but if there is anything limiting users in supporting various language constructs, I'd like to know about it (and I'm already aware of lack of recursion and back references in the end pattern (for heredocs) which I hope to have fixed for 1.1.1, along with some other improvements).
POD is pretty easy - a line beginning with '=' (i.e. =begin, =head1, =synopsis) begins a POD block; a line beginning with '=cut' ends the POD block. It's basically Perl's built in documentation system that also doubles as a method of block-commenting. All you really have to do is treat it as block comments, with any line starting '=' beginning a comment block, and any line starting '=cut' ending one. Yes, the '=' must be the first character on the line. When people use it for documentation, you'll see extra '=' directives in the middle (i.e. '=item1' and such) but that should be irrelevant. In other words, blocks do not nest; =cut closes ALL POD and returns you to code.
As of such, there's nothing built-in, but there's a few default bundle items. TextMate is a general purpose text editor, and for most of what you want as build-in, I'm certain the majority doesn't need it.
Yeah, the more I play with the ability to add custom commands, the more I realize my request was unnecessary. What *would* be nice would be better control over the window that pops up if one chooses a new window to display the output of the command - perhaps the ability to specify the window size/position.
-- "Failure is not an option, it comes bundled with the software" -DefCon 10 Noah M. Daniels ndaniels@mac.com
On Dec 20, 2004, at 15:11, Noah M.Daniels wrote:
POD is pretty easy - a line beginning with '=' [...]
Okay, I take it you just added this to the Perl syntax file by Eric Hsu? You may want to send him your changes, although he probably will add support for it when he reads this :)
What *would* be nice would be better control over the window that pops up if one chooses a new window to display the output of the command - perhaps the ability to specify the window size/position.
I should probably refine it a little -- it hasn't received any attention since it was added before 1.0.
I could add a few options to the actual window (e.g. place them in a drawer that can be toggled, like with the web preview), and allow for these to be either global or saved with the command that spawned the window (incl. size/position). This avoids any extra gadgets and/or output options in the command editor (which I prefer to keep simple).
I'll add it to the to-do.
Also, a reminder to new users: The syntax files are currently created by users of Textmate.
On Dec 20, 2004, at 9:52 AM, Allan Odgaard wrote:
On Dec 20, 2004, at 15:11, Noah M.Daniels wrote:
POD is pretty easy - a line beginning with '=' [...]
Okay, I take it you just added this to the Perl syntax file by Eric Hsu? You may want to send him your changes, although he probably will add support for it when he reads this :)
What *would* be nice would be better control over the window that pops up if one chooses a new window to display the output of the command - perhaps the ability to specify the window size/position.
I should probably refine it a little -- it hasn't received any attention since it was added before 1.0.
I could add a few options to the actual window (e.g. place them in a drawer that can be toggled, like with the web preview), and allow for these to be either global or saved with the command that spawned the window (incl. size/position). This avoids any extra gadgets and/or output options in the command editor (which I prefer to keep simple).
I'll add it to the to-do.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/mailman/listinfo/textmate
Noah M.Daniels wrote:
[...] there are a couple of things still missing, IMHO.
I'm only aware of a single item [1] that kept 1.0.2 from being my final release -- I apologize for this obvious negligence, but as a tea drinker I am heavily biased toward letting it make tea before it can make coffee ;)
So a full-fledged Turkish coffee isn't likely until 2.0?
I'll have you know the menu panel data entry system of Starbucks for the United Kingdom, Europe and the Middle East is programmed using TextMate now :-D
Starbucks Turkey uses that system as well, and they have added a custom product: türk kahvesi Starbucks'ın geleneksel türk kahvesi sunumu
(translations welcome, but I *think* it means Turkish Coffee)
So, in a way, TextMate 1.0.2 is working on it..
Regards,
Martin
-
Allan Odgaard -
jeremy*pinnix -
M Spreij -
Noah M.Daniels