On 9/13/06, Lars F. [email protected] wrote:
Well, it’s not a good sign for a text editor if there is a book needed to
understand it. IMO TextMate requires reading documentation because it’s not
intuitive at all (that doesn’t mean it’s not a good text editor).
Searching for “vi editor” on Amazon.
Showing 1 - 12 of 1826 Results
Searching for “emacs” on Amazon.
Showing 1 - 12 of 1722 Results
I checked out the web page of the book but there’s no way that I’ll spend
$20 for the PDF (a better price would be $8.99).
The $20 PDF already paid for itself in my brief overview of it
yesterday. I’ll easily save that much in time given the tips I’ve
I never had to read the Intellij IDEA documentation in over 4 years despite
the fact that Java projects are way more complex by default. Can’t wait
until IDEA has Ruby support, then I can replace TextMate.
I’ve only heard good things about Intellij, but I have not yet had a
chance to try it. I generally use Eclipse for my Java projects.
The thing is, the text editors in IDE’s like these are typically
dead-simple to use, in exchange for being less powerful than a
dedicated editor. Once you figure out how to trigger auto-complete
and code formatting, most everything else is a matter of finding the
right menu item for what you’re trying to do.
As far as that goes, great. But that’s not the appeal of TextMate.
If you’re using TextMate as a glorified Notepad it’s not worth the
money (for the program or the documentation). The point of TextMate
is that it’s a collection of tools that incrementally make your life
3rd party documentation like this isn’t really a sign of the program
being overly complicated (it’s not). It seems that this book came
into existence because of the large number of tools and scripts
available. It’s hard to know about them all, and this gives an
overview of useful things from a technical point-of-view.