On Oct 9, 2006, at 9:03 AM, Charlie Garrison wrote:
I did give this a whirl, and I must have been using it wrong (very possible ;)) but it didn't quite work as I had hoped (see: not at all, a key-combo could have been conflicting) But this isn't a job for a third party utility, SubEthaEdit, Xcode, TextMate, and even Smultron have some form of usable auto-complete built into the editor, not some third-party add-on. Considering two of the aforementioned are free, and the other two are well below BBEdit's price, I really don't want to shell out the money for BBEdit if one of the key features I think of a source editor is _completely_ missing and to gain that feature I have to rely on some third party tool. Don't get me wrong, BBEdit is a fantastic and robust editor, but with a major feature that almost every other editor in the market glaringly missing (enough so that somebody's written a third party tool to compensate) I can only assume somebody was being ironic when they put "It doesn't suck.®" on the product page :-/ I want to like BBEdit, I really do, since I think most of the other editor offerings are also missing at least one _major_ feature (tabs, code folding, macros, SCM integration), but its hard to with a price tag like it has, while lacking major, necessary, features, and receiving regular errors with code folding (error code -50 IIRC). no where's that flame retardant suit I had around here... Cheers. R. Tyler Ballance: Lead Mac Developer at bleep. software contact: [EMAIL PROTECTED] | jabber: [EMAIL PROTECTED] |
- Clippings versus autocompletion R. Tyler Ballance
- Re: Clippings versus autocompletion Daniel Flatin
- Re: Clippings versus autocompletion Charlie Garrison
- Re: Clippings versus autocompletion R. Tyler Ballance
- Re: Clippings versus autocompletion Maarten Sneep
